Why is my EAR Module Assembly constantly being renamed by Eclipse M2E Maven?

[Perry Terrance]

I use MAVEN SNAPSHOTS for my dependencies - which typically have a naming schema like "dependency-2.1.1.01-SNAPSHOT.jar"

However - every time I update my Maven Java project in my Eclipse Luna (with internal MAVEN 3.2.1) - it gives me the Ear Module Assembly as:

Source
/home/user/.m2/repository/com/dependency-2.1.1.01-SNAPSHOT.jar
Deploy Path
dependency-2.1.1.01-20150403.221111-1.jar

It seems to constantly append the Timestamp to the Deploy Path - when I want it to stay the same naming of "-SNAPSHOT".

Is there a MAVEN configuration in Eclipse (or outside) that I'm missing somewhere?

All I want is the following:

Source
/home/user/.m2/repository/com/dependency-2.1.1.01-SNAPSHOT.jar
Deploy Path
dependency-2.1.1.01-SNAPSHOT.jar

This is causing issues on my local JBoss test server - as it expects the naming of the JARs to be exactly using the "-SNAPSHOT.jar" naming schema when its Published.

[Jeanne Boyarsky]

Perry,
It's a two part fix. #2 is what you are asking about specifically. I'm posting both because it is more subtle being a runtime issue.

1) When configuring maven-ejb-plugin, add <useUniqueVersions>true</useUniqueVersions> in the manifest. Note that if you have multiple ear's (that depend on other ears), you need to do this for each or put this config in a parent pom. For example:

<plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-ejb-plugin</artifactId> <configuration> <archive> <manifest> <addClasspath>true</addClasspath> <useUniqueVersions>false</useUniqueVersions> </manifest> </archive> </configuration> </plugin>

2) In your ear configuration in the pom, set <useBaseVersion>true</useBaseVersion>

These two combined will generate a jar without the timestamp and remove that timestamp from the manifest.mf dependencies.

[Perry Terrance]

Thanks Jeanne for the response - let me try that and let you know.

One more thing, I found that when I ran Eclipse Kepler on the exact same workspace - it do not any Timestamps in the Deploy Path! Is there some different between Eclipse Luna and Kepler thats causing this - cause its all reading the same workspace (basically same MAVEN settings, POMs, etc)?

[Jeanne Boyarsky]

Different version of Maven maybe? I encountered this problem/solution with pure Maven and not specifically to Eclipse.