[jira] Moved: (MPIR-191) Site Plugin modify Compile Plugin classpath

["Benjamin Bentmann (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MPIR-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann moved MSITE-469 to MPIR-191:
----------------------------------------------

    Affects Version/s:     (was: 2.1)
                           (was: 2.0-beta-7)
                       2.1
                  Key: MPIR-191  (was: MSITE-469)
              Project: Maven 2.x Project Info Reports Plugin  (was: Maven 2.x Site Plugin)

> Site Plugin modify Compile Plugin classpath
> -------------------------------------------
>
>                 Key: MPIR-191
>                 URL: http://jira.codehaus.org/browse/MPIR-191
>             Project: Maven 2.x Project Info Reports Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: David Pilato
>         Attachments: hudsonfail.zip, logWithoutSite21.log, logWithSite21.log
>
>
> Hello,
> I'm going to try to explain my problem. Sorry for my poor english ;-)
> I'm building a multimodule project, with 3 modules A, B, C.
> In module A, I generate the test-jar with maven-jar-plugin.
> {quote}
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-jar-plugin</artifactId>
>   <executions>
>     <execution>
>       <goals>
>         <goal>test-jar</goal>
>       </goals>
>     </execution>
>   </executions>
> </plugin>
> {quote}
> I use the A jar and test-jar in my module B with the compile and test scope.
> {quote}
>   <dependencies>
>   	<dependency>
>   		<groupId>com.app.test</groupId>
>   		<artifactId>modulea</artifactId>
>   		<version>0.0.1-SNAPSHOT</version>
>   	</dependency>
> 	<dependency>
>  		<groupId>com.app.test</groupId>
>   		<artifactId>modulea</artifactId>
>   		<version>0.0.1-SNAPSHOT</version>
> 		<type>test-jar</type>
> 		<scope>test</scope>
> 	</dependency>
>   </dependencies>
> {quote}
> I use the module B jar in my module C as this :
> {quote}
>   <dependencies>
>   	<dependency>
>   		<groupId>com.app.test</groupId>
>   		<artifactId>moduleb</artifactId>
>   		<version>0.0.1-SNAPSHOT</version>
>   	</dependency>
>   </dependencies>
> {quote}
> And I run {{mvn clean install}}
> Everything is allright !
> Then I run {{mvn clean install site}}
> It fails.
> With the debug mode, I can see that the classpath is not correct.
> For the first run ({{mvn clean install}}), I have
> {quote}
> [DEBUG] Classpath: [C:\hudsonfail\modulec\target\classes
>  C:\hudsonfail\moduleb\target\moduleb-0.0.1-SNAPSHOT.jar
>  C:\hudsonfail\modulea\target\modulea-0.0.1-SNAPSHOT.jar]
> {quote}
> With the second run ({{mvn clean install site}}), I have :
> {quote}
> [DEBUG] Classpath: [C:\hudsonfail\modulec\target\classes
>  C:\hudsonfail\moduleb\target\moduleb-0.0.1-SNAPSHOT.jar
>  C:\hudsonfail\modulea\target\modulea-0.0.1-SNAPSHOT-tests.jar]
> {quote}
> As you can see, the compile classpath is modified.
> I attached to this JIRA :
> + the full test to reproduce the bug
> + the log file without site
> + the log file with site
> Thanks for your help
> If you have any advice to patch this before the next release, I will appreciate ;-)

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