[
https://issues.apache.org/jira/browse/MRESOLVER-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750266#comment-17750266
]
ASF GitHub Bot commented on MRESOLVER-387:
------------------------------------------
cstamas commented on PR #319:
URL: https://github.com/apache/maven-resolver/pull/319#issuecomment-1662039538
Yes, resolver itself is "incomplete". To provide "complete" resolver, one
must add (maven) models and missing components (implemented in maven as those
are maven model specific).
Hence, I added this new supplier module that constructs and supplies
**complete** resolver instance, but to achieve that, you must have some maven
bits on classpath.
And yes, there IS a seemingly "circular" dependency between Resolver and
Maven. When consumer (you) declare dependency on supplier module, consumer
actually _breaks_ the chain: you declare dependency on supplier in your POM
(1st level), supplier declares dependency on resolver artifacts and maven
artifacts (2nd level) and maven-resolver-provider "points back" to resolver
artifacts (3rd level), but alas, you already have them on 2nd level, so maven
"nearest first" simply ignores those.
Also, this is the reason why README contains the "versions of resolver
artifacts MUST BE aligned with resolver supplier artifact version".
> Provide "static" supplier for RepositorySystem
> ----------------------------------------------
>
> Key: MRESOLVER-387
> URL: https://issues.apache.org/jira/browse/MRESOLVER-387
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.15
>
>
> To provide SL replacement.
> Something like this
> https://github.com/maveniverse/mima/blob/main/runtime/standalone-static/src/main/java/eu/maveniverse/maven/mima/runtime/standalonestatic/RepositorySystemSupplier.java
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
