On Tue, Feb 26, 2008 at 5:07 PM, Marshall Schor [EMAIL PROTECTED] wrote:
Dennis Lundberg wrote:
...
There is an issue for this in JIRA already:
http://jira.codehaus.org/browse/MANTRUN-68http://jira.codehaus.org/browse/MANTRUN-68
I see that issue is more than a year old, and is
We need to have the maven ant run plugin to run ant at version 1.7.0.
How should this be specified?
We tried putting in the POM:
plugin
artifactIdmaven-antrun-plugin/artifactId
dependencies
!-- Ant --
dependency
version1.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.
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).
Wayne Fay wrote:
version1.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.
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
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
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
Dennis Lundberg wrote:
...
There is an issue for this in JIRA already:
http://jira.codehaus.org/browse/MANTRUN-68http://jira.codehaus.org/browse/MANTRUN-68
I see that issue is more than a year old, and is still open.
Until this is fixed, is there a recommended work-around?
-Marshall
