The above XML apparently only works when the POM's packaging is jar. When
I execute this POM from a parent POM, who's packaging is pom, the optional
ant task jar files are not included in and the ant tasks blow out w/ an
error. I can only exec mvn install in the same directory which has the POM
STOP sending this email. You've sent it four times in 12 hours.
If someone feels like responding, they will.
Wayne
On 3/10/08, gotama [EMAIL PROTECTED] wrote:
The above XML apparently only works when the POM's packaging is jar. When I
execute this POM from a parent POM, who's packaging is
I just found that this is a bug:
http://jira.codehaus.org/browse/MANTRUN-51
In a multi-module project, the ant plugin dependencies are lost.
The 'workaround' is the place the ant plugin dependencies in the 1st module
despite if you actually need the ant plugin there, simply to load the
, March 10, 2008 2:08 PM
To: users@maven.apache.org
Subject: Re: running optional ant tasks with maven-antrun-plugin
I just found that this is a bug:
http://jira.codehaus.org/browse/MANTRUN-51
In a multi-module project, the ant plugin dependencies are lost.
The 'workaround' is the place the ant
Maven does not know about your ANT_HOME, nor does it use Jars from
your ANT_HOME.
To use optional Ant tasks, you must declare them as dependencies of the plugin.
build
plugins
plugin
dependencies
dependency...
Wayne
On 3/4/08, gotama [EMAIL PROTECTED] wrote:
How can I run optional ant tasks
Awesome... thanks. That did the trick... Here is the final config fyi...
Remotely stops JBoss, copies over a new EAR file and remotely starts JBoss:
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
dependencies
