[jboss-jira] [JBoss JIRA] Commented: (JBBUILD-382) Testrun of a project with circular dependencies errantly includes older version of itself

Paul Gier (JIRA) jira-events at lists.jboss.org
Thu Aug 9 18:22:01 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBBUILD-382?page=comments#action_12371685 ] 
            
Paul Gier commented on JBBUILD-382:
-----------------------------------

I wonder if the issue was related to this:
http://jira.codehaus.org/browse/SUREFIRE-61

Because looking at the test classpath, it looks like the local classes should have come first before the dependency.
The issue above caused the classpath ordering to be changed when the surefire plugin forked.

> Testrun of a project with circular dependencies errantly includes older version of itself
> -----------------------------------------------------------------------------------------
>
>                 Key: JBBUILD-382
>                 URL: http://jira.jboss.com/jira/browse/JBBUILD-382
>             Project: JBoss Build System
>          Issue Type: Bug
>          Components: Maven
>            Reporter: Jason T. Greene
>         Assigned To: Paul Gier
>             Fix For: Maven Build - Maint 2007
>
>
> jboss-common-core has a dependency on jboss-test
>  <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-test</artifactId>
>       <version>1.0.3.GA</version>
>       <scope>test</scope>
>     </dependency>
> jboss-test has a dependancy on jboss-common-core
> <dependency>
>       <groupId>jboss</groupId>
>       <artifactId>jboss-common-core</artifactId>
>       <version>2.0.4.GA</version>
>     </dependency>
> This leads to the surefire classpath containing 2 versions of jboss-common-core in the classpath, and unfortunately the older version wins. This means the testsuite never actually runs on the version you are modifying, which is a severe problem. Maven should be smart enough not to include the same artifact-id twice.
> [DEBUG] Test Classpath :
> [DEBUG]   /devel/common-core/trunk/target/classes
> [DEBUG]   /devel/common-core/trunk/target/test-classes
> [DEBUG]   /home/jason/.m2/repository/apache-log4j/log4j/1.2.8/log4j-1.2.8.jar
> [DEBUG]   /home/jason/.m2/repository/jboss/jboss-test/1.0.3.GA/jboss-test-1.0.3.GA.jar
> [DEBUG]   /home/jason/.m2/repository/org/apache/ant/ant-junit/1.7.0/ant-junit-1.7.0.jar
> [DEBUG]   /home/jason/.m2/repository/log4j/log4j/1.2.14/log4j-1.2.14.jar
> [DEBUG]   /home/jason/.m2/repository/org/apache/ant/ant/1.7.0/ant-1.7.0.jar
> [DEBUG]   /home/jason/.m2/repository/jboss/jboss-common-logging-spi/2.0.4.GA/jboss-common-logging-spi-2.0.4.GA.jar
> [DEBUG]   /home/jason/.m2/repository/jboss/jboss-logging-log4j/2.0.2.GA/jboss-logging-log4j-2.0.2.GA.jar
> [DEBUG]   /home/jason/.m2/repository/jboss/jboss-common-core/2.0.2.GA/jboss-common-core-2.0.2.GA.jar
> [DEBUG]   /home/jason/.m2/repository/apache-slide/webdavlib/2.0/webdavlib-2.0.jar
> [DEBUG]   /home/jason/.m2/repository/oswego-concurrent/concurrent/1.3.4/concurrent-1.3.4.jar
> [DEBUG]   /home/jason/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
> [DEBUG]   /home/jason/.m2/repository/jboss/profiler/jvmti/jboss-profiler-jvmti/1.0.0.CR5/jboss-profiler-jvmti-1.0.0.CR5.jar
> [DEBUG]   /home/jason/.m2/repository/apache-xerces/xml-apis/2.7.1/xml-apis-2.7.1.jar
> [DEBUG]   /home/jason/.m2/repository/jboss/jboss-logging-spi/2.0.2.GA/jboss-logging-spi-2.0.2.GA.jar
> [DEBUG]   /home/jason/.m2/repository/org/apache/ant/ant-launcher/1.7.0/ant-launcher-1.7.0.jar
> [DEBUG]   /home/jason/.m2/repository/apache-httpclient/commons-httpclient/2.0.2/commons-httpclient-2.0.2.jar

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list