[
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
