When Eclipse Galileo (3.5) was released a while ago, I quickly upgraded to it to try it out, but found a number of incompatibilities with plugins I was using at the time. I rolled back to Ganymede (3.4) and have been using it ever since. However, I recently upgraded my machines to Snow Leopard and with that came the option of only one Java environment, 1.6. You can install Java 1.5, but it’s already past it’s end of life, so decided to move on. This is fine, since I’ve been building and running Sakai with Java 1.6 for over a year now.
Today I came up against a new issue though. The Sakai App Builder, which I’ve done some work on to make compatible with K1 builds, was refusing to start up:
java.lang.UnsatisfiedLinkError: Cannot load 32-bit SWT libraries on 64-bit JVM
I scratched my head for a while but then it clicked, Ganymede is 32 bit and Snow Leopard is 64 bit. I checked the Eclipse download pages and sure enough, Ganymede is only available in 32bit for OS X. Galileo however, is available in both 32 and 64 bit for OS X.
So I took the plunge and upgraded to Galileo 64 bit. First impressions, it looks nice. It’s based on Cocoa so a few little UI things have changed. Most noticeably in the Package Explorer view, the icons and text are a bit smaller so you can see more. This is great because Profile2 has 11 modules and expanding any of those soon eats up real estate.
I’m a bit of a traditionalist and prefer to do things like Subversion and Maven builds on the commandline (having multiple screens helps here), hence don’t use plugins like Subclipse or any Maven plugins so can’t really comment on their compatibility, although am interested to hear your experiences.
So far I haven’t found any abnormal behaviour with Galileo in regards to Sakai, but will report back if I do.
Here are my relevant JVM settings in Eclipse.app/Contents/MacOS/eclipse.ini: