[
https://issues.apache.org/jira/browse/MSHADE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16999141#comment-16999141
]
Francois MAROT commented on MSHADE-206:
---------------------------------------
Hello [~elharo] , as a simple Maven user but following closely what happens in
Maven world and using the shade plugin, I can tell you this is still an issue
and not resolved. If you use the shade plugin, the module using the shade
plugin has to be the LAST one in your Maven execution. Meaning that no module
in your multi-module should depend on the shade jar or otherwise you will not
get what you expect to get regarding dependencies. You have to split your build
in two phase where the first installs (or deploys) the shaded jar.
> Multi-module builds don't pick up dependency-reduced-pom.xml
> ------------------------------------------------------------
>
> Key: MSHADE-206
> URL: https://issues.apache.org/jira/browse/MSHADE-206
> Project: Maven Shade Plugin
> Issue Type: Bug
> Reporter: Robert Joseph Evans
> Priority: Major
>
> I'm not sure if there is a good solution for this or not. As part of the
> Apache Storm project we are trying to shade a lot of dependencies for the
> core platform (storm-core), but we also have other modules in the same build
> that depend on storm-core, but use the shade plugin to create an uber jar for
> deployment. The problem is that if we build all of the modules at once and
> let maven handle resolving dependencies the uber jar projects don't see
> storm-core's dependency-reduced-pom.xml. They see the original pom.xml and
> end up not packaging dependencies that they need.
> Our "fix" for this https://github.com/apache/storm/pull/736 is to split the
> build up into two phases. One that just builds storm-core and another that
> builds the rest. This is going to be a real pain for developers. Are we
> doing something wrong? Is this working as expected?
> I am happy to submit a fix for this, but I am far from an expert on maven so
> if someone in this project sees a direction that I can go in to fix this I
> would appreciate any guidance you might have.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
