maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Commented: (MNG-3118) Test-classes should come before classes in the classpath
Date Wed, 05 Dec 2007 16:09:58 GMT


Benjamin Bentmann commented on MNG-3118:

Henri, Andreas, I think you are suffering from problems with Surefire 2.3. The MavenProject.getTestClasspathElements()
in Maven 2.0.8 now properly puts test-classes before classes (see code in svn or Maven's debug
output when using -X). However, Surefire 2.3 itself causes a reordering of the class path
in its SurefireBooter as reported in SUREFIRE-61. This issue has been marked as fixed and
I just noticed a svn tag for Surefire 2.3.1 has been created. So, it might be just a few days
until a working Surefire version is released and this problem is entirely solved.

> Test-classes should come before classes in the classpath
> --------------------------------------------------------
>                 Key: MNG-3118
>                 URL:
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: General
>    Affects Versions: 2.0.7
>            Reporter: Paul Gier
>             Fix For: 2.0.8, 2.1-alpha-1
>         Attachments: MNG-3118-maven-project-r558713.patch
> Currently maven-project creates the test classpath in the order: classes, tests-classes,
> It would be better if test-classes came first because sometimes it is useful for a test
class to replace a main class during testing.  The opposite case is not normally true (i.e.
one would not want to override a test class with one of the main classes).

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message