Project Documentation

Maven Projects

Usage

Run

The maven-antrun-plugin has only one goal, run.

This allows Maven 2 to run Ant tasks. To do so, there must be an existing project and maven-antrun-plugin must have its <tasks> tag configured (although it would still execute without the <tasks> tag, it would not do anything). Below is the template for maven-antrun-plugin's pom.xml.

Moreover, you can add a script to each lifecycle phase, by duplicating the <execution/> section and specifying a new phase.

Ultimately, you could specify some Ant <target/> attributes in the <tasks/> tag. Only depends attribute in Ant <target/> is not wrapped.

[...]
<configuration>
<tasks name="The name of the tasks"
if="The name of the property that must be set in order for this task"
unless="The name of the property that must NOT be set in order for this task"
description="A short description of this target's function">
<!--
Place any Ant task here. You can add anything
you can add between <target> and </target> in a
build.xml.
-->
</tasks>
<configuration>
[...]

Additional source directories

If your ant tasks generate additional source code that needs to be added to the build, you can use the build-helper-maven-plugin. The sourceRoot and testSourceRoot options of the antrun plugin have been deprecated.

Using maven properties

All of the properties available to maven are also available in the tasks configuration. However, you may want to call an external Ant build script using the ant task. To avoid name conflicts, only a subset of the properties are passed to the external Ant build. These include all properties defined in the properties section of the POM. It also includes prefixed versions of some of the commonly used Maven properties.

Ant Expressions to Maven Expressions Mapping

Some Ant expressions have their respective counterparts in Maven. Thus, one can simply invoke the corresponding Maven expression instead of using maven-antrun-plugin to avoid the unneccessary overhead.

maven-resources-pluginNote: Translate can specify its own tokens and can have a different encoding scheme for reading and writing files. maven-resources-plugin however uses the \$... annotation only and has only one encoding scheme for reading and writing