JDT Improvements, Top Eclipse Indigo Feature #7

As we approach another Eclipse release — this time with over 46 million lines of code — I’m counting down the 10 Indigo features that I’m most excited about.

While I’ve been writing about OSGi, Eclipse Run-Time technologies and the power of the Eclipse technology stack, for many people Eclipse is simply a kick-ass Integrated Development Environment (IDE) for Java.  In fact, according to the most recent Eclipse Community Survey, over 75% of respondents indicated that their primary programming language is Java. It’s no wonder that improvements to the Java Development Environment (JDT) made it onto my Top 10 List (yet again).

There are improvements to Java tooling such as history for breakpoint conditions.

screenshot 103 JDT Improvements, Top Eclipse Indigo Feature #7

Static analysis improvements, such as the detection of methods that ‘could’ be static

screenshot 106 JDT Improvements, Top Eclipse Indigo Feature #7

screenshot 105 JDT Improvements, Top Eclipse Indigo Feature #7

Content assist improvements, such as the ability to introduce a new local variable with cast from within a code block

screenshot 107 JDT Improvements, Top Eclipse Indigo Feature #7

Navigation improvements such as jumping to a super implementation, and jumping to the return type.

screenshot 108 JDT Improvements, Top Eclipse Indigo Feature #7

And a Test Suite wizard that now supports JUnit 4.

screenshot 114 JDT Improvements, Top Eclipse Indigo Feature #7

 

In addition to this, the JDT team has started to add Java 7 support to Eclipse. However, since the Java 7 specification was not finalized in time for Indigo, Java 7 support is not yet available. The JDT team will  release an update once this work is completed (In September when Indigo Service Release 1 ships). Please see the following wiki page for the status of this work.

Kudos for all this work goes out to the JDT (UI, Core and Releng) team including: Deepak Azad, Benno Baumgartner, Tom Hofmann (nee Eicher), Markus Keller, Dani Megert, Kim Moir, Raksha Vasisht, Michael Rennie, Srikanth Sankaran, Ayushman Jain, Jayaprakash Arthanareeswaran, Satyam Kandula and Stephan Herrmann and Olivier Thomann.

For more information on the what’s new in the JDT and JDT Tips and Tricks, please see Deepak’s blog.

6 Responses to “JDT Improvements, Top Eclipse Indigo Feature #7”

  1. Olivier Thomann says:

    JDT/Core team also includes Ayushman Jain, Jayaprakash Arthanareeswaran, Satyam Kandula and Stephan Herrmann

  2. Dave Henderson says:

    You mention that the Test Suite wizard supports JUnit 4, but the screenshot shows the Test Case wizard, which I’m pretty sure has supported JUnit 4 Test Cases for a long time (at least it does in Helios)… Is this the wrong screenshot?

  3. Ian Bull says:

    @Olivier, thanks! I’ve updated the post.

    @Dave Good catch. That was supposed to be the ‘test suite wizard’. I’ve updated the post.

  4. Denys Digtiar says:

    NetBeans and IntelliJ IDEA already have support of java 7. It’s a pity that JDT team defer support till September. Late availability of JSRs sounds more like excuse. And the fact that final jdk7 release will be available for more than a month without proper support in eclipse can harm the community. Personally, If I decide to try java 7 before September, I will use IntelliJ IDEA Community Edition.

  5. Ian Bull says:

    I’m not sure if IntelliJ has a full ‘compiler’ shipped with it, but for legal reasons I doubt Eclipse is even allowed to ship a Java compliant compiler before the JSR has been approved. Anyways, I always suggest to people that they use the right tool for the job, and if Java 7 support is important to you before Sept. then IntelliJ seems like a reasonable choice.

  6. Denys Digtiar says:

    Well… Yes, I missed the full compiler issue. Now it sounds more reasonable.

    Right tool for the job is true approach.

6 responses so far

Written by . Published in Categories: EclipseSource News

Author:
Published:
Jun 14th, 2011
Follow:

Twitter LinkedIn Google+ GitHub