maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trask Stalnaker (JIRA)" <>
Subject [jira] [Commented] (MSHADE-206) Multi-module builds don't pick up dependency-reduced-pom.xml
Date Thu, 01 Oct 2015 04:44:04 GMT


Trask Stalnaker commented on MSHADE-206:

I'm experiencing possibly the same issue.  For me, it actually works fine if I build with
maven 2.2.5, but does not work if I build with maven 3.3.1 and 3.3.3.  Can you see if this
is the case for you also?

> Multi-module builds don't pick up dependency-reduced-pom.xml
> ------------------------------------------------------------
>                 Key: MSHADE-206
>                 URL:
>             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 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

View raw message