[
https://issues.apache.org/jira/browse/MSHADE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MSHADE-159.
---------------------------------
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.
> Chained shading fails
> ---------------------
>
> Key: MSHADE-159
> URL: https://issues.apache.org/jira/browse/MSHADE-159
> Project: Maven Shade Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: MacOS with jdk1.7.0_45
> Reporter: Viktor Sadovnikov
> Priority: Major
>
> * Multi-module project with modules A, B and C;
> * B shades-in a number of classes from A and shade plug-in replaces original
> B artifact
> * C shades-in classes from B, including those, which are originally from A
> If "mvn clean install" is executed on parent level, classes from A are
> missing in resulted C. However if "mvn clean install" is executed from C
> module (and plug-in gets B from local repo) classes from A are available in C.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
