ascheman commented on PR #11639: URL: https://github.com/apache/maven/pull/11639#issuecomment-3864499862
> Regarding `<dependencie>`, this is another issue. The removal of dependencies is not for compatibility with the 4.0.0 model. It is because the current strategy of [apache/maven-jar-plugin#508](https://github.com/apache/maven-jar-plugin/pull/508) uses the consumer POM of the project as the parent of the POM of each module. If we do not remove the dependencies, then every modules would inherit all project's dependencies, including the dependencies that a module does not use. I should have looked again in 508 ... On the other hand I was not aware that there was already some stuff to create consumer POM in the core. Considering that, handling of <whatever> (creating consumer POMs in this case) it is perhaps best to either leave it completely in the core (and thereby unify handling accross plugins) or move it completely to the Plugins. IIRC we already discussed this topic elsewhere. Perhaps it is OK to initially do something at first in single plugins and only move it to the core when it stabilizes? In this case I slightly tend to move the Maven Model > 4.1.0 based consumer POM generation to the core as soon as possible to not get different behaviour on Maven 3 (4.0.0 model) and Maven 4 (4.1.0). -- 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]
