[
http://jira.codehaus.org/browse/SUREFIRE-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121329
]
Benjamin Bentmann commented on SUREFIRE-428:
--------------------------------------------
Another option might be to guard the test by an if-condition that checks for a
newer Maven version similar to a JUnit assumption.
> Add integration test to check class path order
> ----------------------------------------------
>
> Key: SUREFIRE-428
> URL: http://jira.codehaus.org/browse/SUREFIRE-428
> Project: Maven Surefire
> Issue Type: Task
> Reporter: Benjamin Bentmann
> Attachments: classpath-order-it.patch, classpath-order-it.patch
>
>
> The attached integration test checks some ordering constraints on the class
> path for testing:
> - test-classes should come before main-classes
> - main-classes should come before dependencies
> It might not catch all bad cases but currently there seems to be nothing that
> prevents regression of MNG-3118 or SUREFIRE-61 and this test at least tells
> you that Surefire-2.3 is broken.
> In concern of quality assurance, I would also like to mention that MNG-2365
> has an unapplied patch that provides a unit test for MNG-3118.
--
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
