archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "nicolas de loof" <nico...@apache.org>
Subject test failure MavenProjectInfoReportsPluginDependencyGraphTest
Date Wed, 30 Jan 2008 20:02:45 GMT
I get a test failure on MavenProjectInfoReportsPluginDependencyGraphTest

This test use maven-project-info-reports-plugin:2.1-SNAPSHOT to test
dependency graph :

unit.framework.AssertionFailedError:

 (Extra Actual) org.codehaus.plexus:plexus-utils:1.0.4::jar
 (Extra Actual)
org.codehaus.plexus:plexus-container-default:1.0-alpha-8::jar
 (Extra Actual) org.apache.maven:maven-profile:2.0.4::jar
 (Extra Actual) org.apache.maven:maven-repository-metadata:2.0.2::jar
 (Extra Actual) org.apache.maven:maven-artifact:2.0::jar

 (Extra Expected) org.apache.maven:maven-artifact:2.0.4::jar
 (Extra Expected) org.apache.maven:maven-profile:2.0::jar
 (Extra Expected) org.apache.maven:maven-repository-metadata:2.0::jar
 (Extra Expected)
org.codehaus.plexus:plexus-container-default:1.0-alpha-9::jar
 (Extra Expected) org.codehaus.plexus:plexus-utils:1.1::jar

Maybe I've something wrong on my environment, but using a SNAPSHOT in the
test may introduce errors when the target artifact gets updated. Can the
maven version running the build (2.0.8 for me) change the dependency result,
as a plugin is user by the test ? Could this test be rewritten to use a
stable artifact ?


Nico.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message