Upgrading Eclipse? Time to try Callisto.

by Tim O'Brien

Try the latest Callisto Release Candidate




Whenever I upgrade Eclipse, I'm tempted to download the latest development release. Instead of clicking on the production release, I tend to look for other versions and download the latest release candidate or integration build. I've been running a Eclipse 3.2 integration build since last November, and it worked so well I forgot that I was using an early integration build. I finally upgraded this week, and in doing so I decided to try the latest release candidate of the Callisto Simultaneous Release. Verdict? It's official, Eclipse is no longer just an IDE, it is a powerful platform, and I was surprised at the breadth and quality of this release. Read on for an account of my own experience.


12 Comments

Paul Browne
2006-06-11 11:16:50
Tim,


Good post , thanks for reminding me - I'd blogged about Callisto Earlier and was looking forward to it coming out.


Paul , Technology in Plain English


2006-06-19 21:08:52
I just hope Eclipse will get on a diet and consume less of my machine's memory. And now it is getting even fatter by combining stuff that I don't need.
Reini
2006-06-19 22:54:13
Dear Anonymous, you can select the components that you are interested in.
Mr Macintosh
2006-06-20 05:52:20
I cannot agree with this. I have done exactly as you have in this article, upgrading to the latest+greatest via the update manager and have experienced lots of exceptions.

2006-06-20 05:54:31
Call me an "old fart" but I still find that a copy of Emacs and an xterm to be a far more productive and stable environment.
morangatang
2006-06-20 06:49:22
Thanks for the reminder that Callisto is almost ready for final release.


BTW: It might help to identify what platform you're running, and what components you installed successfully (Tim) or unsuccessfully (Mr Macintosh). People won't "buy in" until you show them Eclipse can work in their shop (i.e. the boss who hasn't coded in years, or that dude who thinks a text editor is more productive for coding.)

Tim O'Brien
2006-06-20 06:52:39
re: morangatang


Using Willy G's OS: Windows XP

Randy Strauss
2006-06-20 17:52:43
I thought I'd stick to emacs, but the instant compilation and popup lists of classes/fields/methods are huge time-savers, especially in a large product built by others. Add the excellent debugger and I vastly prefer eclipse. It would be nice to have an emacs keyboard interface, though.
Frank Edwards
2006-06-21 14:57:44
I agree with Randy. I'm a vi bigot myself (although I actually use vim) and I thought I had what I needed with syntax highlighting, split screen, and so on. But Eclipse's debugger is very nice (I particularly like being able to step into the JRE source by pointing the IDE to the top-level directory), and I can easily switch between 1.4 and 1.5 for testing purposes.


I've had problems in the past with the VisualEditor, though, and I haven't been able to get the modeling tool to work (the way I think it is meant to); I'll have to grab a RC version tonight and try it again. :)

Tim O'Brien
2006-06-21 15:00:35
I'm a big Eclipse user, but I still keep emacs around for a lot of command line work I need to do. I don't see myself ever abandoning emacs (or vi), but I find myself unable to program Java without code completion and method completion.


The Rails IDE I use is RadRails - it is based on Eclipse. So it is interesting to see Eclipse which is a Java-based tool emerging as a cross-language development tool. Isn't it?


2007-01-06 17:50:26
this is stupid
Tim O'Brien
2007-01-06 18:21:38
re @Anonymous,


Thanks for the great feedback