[
http://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232387#action_232387
]
Florian Probst commented on MECLIPSE-388:
-----------------------------------------
The classpath order is the reason why we're still using version 2.4 of the
eclipse plugin. It's important that the pom order of the dependencies is
reflected in Eclipse. Imagine you are coding in eclipse, finished and the code
does not compile when you'd like to deploy the artifact. This isn't very
common, but without changing the build order the problem maybe can't be solved.
Now we would like to use the additionalConfig/location feature added in 2.5 and
have to use a newer version. The issue here was last discussed two years ago
and there is still no fix version given. I found a third party version of the
plugin called 2.8-cpfix on the internet:
http://stackoverflow.com/questions/793054/maven-classpath-order-issues
It would be great having a 2.9 fixing this issue instead of using 2.8-cpfix!
> Correct classpath ordering in .classpath
> ----------------------------------------
>
> Key: MECLIPSE-388
> URL: http://jira.codehaus.org/browse/MECLIPSE-388
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.4
> Reporter: Siarhei Dudzin
> Priority: Critical
> Attachments: MECLIPSE-388-it-test.patch, MECLIPSE-388.patch,
> MECLIPSE-388.patch
>
>
> Currently plugin sorts artifacts on its own (alphabetic order???) because the
> order of dependencies that comes from maven is not reliable (random?). This
> breaks tests that use JBoss Embedded which works under maven surefire plugin
> because it still puts dependencies that came first at the beginning of the
> classpath). Apparently not all classpath elements are put in random order. At
> least I get the first ones listed in dependencies also first in the classpath
> (can be seen as ${surefire.test.class.path} and in
> target/surefire-reports/TEST-TestSuite.xml).
> While there is not much we can do for maven eclipse plugin a solution is on
> the way: MNG-1412. When maven 2.0.9 is released maven eclipse plugin can
> revert back to the default classpath order.
> Can we somehow schedule this?
> Another question: is there anyway to put certain dependencies in the first
> place except for renaming them so that alphabetic order does the job?
--
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
