> > With ANT 1.5 now being beta and, in my experience, stable. What are the > > impediments to Maven switching to ANT 1.5? > > -1 > > I would rather only rely on released versions of Ant and since Maven is used > to build other projects which only do the same, then I think that forcing > people to move to 1.5 before it is released is a bad thing.
A quick scan of the ant user mailing list archives turned this up: "I'm running Gump (<http://jakarta.apache.org/gump/>) with Ant's 1.5beta branch to see whether 1.5beta breaks any builds <http://cvs.apache.org/~bodewig/gump/>. Up to now I haven't found any 1.5 specific issues, but then again I haven't been able to build Tomcat 4 because xdoclet's current CVS HEAD branch is broken." http://www.mail-archive.com/[email protected]/msg16504.html http://cvs.apache.org/~bodewig/gump/20020522/ shows a dvsl dependency failure (dom4j) that looks like a dom4j HEAD build problem. Alternatively what about some way of allowing plugins to specify a 1.5 dependency. This way people like me that require 1.5 features could use a different compile or javadoc plugin? This splits the code base a little but might be an acceptable compromise. -k. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
