Tag Archives: eclipse

Getting Jira to work within Eclipse

As by my post of yesterday that I am now using pulse and my eclipse setup simply works I finally came around to see and act upon our feature and bug tracker within eclipse. We are using the great Jira from Atlassian for our open source project Razuna and I read somewhere that they have a Eclipse plugin available.

As I found out soon is that the dedicated Eclipse Jira plugin is not working well (I guess they even stopped development), but that the Mylyn project works perfectly with Jira. Mylyn is a task-focused interface for Eclipse and can be used to track all your issues within Jira, Trac and Bugzilla. For Jira all you have to do is to enable a couple of things.

Install Mylyn in Eclipse

If you are using Pulse (why aren’t you?) then open up the Pulse Explorer and add Mylyn to your profile. Just adding Mylyn won’t do it as the related plugins have to be installed as well. Simply click on the “plus” sign and choose the ones you need.

Then just do a “Run” and Mylyn with the related plugins will be installed. Since we are using Pulse your profile has just been updated and this setup is available to you, and if you share it, anywhere.

Setup Jira to allow RPC calls

To make Mylyn work with Jira you will have to allow RPC calls to Jira. If you did a default installation the RPC plugin should already be installed within Jira. Just make sure that it is also enabled!

Enabling the plugin is not enough. You will also explicitly have to enable RPC API calls to Jira by going into the “General Configuration” and enable “Accept remote API calls”.

You can test that RPC calls work when you go to the following URL for your Jira installation:

http://myjiradomain.com/rpc/soap/jirasoapservice-v2?wsdl

If you receive a XML page all should be good to go.

Jira within Eclipse

Now start up Eclipse and choose “Window / Show View / Others”. From the Explorer choose Mylyn and Taks List and/or Task Repositories. From now on it is simply a matter of setting up Jira parameters. Simply add a new repository and connect to Jira.

Once done you will be able to see all your issues within Eclipse, add a new issue, edit existing ones and so on. The cool thing about it, is that the plugin recognizes your saved searches and displays the issues according to your filters!

This all totally integrated into your editing workflow. I love it.

There is also a dedicated page from Atlassian available that walks you trough all installation steps for other Eclipse versions.

Comments { 40 }

I just did the best thing to myself and my development environment with Eclipse

As some of you might know by following on Twitter I “switched” from a MacBookPro to a MacBook, but actually I don’t want to bore you with that (even if I love to talk about the new MacBook). This post is about how I saved myself some sanity for my development work in regard to my favorite environment, that is Eclipse.

While transferring all my stuff over to the new MacBook (yes it works without Firewire, either use a Ethernet cable or Wireless) all went very well (if you don’t mind reinstalling all the stuff you got with MacPorts, it was time for a reinstall anyway).

So I was about to start some real work again, I was confronted with a ugly update error message by Eclipse 3.4 that went along the lines of:

“…One or more bundles are not resolved because the following root
constraints are not resolved… …equinox.p2….”

and so on. Apparently, there is a new update out to upgrade to 3.4.1. Since I am more or less a update junkie (and the update solved some issues I was having) I wanted to upgrade immediately. As it turns out I could not find anything to solve it. Worse, after some time the Update Manager did not even start anymore and I got a messages saying “Cannot launch the Update UI….”.

Before getting myself into more troubles, I was looking for a alternative to my “disaster”. Well, it did not take long when I found out about “Pulse“. Pulse makes it very easy to manage all Eclipse versions and plugins in one simple tool.

With Pulse I was able to install “any version (Europe or Ganymede)” multiple times each with different setups and configurations. Pulse is a free tool (you can use it free or use it with a free registration) and also has a subscription service which allows you to distribute your profile within the company and other nice features.

I can’t remember how many times I had a problem with Eclipse and such Pulse will be my companion from now on for Eclipse. Make your dev life easier, give yourself a Pulse. (no, I am not affiliated with them, just very happy to have found this great tool).

Comments { 57 }

Migrate from Subclipse to Subversive on MacOS X

For many years I have been using Eclipse with the fine Subversion plug-in. Since I have updated my Eclipse to the Ganymede release (Version 3.4) I unfortunately run into one problem after another. Especially the SVN Repository browser failed to work most of the time.

So, after putting up with this situation for the last 2 months and applying all Subclipse updates in the meantime (and still no working 100%) I decided that I will give the Subversive plug-in a go. This is not a blog post favoring one or the other, but simply what is working for me and proves to work.

I have over 20 projects in different SVN repositories and thus I was eager to find out how to migrate my projects the best way. I looked all over the web, but only found some confusing information or nothing at all (excuse me if anything is available but honestly could not find it).

Thus I thought I publish my steps here:

  1. We assume you already have subclipse installed, thus go to “Help/Software Update”. In the following window click on “Installed Software” and scroll down until you see all installed “Subversion” plug-ins.
  2. Uninstall all “subclipse”, snv and JavaHL plug-ins, except “Subclipse” itself.
  3. Restart Eclipse.
  4. Go to each project that you have in subversion and do a right click, choose Team and then click on “Disconnect…”. Make sure that you keep your project settings.
  5. Restart Eclipse.
  6. Now uninstall Subclipse.
  7. Restart Eclipse.
  8. Now you are ready to install Subversive. Do do that you open up “Software Update” again. Navigate to the “Ganymede” tree and choose under “Collaboration Tools” the Subversive plug-in. These are called “SVN Team Provider” and is a bit confusing at first, but rest assured it is the Subversive plug-in.
  9. Once that is installed you will also need to add the SVN connectors. Due to some licensing issues you will need to grab them from a different site. Within the “Software Update” window add a new site and enter the following URL “http://www.polarion.org/projects/subversive/download/eclipse/2.0/ganymede-site/”.
    Once that site is loaded you will see three categories. Open the “Subversive SVN Connectors” and select the “Subversive SVN Connectors” and the “SVNKit 1.2.0 ……..” one. The later is quite important since I could not get Subversive to work with most repositories by selecting the “SVNKit 1.1.7 implementation” one. But the “SVNKit 1.2.0″ works just fine.
  10. Restart Eclipse.
  11. Now with each disconnected subversion project do a right click, select “Team” and then “Share Projects…”. You should then get a dialog asking you some questions about the Subversion project, mostly you have to enter name and password again and you should be all set.

So far, all is well. SVN repository browsing is still not 100% working, but at least I can connect most of the time and browse it. If that happens a reboot of Eclipse will get me back in the game.

I am sure there are other ways to do it, but this has worked fine for me and worked with all projects.

Comments { 67 }