gnodet commented on PR #11775: URL: https://github.com/apache/maven/pull/11775#issuecomment-4032263592
Closing this PR — after further analysis, the dual consumer POM approach adds significant complexity that is not justified. **Key insight**: Maven 4 can already resolve the `build` classifier POM for full-fidelity parent resolution. There is no need for a separate `consumer` classifier POM. The simpler approach is: 1. Keep flattening as the mechanism for backward-compatible (4.0.0) consumer POMs 2. Add a flag to control managed dep removal during flattening (for users who want correctness over POM size) 3. Validate at build time: if flattening is disabled and the parent has 4.1.0+ features that would be lost in the consumer POM, reject the build See discussion on #11772 for the full reasoning. -- 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]
