Community
Participate
Working Groups
I'm opening this bug simply to track the possibility that the Platform may move to Ant 1.8.2 in Indigo M6. See their bug 302296. I'm not sure if this effects us, but know a few teams use or depend on ant, so thought we could track any impacts here ... especially since possibly coming "last minute" in M6 (instead of early in dev. cycle). So, if anyone has any comments/preferences/suggestions, please comment. (here and/or in platform bug ... especially if there is some negative impact). I did a quick search of what I happened to have loaded, and appear the following bundles make use of "org.apache.ant" in their manifest.mf files. MANIFEST.MF - org.eclipse.jst.server.generic.core/META-INF MANIFEST.MF - org.eclipse.jst.ws.axis.consumption.core/META-INF MANIFEST.MF - org.eclipse.jst.ws.axis2.core/META-INF MANIFEST.MF - org.eclipse.jst.ws.axis2.creation.core/META-INF MANIFEST.MF - org.eclipse.wst.command.env/META-INF MANIFEST.MF - org.eclipse.wst.wsdl.validation.tests/META-INF MANIFEST.MF - org.eclipse.wst.wsdl.validation/META-INF MANIFEST.MF - org.eclipse.wst.xsl.core/META-INF
The platform has been updated to consume Ant 1.8.2 as of 2/8/2011, although I would recommend using the I-build from 2/15/2011 as there was an issue found with the Ant editor (bug 336936). > So, if anyone has any comments/preferences/suggestions, please comment. (here > and/or in platform bug ... especially if there is some negative impact). For any problems (performance or otherwise) with Platform Ant support, please open a new bug (Eclipse => Product: Platform, Component: Ant)
I've tried running the web service ant smoke test scenarios of this weeks 3.3 smoke test and didn't encounter any problems.
We'll count this as "done". No changes required to any code and no issues found. We did convert to use Ant 1.8.2 during our builds, with no problems, but did discover the "created-by" directive in manifest.mf files are slightly changed (technically, for the better, but does cause noise in our "comparator reports". This (small) issue is tracked in bug 338039. Thanks all.