[jira] Commented: (MANTRUN-52) plugin dependencies seem to get lost when using the plugin multiple times

["Christoph Grothaus (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MANTRUN-52?page=comments#action_66709 ] 

Christoph Grothaus commented on MANTRUN-52:
-------------------------------------------

This error also occurs in a reactorized build. Suppose you have a multi module maven setup like
main/pom.xml
main/A/pom.xml
main/B/pom.xml
where A and B are subprojects that have main as parent. Both A and B use the antrun plugin with plugin dependencies. If the reactor sort order is Main->A->B, then the antrun plugin of B will fail because it does not see the correct dependencies (it sees the antrun plugin dependencies of A, not those of B).

> plugin dependencies seem to get lost when using the plugin multiple times
> -------------------------------------------------------------------------
>
>          Key: MANTRUN-52
>          URL: http://jira.codehaus.org/browse/MANTRUN-52
>      Project: Maven 2.x Antrun Plugin
>         Type: Bug

>     Versions: 1.1
>     Reporter: Jorg Heymans
>     Priority: Critical

>
>
> say in the same pom you have
>   <build>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-antrun-plugin</artifactId>
>         <executions>
>           <execution>
>             <configuration>
>               <tasks>
>                 <replace dir="${project.build.outputDirectory}"
>                   replaceFilterFile="${basedir}/src/main/properties/replaceSchemaNames.properties" />
>               </tasks>
>             </configuration>
> ............
>   </build>
> and 
>   <profiles>
>     <profile>
>       ....
>       <build>
>         <plugins>
>           <plugin>
>             <groupId>org.apache.maven.plugins</groupId>
>             <artifactId>maven-antrun-plugin</artifactId>
>             <executions>
>               <execution>
>                 <id>Database recreation</id>
>                 <configuration>
>                   <tasks>
>                     <sql ..../>
>                   </tasks>
>                 </configuration>
>                 <goals>
>                   <goal>run</goal>
>                 </goals>
>               </execution>
>             </executions>
>         <dependencies>
>           <dependency>
>             <groupId>oracle</groupId>
>             <artifactId>oracle-jdbc</artifactId>
>             <version>1.4_g</version>
>           </dependency>
>         </dependencies>
>           </plugin>
>         </plugins>
>       </build>
>     </profile>
> then the antrun configured in the profile will fail saying that it can't find the oracle driver. If i move the oracle dependency to the plugin configured in <build> then it works. 

-- 
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