sebtiem opened a new issue, #864: URL: https://github.com/apache/maven-shade-plugin/issues/864
### Affected version master ### Bug description This issue is only reproduceable under Maven 4, currently RC7. This is possibly also affecting Maven Core but in the end, the Shade Plugin will have to adept conceptual changes of Maven 4. It seems to me that we have an issue with the new consumer-pom approach of Maven 4. I will create a branch in my fork containing an IT for reproduction. Under Maven 3, the Shade plugin creates a xyz.pom in the target directory being the shaded, reduced pom file. Under Maven 4, this xyz.pom is the regular project pom, containing all dependencies, plugins etc. Next to this file, there will be a xyz-build.pom, which contains the contents from the former Maven 3-xyz.pom. **Why is this an issue?** Every project built with Maven 4 relying on the shaded pom is now getting served the non-shaded variant. That circumstance leads to a dirty classpath in your project. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
