[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-users] duplicate pom.properties
|
m2e-wtp (via the mavenarchiver plugin) automatically generates the maven pom and properties files as part of eclipse's incremental build.
The actual problem lies in the packaging done during CLI builds, where these files are also generated and added to the archive, regardless of the presence of existing files with the same name.
The workaround is simple : when doing a CLI build, always invoke the clean goal like : mvn clean verify.
On Wed, Nov 21, 2012 at 9:26 AM, Bjørn-Willy Arntzen
<bwa@xxxxxx> wrote:
Hello all. I’m using m2e 1.2 with IBM RAD 8.5 and most of maven stuff actually works very fine now. Especially deployment to local WebSphere test environment. This is really great, Well done!
I still have one strange issue... I’m using command line to build an ear artifact to deploy to the sentral server, but here I got duplicate files in META_INF\maven\<artifact>\directory
In my web-module
c:\RAD85\workspace\asaptrigger\asaptrigger-web\target\asaptrigger-web-2.5.0-SNAPSHOT.war\META-INF\maven\no.klp.asaptrigger\asaptrigger-web\
there is 4 files, instead of 2. It contains two pom.properties and 2 pom.xml. This is not possible on a file system, but inside a war(zip) there is possible.
One pom.properties has #Generated by Maven Integration for Eclipse the other has #Generated by Maven
The reason seems to be that my m2e is generating a pom.properties and pom.xml, and also a maven (v 3.0.3) clean install from the command line is creating the same set of files.
I see clearly that m2e is generating (and instantly re-generating on a delete) 2 new pom files in the workspace.
How can I get rid of this ?
Med vennlig hilsen
Bjørn Willy Arntzen
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
--
"Have you tried turning it off and on again" - The IT Crowd