[
http://jira.codehaus.org/browse/MNG-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117282
]
Benjamin Bentmann commented on MNG-3118:
----------------------------------------
Well, how should Maven have kept backward compatibility here? There can only be
one class path order.
If Surefire 2.3.1 is not usable for you (I feel happy with it and Maven 2.0.8),
you can lock your POM to Surefire 2.3 by explicitly specifying
<version>2.3</version> in the corresponding <plugin> element.
> Test-classes should come before classes in the classpath
> --------------------------------------------------------
>
> Key: MNG-3118
> URL: http://jira.codehaus.org/browse/MNG-3118
> 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, dependencies.
> 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
