[
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
