[#MASSEMBLY-171] Fix / speedup integration tests - jira.codehaus.org

Maven 2.x Assembly Plugin

Fix / speedup integration tests

Created: 22/Dec/06 11:37 AM Updated: 15/Aug/07 06:46 PM

Component/s:

None

Affects Version/s:

2.2

Fix Version/s:

2.3-beta-1

Time Tracking:

Not Specified

Description

« Hide

After hacking for quite a while in other projects to get the it's to run,
(fixing sandbox/plugins/maven-plug-it-plugin, shared/maven-plugin-testing-tools and components/maven-settings)
I found, after 9 minutes, this:

---------------------------------------
Execution Summary:
Builds Passing: 24
Builds Failing: 14
---------------------------------------

The following builds failed:

*  multimodule/twoLevel-includeSubModules-excludeSubModuleSourceDirs/pom.xml
*  multimodule/two-level-multimodule-dontIncludeSubModules/pom.xml
*  multimodule/two-level-multimodule/pom.xml
*  multimodule/two-levels-includeBaseDirectory-withSources/pom.xml
*  multimodule/twoLevel-dontIncludeSubModules-artifactIdExprOutDir/pom.xml
*  multimodule/two-levels-includeBaseDirectory-withBinaries/pom.xml
*  mojo-tests/single-twice-in-multimodule-hierarchy/pom.xml
*  mojo-tests/single-in-one-project-hierarchy/pom.xml
*  mojo-tests/single-twice-in-one-project-hierarchy/pom.xml
*  basic-features/outputFileNameMapping-withArtifactBaseVersion/pom.xml
*  basic-features/outputFileNameMapping-simple/pom.xml
*  repository-assembly/pom.xml
*  descriptor-refs/jar-with-dependencies/component-descriptors-merged/pom.xml
*  file-sets/same-source-name-different-output/pom.xml

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] : org.apache.maven.plugin.invoker.InvokerMojo@41a7c484
One or more builds failed.

14 builds failed.
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 minutes 58 seconds
[INFO] Finished at: Fri Dec 22 18:25:56 CET 2006
[INFO] Final Memory: 22M/57M
[INFO] ------------------------------------------------------------------------
FATAL ERROR: Unable to configure the Maven application
For more information, run with the -e flag

Most failed builds had this in the build.log:

url = http://snapshots.repository.codehaus.org
Downloading: http://snapshots.repository.codehaus.org/org/apache/maven/plugins/maven-plugins/4-SNAPSHOT/maven-plugins-4-SNAPSHOT.pom
[WARNING] Unable to get resource 'org.apache.maven.plugins:maven-plugins:pom:4-SNAPSHOT' from repository codehaus.org (http://snapshots.repository.codehaus.org)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.plugins
ArtifactId: maven-plugins
Version: 4-SNAPSHOT

Reason: Unable to download the artifact from any repository

  org.apache.maven.plugins:maven-plugins:pom:4-SNAPSHOT

from the specified remote repositories:
  codehaus.org (http://snapshots.repository.codehaus.org),
  central (http://repo1.maven.org/maven2)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Fri Dec 22 18:18:25 CET 2006
[INFO] Final Memory: 2M/6M
[INFO] ------------------------------------------------------------------------
FATAL ERROR: Unable to configure the Maven application
For more information, run with the -e flag

That repo isn't used anymore, plus 4-SNAPSHOT is in my local repo already.

I think repo isolation is good but the builds takes very very long because it tries to download
artifacts 71 times (only 57 are succesfully downloaded), using the wrong repo.

Can't the local repo serve as a fallback, or at least serve non-snapshots, so we can't install
the test plugin?

Reasoning; in order to test the current plugin, it must be available in a local repository
structure for maven to find it, due to a bug in maven (~~MNG-2677~~).
This requires a new local repo, initially empty. The plugin is added there.
But Maven can only handle 1 local repo at a time, so all the cached data there is not used.

Description

After hacking for quite a while in other projects to get the it's to run, (fixing sandbox/plugins/maven-plug-it-plugin, shared/maven-plugin-testing-tools and components/maven-settings) I found, after 9 minutes, this:

---------------------------------------
Execution Summary:
Builds Passing: 24
Builds Failing: 14
---------------------------------------

The following builds failed:

*  multimodule/twoLevel-includeSubModules-excludeSubModuleSourceDirs/pom.xml
*  multimodule/two-level-multimodule-dontIncludeSubModules/pom.xml
*  multimodule/two-level-multimodule/pom.xml
*  multimodule/two-levels-includeBaseDirectory-withSources/pom.xml
*  multimodule/twoLevel-dontIncludeSubModules-artifactIdExprOutDir/pom.xml
*  multimodule/two-levels-includeBaseDirectory-withBinaries/pom.xml
*  mojo-tests/single-twice-in-multimodule-hierarchy/pom.xml
*  mojo-tests/single-in-one-project-hierarchy/pom.xml
*  mojo-tests/single-twice-in-one-project-hierarchy/pom.xml
*  basic-features/outputFileNameMapping-withArtifactBaseVersion/pom.xml
*  basic-features/outputFileNameMapping-simple/pom.xml
*  repository-assembly/pom.xml
*  descriptor-refs/jar-with-dependencies/component-descriptors-merged/pom.xml
*  file-sets/same-source-name-different-output/pom.xml

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] : org.apache.maven.plugin.invoker.InvokerMojo@41a7c484
One or more builds failed.

14 builds failed.
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8 minutes 58 seconds
[INFO] Finished at: Fri Dec 22 18:25:56 CET 2006
[INFO] Final Memory: 22M/57M
[INFO] ------------------------------------------------------------------------
FATAL ERROR: Unable to configure the Maven application
For more information, run with the -e flag

Most failed builds had this in the build.log:

url = http://snapshots.repository.codehaus.org
Downloading: http://snapshots.repository.codehaus.org/org/apache/maven/plugins/maven-plugins/4-SNAPSHOT/maven-plugins-4-SNAPSHOT.pom
[WARNING] Unable to get resource 'org.apache.maven.plugins:maven-plugins:pom:4-SNAPSHOT' from repository codehaus.org (http://snapshots.repository.codehaus.org)
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.plugins
ArtifactId: maven-plugins
Version: 4-SNAPSHOT

Reason: Unable to download the artifact from any repository

  org.apache.maven.plugins:maven-plugins:pom:4-SNAPSHOT

from the specified remote repositories:
  codehaus.org (http://snapshots.repository.codehaus.org),
  central (http://repo1.maven.org/maven2)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Fri Dec 22 18:18:25 CET 2006
[INFO] Final Memory: 2M/6M
[INFO] ------------------------------------------------------------------------
FATAL ERROR: Unable to configure the Maven application
For more information, run with the -e flag

That repo isn't used anymore, plus 4-SNAPSHOT is in my local repo already. I think repo isolation is good but the builds takes very very long because it tries to download artifacts 71 times (only 57 are succesfully downloaded), using the wrong repo. Can't the local repo serve as a fallback, or at least serve non-snapshots, so we can't install the test plugin? Reasoning; in order to test the current plugin, it must be available in a local repository structure for maven to find it, due to a bug in maven (~~MNG-2677~~). This requires a new local repo, initially empty. The plugin is added there. But Maven can only handle 1 local repo at a time, so all the cached data there is not used.

Show »

Sort Order:

There are no comments yet on this issue.