Editing Eclipse (section)

==Plug-Ins==

===Angular IDE===
* installed via eclipse marketplace

===Ant===
Das Ant-Plug-In ist integraler Bestandteil von Eclipse. Ein Ant-Build fügt man an folgender Stelle in den Properties eines Projekts ein:

[http://localhost/mediawiki-1.9.3/MyImages/eclipse.htm "Ant View"]

und kann dort editiert werden.
Der AntBuild kann entweder mit dem konfigurierten Target (s. 2. in Screeshot) oder aber mit einer manuellen Auswahl des Targets mit Doppelklick (s. 3. in Screenshot) erfolgen:
CallAntFromEclipse.jpg

===[[Git#Egit|EGit]]===
* Egit is the Eclipse standard and in most cases part of an Eclipse distribution
* tutorial and detailed description see [https://www.vogella.com/tutorials/EclipseGit/article.html here]
* installation s. Help -> About Eclipse IDE -> Installation Details -> Plug-Ins -> Filter to EGit
* available view s. Window -> Show View -> Others -> Git
** Git Staging
** Git Repositories
** History
* for adding, commiting and pushing use the 'Git Staging' view starting with 'Unstaged Changes' and adding or ignoring and committing or see below
Egit uses the same configuration files as git. The label decoration is shown in the views 'package explorer', 'project explorer' and 'navigator'. 

====Text Decorations====
* see Window -> Preferences -> Git -> Label Decorations -> Text Decorations

====Icon Decorations====
The decorations icons are:

[[File:GitIcons.png|400px]]

====Gitting an Eclipse Project====
There is a discussion if you should put multiple projects in one git repository or having a git repository for each eclipse projects. It seems that the second options is better if the projects are not related. The same applies to what should be included in a git repository and what should be ignored (see [http://blog.askjoelit.com/2014/07/eclipse-team-projects-best-practices.html here]).

See list below which files and folders should be in scope of git:
* \src\...
* \.settings\   // if projects settings differ from workspace settings
* \.classpath   // e.g. what is the source, where does the class files go, ...
* \.project

See list below which should be ignored:
* \bin\...  // or anything which can be recreated

* Right click on project -> Team -> Share Project
* Select repository or create a new one // moves the complete project to the repository 
* select files or folder and Team -> Add/Ignore

====Adding a file to the Index====
* Right Click on File -> Team -> Add to Index

====Unignore File or Directory====
* edit .gitignore and delete the rows
* add to file to index

====Committing Changes====
* Right Click on Project -> Team -> Commit opens the commit view

====Creating Project from Local Repository====
* File -> Import
* Git -> Projects
* Existing Local Repository
* Select Repository Directory
* Import as General Project
* Right Mouse on Project -> Configure -> ...Facet...
* Select Java (and additional)

===Show Differences===
* right click on project resource -> Compare with

===Maven===
Name is [http://www.eclipse.org/m2e/ M2E]. Documentation can be found [http://wiki.eclipse.org/Maven_Integration here].

If you have added a dependency manually to <code>pom.xml</code> then right click on project -> Maven -> Update Project.

===PDT===
* s. Installation of PDT
* adjust [[EONISLaptop#PHP|php.ini]] for XDebug
* adjusted Window->Preferences->PHP->Debug and PHP Executables

===BPMN2 Modeler===
* Help -> Install new Software -> http://download.eclipse.org/bpmn2-modeler/site

===JBoss Tools===

====Installation====
* Add Site http://download.jboss.org/jbosstools/updates/stable, check checkbox and press install

====Description====
The JBoss Tools are somehow an extension of the Java EE WTP Tools. The JBoss Tools contain a set of tools for Hibernate among others tools for reverse engineering an existing database and code generation. The documentation is [http://docs.jboss.org/tools/2.1.0.CR1/en/hibernatetools/publish/en-US/html/plugins.html#console_conf here]. My description is [[Hibernate#Reverse_Engineer_a_Database|here]]

===JDT===
The Jave Development Tools adds a Java project nature and Java perspective to the Eclipse Workbench as well as a number of views, editors, wizards, builders, and code merging and refactoring tools. The JDT project allows Eclipse to be a development environment for itself.

===Spring Tools===
* was called STS
* installed via Help -> Eclipse Marketplace (will not work in Eon CN) [[File:STS1.PNG|400px]]


===Subversion===
* installation like http://javathreads.de/2008/07/subversion-unter-eclipse-ganymede-konfigurieren/

===Subclipse===
====Installation====
#Help->Software Updates->Find and Install...
#Search for new features to install
#New Remote Site
#http://subclipse.tigris.org/update_1.2.x
#Restart

====Using====
If you add a file to your project, it's not automatically part of version control. Right-click the new file, then choose ''Team -> Add to Version Control''. If you've added a file to the repository that's no longer relevant to your project, you can easily delete it. Right-click the file, then choose Delete. No need for the Team menu. To rename a file or directory under Subclipse's control, right-click it, then choose Rename. Type the item's new name in the entry field and click Enter. The file is renamed in the project, and the rename operation (an Add for the new name, and a Delete for the old one) is queued for your next commit. If your project generates files, or otherwise includes files that you don't want to check in to the Subversion repository, you can tell Subclipse to ignore them. Right-click the file or directory you want to exclude from version control, then choose ''Team > Add to svn:ignore'' to display the Add to svn:ignore dialog. 
To ignore an already added file from a repository delete it with the SVN Repository Perspective and then sign it as svn:ignore.

===[[WTP|WTP]]===


===Workspace===

====JBoss 7 Quickstarts====
* File -> Import -> Existing Maven Projects -> C:\Uwes\java\jboss\jboss-as-quickstarts-7.1.0.Beta1b