Maven Shared Components

Duplicate pom.properties files being created

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: maven-archiver
  • Labels:
    None
  • Environment:
    Spring Tool Suite 2.8.1
    JDK 1.6.0_29
    Maven Integration for WTP 0.14.0
  • Number of attachments :
    1

Description

When using STS, if you create a new maven project (skip archetype selection), when running a maven install from inside eclipse you end up with a jar file as per the attached.

This has two copies of the pom.properties, and pom.xml files in the META-INF directory (this causes knock on problems for us when running JiBX).

It seems the reason that the final jar file has the duplicates in is that the target directory that is being jar'd up already contains these files, so they are being pulled in, and then the archiver is creating its own.

I think it would be good if the archiver checked to see if the files where already there before creating them, if it doesn't already?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Warren Goldman added a comment -

Is there a work around, so they only show up once? Or if not that, so they are not included at all?

Show
Warren Goldman added a comment - Is there a work around, so they only show up once? Or if not that, so they are not included at all?
Hide
Permalink
Matthew Harrison added a comment -

We're kind of living with it for now - the issue is only when you're working in eclipse. From memory I think its actually the m2 eclipse plugin thats the issue, you may want to look at this:

https://github.com/sonatype/m2eclipse-extras/issues/9

But if you run maven outside eclipse you won't get the same issue.

If you really had to I think you could probably sort out the maven build to produce the right jar file, but it was never worth it for us to do it.

Hope that helps a bit?

Matt

Show
Matthew Harrison added a comment - We're kind of living with it for now - the issue is only when you're working in eclipse. From memory I think its actually the m2 eclipse plugin thats the issue, you may want to look at this: https://github.com/sonatype/m2eclipse-extras/issues/9 But if you run maven outside eclipse you won't get the same issue. If you really had to I think you could probably sort out the maven build to produce the right jar file, but it was never worth it for us to do it. Hope that helps a bit? Matt

People

  • Assignee:
    Unassigned
    Reporter:
    Matthew Harrison
Vote (1)
Watch (1)

Dates

  • Created:
    Updated: