You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/01/21 23:29:22 UTC

[jira] Moved: (SUREFIRE-210) Wrong classpath order when running tests

     [ http://jira.codehaus.org/browse/SUREFIRE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter moved MSUREFIRE-15 to SUREFIRE-210:
------------------------------------------------

        Key: SUREFIRE-210  (was: MSUREFIRE-15)
    Project: Maven Surefire  (was: Maven 2.x Surefire Plugin)

> Wrong classpath order when running tests
> ----------------------------------------
>
>                 Key: SUREFIRE-210
>                 URL: http://jira.codehaus.org/browse/SUREFIRE-210
>             Project: Maven Surefire
>          Issue Type: Bug
>            Reporter: Magne Rasmussen
>         Assigned To: Brett Porter
>         Attachments: MNG-898-maven-surefire-plugin.patch
>
>
> When running tests, the surefire plugin puts the ${project.build.outputDirectory} before the ${project.build.testOutputDirectory} in the classpath. This prevents overriding classes/resources in tests, and breaks maven 1.1 compatibility.

-- 
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