Community
Participate
Working Groups
We need to review the Ant/Ext Tool API. * we need an Ant UI plug-in * all extension points need doc
Note that an Ant UI project already exists in the Eclipse repository.
Plan for 2.1 is to have no API and no separate plug-in. We will make all packages internal.
We should do this ASAP, to see if we break any of our users. Dejan - which class (es) do you use in External Tools (to run ant scripts)?
Darin, there are lots of users that have talked about using org.eclipse.ant.core.AntRunner (I believe this is most of Dejan's uses as well). Although it has never explicitly been published as API, I think it would be a mistake to suddenly change the package structure. Can we not just add the caveat in the class javadoc like debug had for 1.0? This leaves no solid API but doesn't break anyone who has been building plugins on top of ant core.
We use AntRunner but not external tools.
We are only changing external tools to internal - not ant core.
All of the external tools packages have been changed to be internal. plugin.xml updated Nls message accessor classes updated. None of the ant packages have been changed Please verify (DarinW).
Verified