You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tomasz Pik (JIRA)" <ji...@codehaus.org> on 2007/01/08 23:19:21 UTC
[jira] Created: (MASSEMBLY-175) MANIFEST entries are not preserved
during assemby
MANIFEST entries are not preserved during assemby
-------------------------------------------------
Key: MASSEMBLY-175
URL: http://jira.codehaus.org/browse/MASSEMBLY-175
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: Tomasz Pik
"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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-175) MANIFEST entries are not
preserved during assemby
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100277 ]
Paul Gier commented on MASSEMBLY-175:
-------------------------------------
I don't think this is the correct behaviour. There may be situations where you want to create a jar with deps, but do not want the same manifest configuration. It seems like it's better/simpler to just add the desired manifest configuration to to the assembly plugin config. You have some duplication of config, but it is more clear what is happening.
> MANIFEST entries are not preserved during assemby
> -------------------------------------------------
>
> Key: MASSEMBLY-175
> URL: http://jira.codehaus.org/browse/MASSEMBLY-175
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Tomasz Pik
> Fix For: 2.2-beta-2
>
>
> "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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MASSEMBLY-175) MANIFEST entries are not preserved
during assemby
Posted by "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
[jira] Updated: (MASSEMBLY-175) MANIFEST entries are not preserved
during assemby
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MASSEMBLY-175:
---------------------------------
Fix Version/s: (was: 2.2)
2.2-beta-2
> MANIFEST entries are not preserved during assemby
> -------------------------------------------------
>
> Key: MASSEMBLY-175
> URL: http://jira.codehaus.org/browse/MASSEMBLY-175
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Tomasz Pik
> Fix For: 2.2-beta-2
>
>
> "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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-175) MANIFEST entries are not preserved
during assemby
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-175?page=all ]
John Casey updated MASSEMBLY-175:
---------------------------------
Fix Version/s: 2.2
> MANIFEST entries are not preserved during assemby
> -------------------------------------------------
>
> Key: MASSEMBLY-175
> URL: http://jira.codehaus.org/browse/MASSEMBLY-175
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Tomasz Pik
> Fix For: 2.2
>
>
> "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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-175) MANIFEST entries are not
preserved during assemby
Posted by "Brian Jackson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MASSEMBLY-175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106981 ]
Brian Jackson commented on MASSEMBLY-175:
-----------------------------------------
My case is, we have an administration page for our application that displays the title/version/vendor for each of the packages in memory based on the Specification* and Implementation* keywords in the MANIFEST.MF files. If we use the original jars it works, but if we assemble a jar-with-dependencies it fails because the MANIFEST.MF are not merged. I don't want to maintain a MANIFEST.MF for the assembly by hand because its prone to becoming out-of-date with the actual dependency version in the POM (or transitive POMs). I need the assembly plugin to create an MANIFEST.MF that merges the MANIFEST, otherwise I can't deploy the assembly into our production environment (we need to know what versions of various libraries are deployed).
> MANIFEST entries are not preserved during assemby
> -------------------------------------------------
>
> Key: MASSEMBLY-175
> URL: http://jira.codehaus.org/browse/MASSEMBLY-175
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Tomasz Pik
> Fix For: 2.2-beta-2
>
>
> "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.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira