You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Rustam Abdullaev (JIRA)" <ji...@codehaus.org> on 2009/05/12 13:56:45 UTC
[jira] Updated: (MECLIPSE-561) Provide a way to choose .classpath
ordering test-first vs. test-last
[ http://jira.codehaus.org/browse/MECLIPSE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rustam Abdullaev updated MECLIPSE-561:
--------------------------------------
Attachment: testBeforeMain.patch
attached testBeforeMain.patch introduces a new configuration variable <testBeforeMain> (true/false) that can be used to override default behavior.
> Provide a way to choose .classpath ordering test-first vs. test-last
> --------------------------------------------------------------------
>
> Key: MECLIPSE-561
> URL: http://jira.codehaus.org/browse/MECLIPSE-561
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Core : Dependencies resolution and build path (.classpath)
> Affects Versions: 2.6
> Reporter: Rustam Abdullaev
> Attachments: testBeforeMain.patch
>
>
> It seems like classpath ordering has been changed in 2.6, see bug MECLIPSE-318.
> Yes it improves unit testing, but it completely breaks integration testing. Now we can't run our Spring-based web application inside Eclipse because unit test resources override normal resources.
> Please revert this change or provide a way to specify that I want test classes/resources to be put in the classpath after non-test resources.
--
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