maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rustam Abdullaev (JIRA)" <>
Subject [jira] Updated: (MECLIPSE-561) Provide a way to choose .classpath ordering test-first vs. test-last
Date Tue, 12 May 2009 11:56:45 GMT


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:
>             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
> 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:
For more information on JIRA, see:


View raw message