- This short introduction aims at providing some practical advice for setting-up an Ecipse IDE with JIRA.
- The benefit of integrating these two powerfull tools is just one more step closer to the "single point of development" approach.
- BTW: There is a connector for Microsoft Visual Studio, see http://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+for+Visual+Studio
What components will you need?
- First of all: Eclipse with Mylyn. We suggest to use the latest version of Eclipse.
- At the time of writing: Helios (3.6). Helios includes a current Mylin version (3.4).
- Of course, a JIRA server is required. At the time of writing version 4.1 was used. To communicate from Eclipse to JIRA and vice versa the JIRA Plugin is required.
Where to get it?
- Eclipse: http://www.eclipse.org
- JIRA: http://www.atlassian.com/software/jira/
- JIRA Plugin: http://confluence.atlassian.com/display/IDEPLUGIN/Installing+the+Eclipse+Connector. It is recommended to use the Eclipse-update Site of the JIRA Plugin .
- The source code of the connector is available from Atlassian.
- The source code for the connector is published as open source.
- To get an overview it is the best way to create a new project in Eclipse an connect to the subversion repository.
To start working with JIRA inside Eclipse some configuration has to be effected.
- This JIRA server has to enable the xml-rpc functionality. Normaly, this is a task that is effected by the JIRA Administrator.
- see https://developer.atlassian.com/display/JIRADEV/Remote+API+Reference
- The JIRA Plugin has to be imported in every Eclipse installation folder, e.g. /eclipse/plugins.
- For SOS the URL of the JIRA server is https://change.sos-berlin.com and the configuration as follows:
- It is required, to set the proxy proxy.sos to port 3128 to get in contact with JIRA.
- The (not required) Label should be "SOS Jira".
- The userid and password are the same as for user access to JIRA.
Working with JIRA