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". -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
