[MECLIPSE-388] Correct classpath ordering in .classpath

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.4
• Fix Version/s: 2.9
• Component/s: Core : Dependencies resolution and build path (.classpath)
• Assignee: Barrie Treloar
• Reporter: Siarhei Dudzin
• Created: 09/Feb/08 20:57
• Updated: 17/Nov/11 21:00
• Resolved: 17/Nov/11 20:56

Description

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?

Issue Links

• is duplicated by: MECLIPSE-665 wrong classpath order generated in .classpath file for transitive dependencies
• is related to: MECLIPSE-705 Use Aether (or the shared exposed interface) to ensure correct .classpath ordering of dependencies.
• is related to: MNG-1412 dependency sorting in classpath
• is related to: MNG-3118 Test-classes should come before classes in the classpath
• relates to: MECLIPSE-318 test classes and resources need to be first in .classpath file