You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/12/31 22:39:39 UTC

[jira] [Closed] (MSHARED-324) Archiver zips duplicate pom.xml and properties files

     [ https://issues.apache.org/jira/browse/MSHARED-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MSHARED-324.
----------------------------------
    Resolution: Cannot Reproduce

Works flawlessly with Maven JAR Plugin 2.6. Everything below is broken. Upgrade.

> Archiver zips duplicate pom.xml and properties files
> ----------------------------------------------------
>
>                 Key: MSHARED-324
>                 URL: https://issues.apache.org/jira/browse/MSHARED-324
>             Project: Maven Shared Components
>          Issue Type: Bug
>          Components: maven-archiver
>    Affects Versions: maven-archiver-2.5
>            Reporter: Fred Bricon
>         Attachments: duplicate-zipped-files.zip
>
>
> Several users of m2e-wtp complained invoking *mvn package* (without clean) on their project generates a jar containing duplicate pom.properties and pom.xml.
> * http://stackoverflow.com/questions/10308916/maven-generates-duplicate-pom-xml-and-pom-properties-files-in-a-jar
> * http://dev.eclipse.org/mhonarc/lists/m2e-users/msg01995.html
> * https://issues.sonatype.org/browse/MECLIPSEWTP-209
> * https://issuetracker.springsource.com/browse/STS-2349
> * https://github.com/sonatype/m2eclipse-extras/issues/9
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=405915
> This is caused by m2eclipse-mavenarchiver generating these files during eclipse incremental builds, under target/classes.
> The proper course of action is generally to invoke mvn clean package, in that case, but I believe the archiver should never generate zips with duplicate entries in the first place.
> I don't have an opinion whether the mavenarchiver generated files should take precedence over the existing ones, or the other way around. Whatever solution is chosen, a warning should be logged in case of duplicates.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)