[
http://jira.codehaus.org/browse/MECLIPSE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabrizio giustina closed MECLIPSE-561.
--------------------------------------
Resolution: Fixed
Fix Version/s: 2.9
I was a little bit uncertain to add this option since, according to several
comments, it could deviate the eclipse configuration from the standard maven
behaviour.
I think anyway it make sense to made it configurable for different reasons:
- it's not true that the current behaviour closely matches the maven one: it
matches the one used by maven in the test phase, but since eclipse has no
concept of phases this doesn't mean it will always be the expected
configuration. There is no way to mark dependencies and source dirs as "test
only" like maven does so there will always be a different between maven and
eclipse. The ability to run it tests (or simply to start an application) from
eclipse is a good argument.
- since the test-last ordering has been the default for the eclipse till
version 2.6 and several users complained about the change I think it's better
to explain why we changed the default but leaving the option to switch back to
the old behaviour, given the appropriate warning. Too many users seems to be
still tied to old (2.5) version of the plugin due to changes introduced after
that version
- another (silly) reason is just to keep the order users are used to in eclipse
(it's pretty normal to expect the main dirs first there) when there is nothing
in the project that may cause conflicts and dirs ordering doesn't matter for a
functional point of view.
Added in version 2.9, the new property is named "testSourcesLast" for
consistency with other options. An appropriate explanation/warning has been
added to the parameter documentation.
> 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
> Assignee: fabrizio giustina
> Fix For: 2.9
>
> 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
