[jira] Closed: (MASSEMBLY-175) MANIFEST entries are not preserved during assemby

["John Casey (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MASSEMBLY-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MASSEMBLY-175.
--------------------------------

    Resolution: Won't Fix
      Assignee: John Casey

I don't think there's a reasonable way to specify the merging rules for manifests...which assembly constituent gets preference in a collision? Also, I don't think it's reasonable to assume that manifest entries for an assembly will be the same as for the original project jar.

Is there a reason you can't use the same <archive> configuration subsection that you'd use in the jar plugin, and specify the manifest that way?

If someone is willing to submit a patch that contains integration tests showing how to specify merge rules for colliding manifest attributes, how to turn off manifest merging, and so forth, then we can reopen...but it seems like automatic merging is one of those places that could lead to a lot of consternation about what the plugin is doing, and why.

> MANIFEST entries are not preserved during assemby
> -------------------------------------------------
>
>                 Key: MASSEMBLY-175
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-175
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Tomasz Pik
>            Assignee: John Casey
>             Fix For: 2.3
>
>
> "jar-with-dependencies" assembly should preserve MANIFEST entries from project main result (so configuration for this will be inherited from maven-jar-plugin).
> This is especially important in case for <mainClass> parameter.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira