[MSHADE-326] Hide shaded dependencies from the rest of the reactor build

[jira-importer]

Niels Basjes opened MSHADE-326 and commented

When building a multi module project the following effect occurs:

1. A module with functionality is build ("library") that shades (and relocates) some of the  dependencies into the jar file. With https://issues.apache.org/jira/browse/MSHADE-36 in place this jar file has the correct transitive dependencies specified in the jar.

2. However when another module in the same project ("tool") uses that library the reactor will NOT look at the dependencies specified in the jar of the library. It will look at the dependencies specified in the original pom.xml of the library.

The effect is that the "tool" will have all dependencies of the "library" twice: Once from the library jar (possibly relocated) and once from the transitive dependencies passed on via the reactor.

 

Proposed change: 

1. Extra flag to enable this feature

2. If enabled the dependencies in the reactor are modified to match the dependencies in the actual jar file.

 

---

Affects: 3.2.1

Issue Links:

• MSHADE-206 Multi-module builds don't pick up dependency-reduced-pom.xml

Remote Links:

• GitHub Pull Request #26
  
• GitHub Pull Request #483
  

[jira-importer]

Ches Martin commented

Possible duplicate of MSHADE-206, I'll let a maintainer change the issue link type if confirmed. That issue is also linked to MNG-5899.

[jira-importer]

Michael Osipov commented

The description does not make sense. Maven never reads the POM from JAR/WAR, etc. Maven either uses the reactor or download the POM from a repo directory. Please clarify.