desruisseaux commented on PR #11639: URL: https://github.com/apache/maven/pull/11639#issuecomment-3811254740
> hmm, this is not the point, the point is that I'd like to avoid a consumer pom to be different if the upstream project is JPMS or not, there is no reason we make it different. A consumer POM of a classical Maven project can be a valid 4.0.0 model. But in a multi-module projects, the `<build>` element cannot be a valid 4.0.0 model. We must at least remove the `<sources>` element, which change the semantic. In other words, in a non-modular project, it is possible to produce a consumer POM in such a way that the users can trust the `<build>` as an accurate description of how the model was built. In a multi-module project, this is not possible. -- 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]
