I'm a Maven newbie, but it's not obvious to me that the proposed change will do what I think we need. It sounds like this change applies the overrides when you *generate* the build.xml file -- so the overrides in effect will be for those of the person running the generation.
In Commons, we've been having someone do the generation, and then check in the generated build.xml file, so that Commons users who like Ant can build the packages in the usual way. In the generated build.xml file, it would seem that the paths for <get> methods would still be hard coded (either the default ones or the overrides for the person who did the generation), wouldn't they? Also, which version of Maven will include the fixes listed on this issue? Craig On Wed, 1 Dec 2004 12:54:31 +0800, Brett Porter <[EMAIL PROTECTED]> wrote: > Quoting Craig McClanahan <[EMAIL PROTECTED]>: > > > It would be really nice if the generated build.xml produced by Maven > > would allow Ant property replacements for the paths to all the > > dependencies, instead of hard coding them, so you could just define > > your exceptions in a local build.properties file. > > http://jira.codehaus.org/browse/MPANT-7 > > This *should* do what you want (specify ${libdir} in ant and put all your > non repository stuff in there). > > Cheers, > Brett > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
