on Nov 2nd, 2009Eclipse 3.6 M3 (Helios) available for download
Milestone #3 for Eclipse 3.6 is now available for download.
Here are the noteworthy changes up this milestone:
My favorite change is the new support for software installation while running & debugging. This should be a huge time-saver for all developers who are adding p2 support to their RCP apps. It permits to do install operations in a launched application. Previously this was only possible after regularly deploying the RCP application via the export wizard.
Related posts:
Glad to hear you like it Elias.
The PDE team is working on slicker p2 integration in the next milestone. The whole target should be managed by p2 by the end of the Eclipse 3.6 M4 release.
Look for functionality that allows you to easily add things to your targets.
Maybe it’s just me, but I am still waiting for some eclipse release where code autocompletion does not suck. I mean, IntelliJ had a nice implementation since day 1, but eclipse lags far behind. It’s not that hard!
* If I write the name of a method and the parameter name is “eventParam” and I have a local variable named param declared two lines ago, propose that instead of the “fooChild” attribute of the class, or, even worse, nothing at all.
* If I write some expression that happens to have some ‘(‘ included, do not overthink and move my cursor somewhere else because a [return] key was detected. Multi-line expressions exist!
* Alt+Ctrl+J inside a comment does not handle the extra ‘*’ properly, as [return] does.
Please don’t get me wrong, I like eclipse but this is the bread and butter of coding and it’s like nobody cares.
Ignacio,
thanks, these are all good suggestions.
The best way to see this happen is to file individual bugs against the JDT (Java Development Tools) component (see link below). This way the committers working on this will be made aware of your ideas. This would be the first step towards having something in the next version. Right now the timing is good, since the feature freeze is still 4-5 months away. The second step would be to work with them and write some code that addresses these issues. Eclipse is free and therefore depends heavily on community bug and code contributions to continue getting better.
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=JDT
Kind regards,
Elias.