You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/18 11:42:01 UTC

[jira] [Resolved] (MSHADE-165) Allow collection of additional manifest sections in the shaded jar manifest

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

Elliotte Rusty Harold resolved MSHADE-165.
------------------------------------------
    Resolution: Fixed

Referenced change seems to have been merged

> Allow collection of additional manifest sections in the shaded jar manifest
> ---------------------------------------------------------------------------
>
>                 Key: MSHADE-165
>                 URL: https://issues.apache.org/jira/browse/MSHADE-165
>             Project: Maven Shade Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.2
>            Reporter: Henning Schmiedehausen
>            Priority: Major
>
> https://github.com/apache/maven-plugins/pull/18
> This change adds a flag to the ManifestResourceTransformer that will
> make it collect all additional manifest sections (non-main) and add
> them to the manifest of the shaded jar.
> This is useful if per-jar information is stored in Manifests
> (e.g. build information) and should still be present in the resulting
> shaded jar.
> If a section is present in one or more source jars, they are merged
> into a single section (TODO: add code to choose between "replace",
> "merge" or "fail").



--
This message was sent by Atlassian Jira
(v8.3.4#803005)