cstamas commented on PR #445: URL: https://github.com/apache/maven-resolver/pull/445#issuecomment-2000046152
Well, IMO this PR goes exactly in direction of MRESOLVER-471, as: * scope manager is optional, in a sense, if you want to use Resolver 2.x as you did Resolver 1.x, go for it * ScopeManager solves the problem of "Resolver should be oblivious about scopes" (MRESOLVER-471), as Resolver 1.x implemented scope related logic scattered across several (dozen?) classes, and actions like "introducing new scope" or "removal of a scope" was impossible exactly due that (as Resolver was not oblivious, but had them cemented as String constants spread across dozen classes). Hence Resolver was "this xor that". With ScopeManager Resolver IS really oblivious, as they are defined by client project, the app that is integrating Resolver 2. -- 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
