[
http://jira.codehaus.org/browse/MECLIPSE-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268987#action_268987
]
Jean-Noel Rouvignac commented on MECLIPSE-388:
----------------------------------------------
Even though the sumarry does not reflect it, I think MECLIPSE-665
is a duplicate of the current bug.
By the way, do you have any news on this bug? I am facing it as well where I
want a hibernate.cfg.xml file from one project to be picked up based on the
ordering of the depencencies in the classpath. I have a test which work fine in
Surefire, but since Eclipse is using an alphabetical ordering, it is picking up
the hibernate.cfg.xml file from another project making the test fail. I had to
do some classloader magic (ClassLoader.getResources()) to make it work all the
time at the expense of longer running tests. Everything that adds up time to
run a test is definitely not nice.
Thanks.
> 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
