|Re: [m2e-users] Duplicate pom.properties and pom.xml in jar file|
Hmm, ok. When I put my full project into Indigo I got the duplicate file issue.
I found this issue on this mailing list:
Re: [m2e-users] Conflicting lifecycle mapping
Which seemed to indicate its in issue with wtp and the mavenarchiver m2e plugin.
When I pulled out the mavenarchiver plugin (it had been added when I imported my project into Indigo), then this all seems to be ok now.
However the previous thread seems to talk about m2e/wtp connector – which I don’t think I have, its still on my list of possible connector to install. So could this be a conflict with wtp in some way? Where would I look next to find out what the cause is?
Actually, just downloaded Indigo (EE version) direct, and created a new project – didn’t get the duplicate files this time. I’ll check off versions of maven/m2e and just see if I can find out any more about this.
I’m just moving to using the latest m2e (1.0) in the springsource tool suite (basically eclipse indigo I believe), and am having a bit of a problem with the generated jar files.
When I run a mvn clean install outside eclipse it all seems fine, however when I run it inside I end up with a jar file (attached), this has two copies on pom.xm and pom.properties in META-INF\maven\test\test\
It seems on is created by maven and one by the maven eclipse integration. Any clues on how to stop it doing this?
Is this anything to do with connectors? Please let me know if any more info would be useful,
Thanks in advance for any help/advice,