Wayne Fay wrote: > The easiest solution would be to "build" your own internal pom for > maven-antrunner-plugin and specify the ant 1.7 artifacts as > dependencies, then declare that plugin version number in your pom > where you need to run the ant 1.7 version. Your version would be > something like 1.1-SCHOR. > > Grab the source for m-a-p, edit the version to an internal version > specific to your company, edit the dependencies to org.ant.* and > version 1.7, and mvn install/deploy it (you can do this right now). > > Or post a JIRA against this plugin asking for a 1.7-compatible release > (but this will not happen overnight). > Thanks, Wayne. My "Company" is the Apache UIMA project in the incubator. We currently don't have a maven repository we're using, other than the main Apache ones. So I'm missing a solution that lets everyone working on Apache UIMA have a stable reproducable build...
A bit more investigation showed that if I make the dependency have <scope>runtime</scope>, then both the 1.6.5 and the 1.7.0 end up the classpath used for running the plugin. The problem is the "order" of these is arbitrary. So it's "unreliable". I thought I might be able to use the <exclude> maven element to exclude the 1.6.5 ant level - but I couldn't figure out how to get the exclude to apply to the dependencies in the maven-ant-run POM.. It seems to me that others might want to be able to specify what level of Ant to use with ant-run-plugin. So maybe the Jira I post should suggest a fix that makes the version of Ant used something that can be configured in the caller's POM. -Marshall --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
