Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0.9
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: Plugins and Lifecycle
-
Labels:None
-
Complexity:Intermediate
Description
In this example antrun:run is excuted after dependency:copy-dependencies by virtue of plugin order. Preferable would be an explicit order definition. For example, a plugin could export a 'phase-id' that another uses in its 'phase' element.
<plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <executions> <execution> <id>copy-dependencies</id> <phase>package</phase> <goals> <goal>copy-dependencies</goal> </goals> <configuration> <outputDirectory>${project.build.directory}/thirdparty</outputDirectory> <stripVersion>true</stripVersion> </configuration> </execution> </executions> </plugin> <plugin> <artifactId>maven-antrun-plugin</artifactId> <executions> <execution> <phase>package</phase> <goals> <goal>run</goal> </goals> <configuration> <tasks> <ant antfile="ant/build-concat.xml"/> </tasks> </configuration> </execution> </executions> </plugin> </plugins>
This issue probably applies to plugin execution in general, not just antrun