[
https://jira.codehaus.org/browse/MSHADE-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321739#comment-321739
]
Mikhail Bautin commented on MSHADE-140:
---------------------------------------
Our Maven plugin that allows to automatically exclude jars that are already
included in specified shaded jars from the newly created shaded jar is
available at https://github.com/mbautin/maven-shade-diff-plugin
> Store the list of included artifacts as metadata and support an additional
> exclusions property
> ----------------------------------------------------------------------------------------------
>
> Key: MSHADE-140
> URL: https://jira.codehaus.org/browse/MSHADE-140
> Project: Maven 2.x 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
