Skip to content

Random thoughts whilst setting up a Java project in Eclipse on Snow Leopard

January 16, 2010

I thought that it was about time that I set up my java dev environment on my macbook. Sure, I could keep coding on my desktop, but why do that when I can spend my whole life chained to the source code? Here’s a list of anything out-of-the-ordinary that I found whilst setting up my latest project…

Setting up Eclipse on Snow Leopard

So first things first, I need the Eclipse IDE (I use the version “for Java Developers”). Whilst there’s only one version for Windows and two for Linux, there are three for Mac (because it’s three times more awesome than Windows, right?). Which one to choose? According to the very aptly named Either You Succeed Or You Explain blog, Snow Leopard users should choose the 64bit Cocoa version. So I have.

If you haven’t used Eclipse before, you might be surprised to find that the .tar.gz file you’ve just downloaded doesn’t contain an installer, just the program itself. Just drag the folder to somewhere suitable, then drag the eclipse program from there to the dock and you’re done.

Installing the Subversive plug-in

If you’re using subversion (which you should), you’ll want to install the Subversive plug-in. In Eclipse, go to Help > Install new software, and search the Galileo update site (top of the pull-down list) for Subversive. Install the Team Connector (but not the optional “for Mylyn projects”, unless you need it). Eclipse will restart, then right click on your checked-out-from-svn project, Team > Share Project, and a box will pop up for you to configure your connectors (you only have to do this once). I’m using “SVN Kit 1.3.0”. Eclipse will now get a bit confused, as the installation of the plug-in happens in parallel to your earlier attempt to Share [your] Project. Eclipse will restart once again (provided you click on “yes”), then you can have another go at right clicking on your checked-out-from-svn project, Team > Share Project. The rest should be fairly self-explanatory; post a comment if these instructions suck…

Linking your Check-in comments to your Issues on Google Code

Whatever you’re doing, you’re hosting the code in version control, right? We use subversion and trac in work, and can add comments to our svn check-ins that appear in our trac tickets. It turns out that you can do exactly the same thing with google code, and if anything, their check-in messages are even more powerful. I look forward to trying them out on my jade-oo project.

No comments yet

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: