[SUREFIRE-619] The surefire plugin should generate the test classpath

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5
• Fix Version/s: 2.6
• Component/s: classloading, Maven Surefire Plugin
• Assignee: Paul Gier
• Reporter: Paul Gier
• Created: 14/May/10 11:42
• Updated: 17/May/10 14:48
• Resolved: 17/May/10 14:48

Description

I believe the surefire plugin would be improved if it generated the test classpath internally instead of getting the test classpath from MavenProject. This would allow the user better control over what is included in the classpath, and would actually simplify parts of the code for building the classpath.

The risk associated with this change is that the default surefire classpath could end up being different than the test classpath in MavenProject. However, I think that as long as the surefire plugin classpath generation is well documented, this won't cause a problem for users.

Issue Links

• is related to: SUREFIRE-502 Specified classesDirectory is added to the end of the classpath
• is related to: SUREFIRE-576 Have the abiltiy to remove a dependency from the test classpath (at least optional ones
• is related to: SUREFIRE-598 run maven test with customized classpath