[MNG-6579] Externalize org.apache.maven.repository.internal.MavenRepositorySystemUtils

[jira-importer]

Elliotte Rusty Harold opened MNG-6579 and commented

org.apache.maven.repository.internal.MavenRepositorySystemUtils is essentially mandatory for using the resolver. Without it you can't create a RepositorySystem, a ServiceLocator, or a RepositorySystemSession; all of which are needed before you can resolve an artifact.

This functionality should be available in a non-internal package. 

---

No further details from MNG-6579

[jira-importer]

Sylwester Lachiewicz commented

This issue should propably go to the Maven project as the MavenRepositorySystemUtils is part of Maven's org.apache.maven:maven-resolver-provider artifact

[jira-importer]

Robert Scholte commented

I'd like to have a concrete example, because my idea is to make it even harder to get access to Maven Artifact Resolver. The maven-plugin-api should be extended for better dependency resolution support.

[jira-importer]

Elliotte Rusty Harold commented

See almost all of this repo: https://github.com/GoogleCloudPlatform/cloud-opensource-java but especially https://github.com/GoogleCloudPlatform/cloud-opensource-java/tree/master/dependencies which uses Aether to query the Maven repository system. Remember, the repository system is much more broadly used than Maven itself, for instance by Ivy and Gradle. Aether may have moved from Eclipse to Apache but it should be separate from Maven. That is, Maven can depend on the repo system but the repo system should not depend on Maven.