I'm happy to support Ant 1.5 when it's released. That's not far away, but most builds these days are done with 1.4.1, and we need to support the most common build environment.
Which issues, other than javadoc do we have with jdk 1.4? I'm running it at the moment, and that's my only hassle. Re: the J2EE Plug-in/Ant 1.5 dependencies, I 'fixed' those on the weekend, let me know if it's broken. I'm happy that Ant 1.5 support will be pretty easily done, as my experience with it is proving fairly seamless. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers Kevin O'Neill <kevino@jacus. To: Turbine Maven Developers List com.au> <[EMAIL PROTECTED]> cc: 05/27/02 10:53 Subject: Re: Will Maven's final release be Ant 1.4.1 compatible? AM Please respond to "Turbine Maven Developers List" Peter, > It might be a tad early to ask, but what is the plan for supporting 1.4.1 when > Maven is finalized? Will it start at Ant 1.5? > > Just see a need for an http condition in some stuff I'm hacking with and > wondered if I'll have to write my own task. I've been arguing for some time that maven should be designed for 1.5 as opposed to 1.4.1 Mostly this is due to jdk 1.4 compatibility problems with 1.4.1 and additional tasks I used in the ejb portion of the j2ee target. See my earlier post on the subject and the followup regarding gump results using ant 1.5. http://www.mail-archive.com/[email protected]/msg00937.html -k. -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED]> For additional commands, e-mail: < mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
