Eclipse Community Forums: Maven Integration for Web Tools Platform » Weird Behavior Between Kepler and Luna for M2E Deployment Assembly

Home » Archived » Maven Integration for Web Tools Platform » Weird Behavior Between Kepler and Luna for M2E Deployment Assembly

Show: Today's Messages :: Show Polls :: Message Navigator

Weird Behavior Between Kepler and Luna for M2E Deployment Assembly [message #1691245]

Fri, 03 April 2015 20:09

Perry Terrance

Messages: 1
Registered: April 2015

Junior Member

There is something really weird going on between the KEPLER version of the Deployment Assembly and the LUNA Version of Deployment Assembly when used with M2E.

If for example I have a single EAR I think to deploy - it will deploy the JARs packaged in the EARs differently even if its using the same exact POM and MAVEN settings.

Example:

EAR Project with dependency of depsample.jar

Since I am using a SNAPSHOT of that dependency - the POM would contain

<dependency>
<groupId>sample</groupId>
<artifactId>depsample</artifactId>
<version>1.0.0.2-SNAPSHOT</version>
</dependency>

In KEPLER - Deployment Assembly of the EAR Project I would see the following:
Source: /home/dev/.m2/repository/sample/1.0.0.2-SNAPSHOT/depsample-1.0.0.2-SNAPSHOT.jar
Deploy Path: depsample-1.0.0.2-SNAPSHOT.jar

This is OK for me.

However in LUNA - Deployment Assembly of the EAR Project I would see the following:
Source: /home/dev/.m2/repository/sample/1.0.0.2-SNAPSHOT/depsample-1.0.0.2-SNAPSHOT.jar
Deploy Path: depsample-1.0.0.2-20150403.11111-1.jar

Both are pointing to the same MAVEN 3.1.0 installation and repos.

I've been tinkering with LUNA like mad and can't get it to simply put the Deploy Path as the Source.

Why is LUNA doing this and not KEPLER?

Report message to a moderator