I'd really like to see something where (take collections for instance) maven.xml uses the ant build.xml script to either pregoal,goal,postgoal the dist goal, this way collections can maintain their unique builds but they can all be exec'd within maven too.
I'm not sure about the top level jakarta-commons/build.xml, we should review its usage and see whos using know days.
-Mark
Henri Yandell wrote:
Cool, what I was hoping [or hoping not to] find out :)
Will ensure that I don't remove things.
Hen
On Sat, 15 May 2004, Stephen Colebourne wrote:
I'm under the impression that all of our releases are now cut using Maven, so I'd like to mavenise [as such] the release instructions so they make some sense in the modern context.
By all means add maven stuff, but please don't delete ant references.
Am I correct in this? Is there any reason to keep the old build.xml's, or should we maven ant in each project and push in each maven generated build.xml.
collections builds multiple targets now within the ant script, and I'm not in the mood of trying to get maven.xml to work.
Stephen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
