kerimovkhikmet commented on issue #11242: URL: https://github.com/apache/maven/issues/11242#issuecomment-3389159427
> This would be an issue for resolver or m-dependency-p, not Maven. > > But, as your pointed doco _explains_ this is not how Maven works. It is nicely explained [here](https://github.com/ghostbuster91/demos/tree/coursier-not-found): > > > The reason for that is that maven will first download only poms to create a dependency tree. Then versions will be chosen based on maven's version conflict resolution strategy and only then maven will download jars for the picked versions. > > For example, when version range is used, that range may contain tens or even more "candidates" (who's POM will be downloaded), but not all the JARs will _ever_ be needed. Alright, I get what you mean, and see possible complications. > And even more, Maven "enhanced" (used by Maven 3) local repository tracks origins of artifacts, and existence of that metadata is a must for correct mode of work (to let Maven figure out things for you), so "sharing" is not so simple. Do you mean that the addition of an option to remove all non-used POMs somewhere during the end phases, and respective local folders, also could not be applicable? > Finally, Maven transparently can use "split local repository" as well, that completely changes the layout on disk... Well, then, can you please share the link to the documentation with examples and details on how it works? -- 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]
