rmannibucau commented on PR #11639: URL: https://github.com/apache/maven/pull/11639#issuecomment-3807557187
@desruisseaux while we say consumer pom == runtime dependency set we are good, it means we prune optional, provided, test dependencies too. But it also means we prune all other kind of dependencies (javadoc, annotation-processor etc... and extension ones - will start to be complicated, think bundle for OSGi for ex). So basically we keep dependencies almost as this with just the flatten option. The dependency part I'm thinking about is parent gets my-java-util-logging-log-manager, so all children get it even the lib/ module which doesn't care. Loosing the inheritance info makes it harder to understand without checking original sources and automotion is harder if you need an unstable metadata source (build pom). This is part of the pom metadata which are consumed, now it is also common to put metadata in the pom elsewhere, properties are one location, plugins are another one. I can totally hear, "no this is wrong", but then we need a location which would be passthrough to consumer pom to let it be used downstream before downloading an artifact. All that to say that I think we should be able to keep the original info somehow in a normalized way. Fine if it needs to enhance the model to get there but just dropping will recreate the issues we original had. -- 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]
