Robert Joseph Evans created MSHADE-206:
------------------------------------------

             Summary: 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


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
(v6.3.4#6332)

Reply via email to