Eclipse Ganymede - 18 Million Lines of Code Delivered on Schedule
For many people, the Ganymede release is the new Eclipse Platform 3.4 release, including the new p2 provisioning platform, Equinox security features and JDT improvements. However, with 23 projects there are many other things to highlight, like the new Ecore modeling tools, the new SQL Query Builder in DTP, new C/C++ refactoring tools in CDT, the very cool pair programming tools from ECF, a SOA SCA Designer and Policy Editor in STP and many more highlights. The Eclipse Foundation is also encouraging people to blog about their own Ganymede highlights, so check out the Ganymede Around the World map to see what other people think is cool in Ganymede.
To get started on Ganymede, download one of the packages that have been created by the Eclipse Packaging Project. We will also be releasing a number of short videos and webinars on Eclipse Live that highlight the new features in each project.
Congratulations to everyone in the Eclipse community that made Ganymede happen. It is really a great accomplishment to ship over 18 million lines of code on a date that was scheduled close to 12 months ago.
Article Type:
Opinion/Editorial
(5 votes)
- Login or register to post comments
- 10728 reads
- Email this Article
- Printer-friendly version
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)







Comments
Andrew McVeigh replied on Wed, 2008/06/25 - 10:29am
Peter Mularien replied on Wed, 2008/06/25 - 11:00am
Link to download
Ganymede Release Info
For whatever reason, I didn't notice any links in the original article, so I hope these help some people.
Ian Skerrett replied on Wed, 2008/06/25 - 11:24am
in response to: pmularien
Peter,
Not sure what happened to the links; I've added them to the article too. Thanks for pointing it out.
Ian
Ian Skerrett replied on Wed, 2008/06/25 - 11:25am
in response to: andrewm
Jim Bethancourt replied on Wed, 2008/06/25 - 12:31pm
in response to: andrewm
I remember seeing a JavaPolis talk on video given by Erich Gamma on how they use a Shipping Culture approach. I think this is the link:
http://www.javalobby.org/av/javapolis/JPVideoPlayerV3.swf?content=/av/javapolis/university/Erich%20Gamma/eclipse.xml?version=1
He explains the development approach they take and how each team develops agains the previous releases of all the other teams, and if a team doesn't release, they don't ge to participate in the next release plan.
The best quote from the talk is definitely "We get ship done".
Cheers,
Jim
Jesse Sightler replied on Wed, 2008/06/25 - 12:39pm
Andrew McVeigh replied on Wed, 2008/06/25 - 6:09pm
in response to: jimbethancourt
i can see this working (e.g. building on previous releases) for non-breaking changes (e.g. 3.4 to 3.5). I wonder how they handle the ripple effects of breaking changes (e.g. 3.5 to 4.0) say. Breaking changes tend to have a ripple effect.
Andrew
Artur Biesiadowski replied on Thu, 2008/06/26 - 2:48am
in response to: jsight
You can find it at
http://ganymede-mirror1.eclipse.org/eclipse/downloads/drops/R-3.4-200806172000/whatsnew3.4/eclipse-news-all.html
It is still available if you go to main eclipse site, then chose downloads and then release notes.