if one of your modules _is_ the custom ant task (one of the modules is a
maven project that codes to ant api and contains the ant task), then you can
do this:
<plugin>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
...
<configuration>
<tasks>
<my.task> run special task defined in another
module</my.task>
</tasks>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>my.groupId</groupId>
<artifactId>my-ant-task-project</artifactId>
</dependency>
</dependencies>
</plugin>
the only thing I would wonder about is if the reactor inter-dependency logic
can correctly "see" that the "my-ant-task-project" needs to be built before
its consumers
--
View this message in context:
http://maven.40175.n5.nabble.com/Create-a-common-shared-task-for-the-maven-antrun-plugin-tp3346449p3346860.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
