[jira] Moved: (MASSEMBLY-397) One IT of MASSEMBLY only succeeds if run individually

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

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

Benjamin Bentmann moved MNG-4073 to MASSEMBLY-397:
--------------------------------------------------

    Affects Version/s:     (was: 2.0.10)
                       2.2-beta-3
          Component/s:     (was: Integration Tests)
           Complexity:   (was: Intermediate)
           Issue Type: Task  (was: Bug)
                  Key: MASSEMBLY-397  (was: MNG-4073)
              Project: Maven 2.x Assembly Plugin  (was: Maven 2)

> One IT of MASSEMBLY only succeeds if run individually
> -----------------------------------------------------
>
>                 Key: MASSEMBLY-397
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-397
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Task
>    Affects Versions: 2.2-beta-3
>         Environment: Linux, Sun JDK 5, M2.0.10, Subversion rev 750882
>            Reporter: Joerg Schaible
>
> One IT of the maven-assembly-plugin fails always if it is executed together with all the other ITs, but succeeds if it is run separately:
> {noformat}
> ./maven-assembly-plugin $ mvn clean integration-test -P run-its -Dit.pomIncludes=mojo-tests/single-twice-in-multimodule-hierarchy/pom.xml
> ...
> [INFO] [invoker:run {execution: integration-test}]
> [INFO] Building: mojo-tests/single-twice-in-multimodule-hierarchy/pom.xml
> [INFO] ...SUCCESS.
> {noformat}
> However, it fails if all tests are executed:
> {noformat}
> ./maven-assembly-plugin $ mvn clean integration-test -P run-its
> ...
> [INFO] Building: mojo-tests/single-in-one-project-hierarchy/pom.xml
> [INFO] ...SUCCESS.
> [INFO] Building: mojo-tests/single-twice-in-multimodule-hierarchy/pom.xml
> [INFO] ...FAILED. The post-build script returned false.
> [INFO] Building: mojo-tests/single-twice-in-one-project-hierarchy/pom.xml
> [INFO] ...SUCCESS.
> {noformat}
> The verify.bsh fails, because the files ...
> {noformat}
> result = result && new File( basedir, "child1/target/child1-1.0-SNAPSHOT-bin/lib/junit.jar" ).exists();
> result = result && new File( basedir, "child2/target/child2-1.0-SNAPSHOT-bin/lib/junit.jar" ).exists();
> {noformat}
> are copied to child1/target/child1-1.0-SNAPSHOT-bin.dir/lib/junit.jar and child1/target/child1-1.0-SNAPSHOT-bin.dir/lib/junit.jar (not the .dir extension of the directory). The interesting part is, that John Casey removed this extension of the path in the verify.bsh in Sept. 2008.
> Note, that other tests are failing if the target was not cleaned before.
> Since it is not clear which component (Maven core, invoker plugin or assembly plugin) triggers this strange side effect I added the issue to Maven core. Maybe John can remember what was the original cause of the change (the changeset contains a lot of files) and why the old behavior might arbitrarily creep into the IT execution.

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