[
https://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barrie Treloar closed MECLIPSE-388.
-----------------------------------
Resolution: Fixed
>From feedback for this "iteration" of the solution is more palatable to users.
The next step is to look at aether and how its doing the dependency graph so
that this can be shared appropriately.
> Correct classpath ordering in .classpath
> ----------------------------------------
>
> Key: MECLIPSE-388
> URL: https://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
> Assignee: Barrie Treloar
> Priority: Critical
> Fix For: 2.9
>
> Attachments: ideal.classpath, MECLIPSE-388-it-test.patch,
> MECLIPSE-388.patch, MECLIPSE-388.patch, Test.zip
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
