>….is going to need a crow bar, a couple of sticks of dynamite, and a lot of beer. I wasn’t surprised to see how closely tied to the JDT core and debug/launch UI that the Ant Launching support is. Mainly for the use of the JRE Tab and the Classpath Tabs, however what was a bit more surprising is how closely tied to JDT the ANT Editor itself is. I have no problem with JDT depending on ANT for some functionality, but it just seems wrong to have ANT depend on JDT for functionality, the two don’t necessarily need to go together.
The later has been an open request for the last 4 years and keeps getting pushed off, the latest comment being that it would be best to do during the e4 refactoring. However, I have the need now, not later to get this out for an XML IDE that I work on that is based on eclipse. I don’t want or need full JDT/Java editing support, just pieces to help run some applications. Ant is one of the applications, but the XSL Tools project also needs to leverage the JRE and Classpath tabs for the Java specific XSL processors like Xalan and Saxon.
Unfortunately, while it looks on the surface that the Ant related projects are their own separate packageble pieces, they actually are pretty heavily tied to jdt.ui and jdt.debug. One thing that could help here is if JDT could do something similar to what Web Tools has done. Create a set of Java Commons plugins, that contain the necessary standalone classes that are common to basic java runtime support. Some of this is in JDT Core, but that also contains a whole boat load of stuff that really isn’t necessary or needed in the ability to just do runtime and jre selection, or classpath.
How much work this would be I’m not sure, as I’ve only started scratching the surface, but it might be something I’ll fiddle with to see if I can get it down to basics of what is needed. There are a lot of use cases where having just the JRE and Classpath support for launching java application can be helpful, it’s hard to believe that this hasn’t been a more requested feature.
One other thing that could be done is to build the Ant editor off of the Web Tools XML editor, this already provides most of the editing functionality, but still would require some special handling for content assistance, and some ant specific functionality for variable handling.