[
https://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280314#comment-280314
]
Barrie Treloar commented on MECLIPSE-388:
-----------------------------------------
Jean-Noel, thanks for the feedback but its reads as a mixed message. I'm not
sure if this is fixed or there is more work to be done.
I suspect more work.
When you say it better respects the dependency tree, are you saying that the
output is not correct?
Looking at the 2.9 output, I'm suspicious about why the JRE_CONTAINER is third
on the classpath (i.e. splattered in amongst everything else).
Also why is
M2_REPO/javax/persistence/persistence-api/1.0/persistence-api-1.0.jar second?
Its a transitive dependency of
org.hibernate:hibernate-annotations:jar:3.2.1.ga:compile.
The ordering doesn't look like the order I expect.
Would you be able to re-arrange the 2.9.classpath into the order you expect?
I've pulled out the dependency mojo which uses a shared component for building
the tree.
I vaguely recall something about that not being 100% correct but I think I'll
look at switching the m-e-p implementation from a home-grown to shared
components.
At least that will mean it can get fixed once.
Work is busy at the moment so progress may stall for a bit.
> 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: 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
