I would like to ask about the current state of the Groovy compiler integration with JDT.
AFAIK, JDT has to be patched for each Eclipse release to integrate the Groovy compiler with the regular JDT functionality. As this is a major effort, this usually happens only towards the end of a release, which is also, why Groovy Eclipse for Kepler still ships with a JDT 3.8-based compiler, right?
Bug 36939 in Eclipse Bugzilla ("Improve support for Java-like source files", ) contains a long discussion started in 2003 about making a integration of JDT with other languages (AspectJ, Scala, Groovy, ...) possible in order to reuse all the goodness of JDT. Now that Andy Clement is a JDT committer, is there new hope for progress?
I usually like to keep up to date with Eclipse milestones, but as we need Groovy Eclipse for our application, I always have to wait until the Groovy compiler has been updated to the new release. With an out-of-the-box integration not requiring feature patches this would not be a problem any longer and as a positive side effect it would be also possible to use multiple languages in one workspace with the same Eclipse installation.
Looking forward to a bright future of JDT with other languages :-)
Re: State of Groovy compiler integration with JDT?
> AFAIK, JDT has to be patched for each Eclipse release to integrate the > Groovy compiler with the regular JDT functionality. As this is a major > effort, this usually happens only towards the end of a release, which is > also, why Groovy Eclipse for Kepler still ships with a JDT 3.8-based > compiler, right?
I wouldn't say we consciously schedule that work at a particular time.
Originally we provided the patch on the same day the eclipse version
came out but recently we haven't had time. However, we are currently
testing the patched 3.10 JDT (Java8) so that will be available next week
when Java8 comes out.
I am a JDT committer but whilst a few of the changes that Groovy-Eclipse
and AspectJ make to JDT could be put into JDT as is, some of them are
still too dirty ('hacks' if you like) so would need a bunch of refactoring
before they'd be properly allowed in. Finding time to do this refactoring is
Perhaps more realistically the patching could be made automatic with no human
interaction required (unless it goes wrong) - like ObjectTeams does and
then simply integrate it into the build process. This could be done for both
the JDT patch and the groovy patch (Groovy patch
is slightly trickier due to grammar merge being required).