Github user revans2 commented on the pull request:

    https://github.com/apache/maven/pull/69#issuecomment-145854660
  
    @ifedorenko Without this kind of functionality using the shade plugin with 
multi-module projects is a huge pain, and would require us to use an external 
build system to coordinate the maven builds.  You have to fully build/install 
each shaded package independent of all other packages that depend on it.
    
    I understand that it is ugly to have the dependencies change as the build 
progresses.  I agree it really confuses things to run dependency:tree and see 
it be completely different from what is actually pulled in.  But it is not as 
bad as getting the wrong uber-jar that is missing things it needs.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to