[ http://jira.codehaus.org/browse/MANTRUN-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130732#action_130732 ]
Thomas Diesler commented on MANTRUN-89: --------------------------------------- This issue probably applies to plugin execution in general, not just antrun > Cannot define execution order explicitly > ---------------------------------------- > > Key: MANTRUN-89 > URL: http://jira.codehaus.org/browse/MANTRUN-89 > Project: Maven 2.x Antrun Plugin > Issue Type: Bug > Reporter: Thomas Diesler > > 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 message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira