> May I ask you a favor and lead me to a document describing how we can make > maven using our own ant 1.7.1, > as we had changes in ANT 1.7.1 specifically for OpenVMS, those catching > logical, and generating a temporary > file where all the many hundred arguments being passed today to JAVA / JVM > are stored in.
I already told you what to do but here are the complete steps: Decide on a version string that you will use for your version of this Ant build (if 1.7.1 is the base, I might call yours 1.7.1-AXA). Make your own version of Ant's binaries (supposedly you've already done this). Install those binaries into Maven's cache using the "mvn install" command with proper parameters. Note: this install step will need to be performed on every system and across every user account that utilizes these modified Ant binaries since you are not using a Maven Repo Manager. Change you pom files to refer to this specific version of Ant using <version>[your.version.here]</version>. Execute your build and watch Maven use those Ant binaries instead of the default. It really is that simple. > can we make maven use our ant by changing pom.xml or better have a more > global approach/setup such as in a settings.xml? The global approach involves a parent (corporate) pom that specifies the Ant version and which you inherit in all your children poms. And ideally you'd have Nexus installed and your various Maven instances pointing to Nexus for artifacts so you didn't need to manually install them everywhere. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
