[
https://issues.apache.org/jira/browse/MSHADE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSHADE-140.
---------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Store the list of included artifacts as metadata and support an additional
> exclusions property
> ----------------------------------------------------------------------------------------------
>
> Key: MSHADE-140
> URL: https://issues.apache.org/jira/browse/MSHADE-140
> Project: Maven Shade Plugin
> Issue Type: Improvement
> Reporter: Mikhail Bautin
> Priority: Minor
> Attachments:
> MSHADE-140-Store-the-list-of-included-artifacts-as-m.patch
>
>
> In our deployment scenario we have multiple shaded jars, and some "library"
> shaded jars are always on the classpath, so "application" shaded jars do not
> have to include any classes that are already included with the library shaded
> jars. It is possible to take advantage of this optimization with a custom
> Maven plugin that is executed in the "package" phase before
> maven-shade-plugin, but we need to add two hooks to the latter:
> (1) Store the set of artifacts included in a shaded jar inside that shaded
> jar.
> (2) Allow specifying additional exclusions for maven-shade-plugin with a
> property.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
