[SUREFIRE-61] Incorrect classpath ordering

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0 (2.2 plugin)
• Fix Version/s: 2.3.1
• Component/s: JUnit 3.x support
• Environment: maven2.0.4, sun-jdk-1.5.0.09, maven-surefire-plugin 2.2, surefire 2.0, gentoo linux x86
• Flags: Patch
• Assignee: Brett Porter
• Reporter: Martin Vysny
• Created: 04/Jan/07 04:22
• Updated: 05/Apr/15 14:53
• Resolved: 08/Aug/07 06:03

Description

Surefire incorrectly interprets classpath ordering.
Steps to reproduce:
1. unzip my-app.zip - it's a simple mvn project created with
mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app
and lightly patched
2. mvn test
in my case, it prints out
jar:file:/home/vyzivus/.m2/repository/jxta/jxta/2.0/jxta-2.0.jar!/log4j.properties
jar:file:/home/vyzivus/.m2/repository/jxta/jxta/2.0/jxta-2.0.jar!/log4j.properties
which is incorrect. log4j.properties is located both in jxta.jar and src/test/resources, but I think that src/test/resources takes precedence over jxta. This ordering is set correctly in surefire36745tmp file I think, but surefire seems to ignore the ordering.

Issue Links

• is duplicated by: SUREFIRE-289 Surefire classlaoder loads wrong class when classes are of same package/class name
• is related to: MNG-3118 Test-classes should come before classes in the classpath
• relates to: SUREFIRE-318 Fails to run build on Windows Server 2003