gnodet commented on issue #11391: URL: https://github.com/apache/maven/issues/11391#issuecomment-3601107448
> > That's exactly what already happens when you consume a jar as a dependency. > > No, before the rule was unified in the build and mainly (even if tunable, nobody was using it almost) accross all projects, so all resolutions were well understood and known. Now the resolution of a 3rd party transitive deps will not more be aligned on the project which produces it view which is an issue IMHO so until we can flatten back the consumer pom we can have weird cases. Resolvable but useless headache for end users IMHO for an use case which is really rare since you never need that to resolve properly your dependencies (it is just an enhancement for comfort when you do not like defaults). If we keep this as a property to be specified as a maven user property (cli or config file), this information won't be available to consumers, so this can only affect build time behavior. -- 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]
