Maven classpath order issues

Question

Does anyone know of a way to set a specific classpath order in Maven2, rather than the random ordering I appear to experience at the moment?

There are a number of le

Answer 1

Maven 2.0.9 adds correct ordering so you absolutely must have that version or higher for the below to work.

Secondly you need the an updated plugin. The Maven guys are working on a fix, its in their jira to fix but this is something I urgently needed. So in the meantime I have fixed this myself and you can pull the Modified plugin source code from github.

Edit: Refer to http://jira.codehaus.org/browse/MECLIPSE-388

There are two ways to install it, either pull my modified code and install it or download the prebuilt jar and just add it.

Building the plugin

Run maven install from the plugin directory you checked out and then add the following in your plugins section of your projects pom:

<build>
  </plugins>
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-eclipse-plugin</artifactId>
      <version>2.8-cpfix</version>
    </plugin>
  </plugins>
</build>

Download the jar

Alternatively if you don't want to download and compile yourself then you can just get hold of the jar file and install it yourself.

Once you have the file run

mvn install:install-file -Dfile=<path-to-file> -DgroupId=org.apache.maven.plugins \
    -DartifactId=maven-eclipse-plugin -Dversion=2.8-cpfix -Dpackaging=jar

Regardless of how you installed it now when you run mvn eclipse:eclipse it will pick up the modified code and order the dependencies based on the order you defined in your pom file, no alphabetical ordering. It will also put the JRE container at the top of the dependencies.

Hopefully the real version of this code will come out soon, but in the meantime this fix has worked for me on my project and I hope it can help some others as well.

Answer 2

As of version 2.0.9 maven uses pom order for classpath, so you can actually manipulate it now. We mostly supress transitive dependencies to external libraries that we also include directly.

From the release notes of maven 2.0.9:

MNG-1412 / MNG-3111 introduced deterministic ordering of dependencies on the classpath. In the past, natural set ordering was used and this lead to odd results. The ordering is now preserved from your pom, with dependencies added by inheritence added last. In builds that had conflicting or duplicate dependencies, this may introduce a change to the output. In short, if you have weird issues with 2.0.9, take a look at the dependencies to see if you have conflicts somewhere.