ant & maven.xml

[Brett Porter]

Hi,

I was just wondering what thoughts there are on how the content of maven.xml could be included in the generated ant scripts, or whether this is a good goal to obtain.

The reason I ask is that it appears ant is faster to execute (and always likely to be) because of a lower overhead - correct me if others experience it differently.

I'd like to use maven for all of our full builds and whenever there are property changes, but ant whenever I change only a java file, or a jsp file. This means you could generate the ant script by "executing" the jelly script and writing out what would have been run in ant I think. Even then, the definition will be fuzzy because some properties will be used in jelly, and some only filtered, so sometimes you'd need to run ant and sometimes maven. Anything that relied on a plugin (eg XJC now) would also require maven.

I'd just like to know what the thoughts are on this in the interest of speeding up the build process for smaller tasks (although console/wizard are also good alternatives), as well as utilising existing ant frameworks/IDE plugins. At the moment, most of my stuff I've mavenised won't completely build in ant because of necessary preGoals or postGoals.

Thanks,
Brett


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>