Wayne Fay wrote:
<version>1.7.0</> is merely a strong suggestion to Maven.
<version>[1.7.0]</> will fail the build if it is unable to acquire
this artifact
Further investigation shows these dependency statements added ant to the
"compile" <scope> - I think this has nothing to do with what ant-run
uses. I tried adding <scope>runtime</scope> but that didn't work either.
As for the missing 1.7.0 jar files, please ask the Ant team to upload
them, or move them to a shared sync directory etc (depends on how they
have set this up).
Further investigation shows the jars for 1.7. 0 *are* in the
http://repo1.maven.org/maven2/ but not under "ant" but rather under
"org" (that is, org/apache/ant/... etc.)
So the real underlying problem is the mechanism I tried for the ant
dependency is not working to specify the ant version to use for the
maven running. I think that's coming from the maven-antrun-plugin.
This plugin has these pom entries:
<dependency>
<groupId>ant</groupId>
<artifactId>ant-launcher</artifactId>
<version>1.6.5</version>
<scope>runtime</scope>
</dependency>
−
<dependency>
<groupId>ant</groupId>
<artifactId>ant</artifactId>
<version>1.6.5</version>
</dependency>
Is there a way to get maven-ant-plugin to use ant 1.7.0 level?
-Marshall
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
