[
http://jira.codehaus.org/browse/MNG-3118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117314
]
KlaasJan Elzinga commented on MNG-3118:
---------------------------------------
It just didn't feel like a patch version change. The fact that my build failed
first with 2.0.8 and a week later with 2.0.7 doesn't feel right.
Backwards compatibility could be accomplished by mvn querying the surefire
plugin version and construct the path with respect to that version. FYI, I was
using mvn in an environment where upgrades are not allways possible/easy
(...and all the dvl'ers had to upgrade), I know how to work around it, which
meant a code change or an upgrade.
In the end I advised everyone to upgrade to 2.0.8. I'll stop commenting on this
issue since this is not really the place for it anyway.
Thanks for the reaction though.
> 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
