Eclipse Ganymede

Posted in java by pedro | Thursday, August 23rd, 2007 at 9:06 am

Next version of eclipse IDE will be called “Ganymede”. The name is the third moon of Jupiter. The release date is scheduled on June 30 2008. Some features for M1:

  • Profiles with shared plugins : You can create multiple profiles, but all bundles are downloaded once.
  • 64-bit for Windows
  • Regular Expressions support in find/replace.
  • Replacing text now uses the same dialog as refactoring (preview, undo)
  • Ignore Resources (good for .svn or for target directory ;) )
  • Correct spelling in CVS so I guess SVN plugin do the same.
  • Drag text into Expressions, yea this is really cool feature
  • Extract Class from groups of fields.
  • Move block of code by drag and drop in Outline View.
  • Watchpoint for field access & modification

I’ll be waiting for next version ;)

2 Responses to “Eclipse Ganymede”

  1. [...] time ago I write about next Eclipse version called Ganymede. Also some time ago I have switched to Mac and InteliJ IDEA. The reasons was that eclipse has poor [...]

  2. [...] Saulės sistemoje. Vizualiai keičiasi naujosios versijos pradinis langas, funkcionalumo pakeitimai čia. Planuojama išleidimo data – 2008 birželis. Categories: dev, java, tools Tags: [...]

Leave a Reply

about me

My name is Sebastian Pietrowski. I've finished Warsaw University as Master degree. I started my journey with Java 1.1 with Thread and JDBC programing in 1998 as I worked for merlin.pl. In 1999 I've passed Java Programer Certificate for Java 1.2, and was solution architect of merlin.pl infrastructure when we was moving from pl/sql to J2EE. It was great performance optimization with 10 times more req/sec than in requirements and 85 times faster as original solution.

Currently I work as Expert Software Development Java at F.Hoffmann-La Roche. The company was founded in 1896 and today, Roche employs over 80.000 people. After work I'm involved in activities related to Scala/Lift, Ruby/Rails/Merb, Python/Django. This is because I try to be pragmatic also I'm focused on application performance and tuning with success in my daily work.

My Yoda's motto: Do, or do not. There is no try.