cstamas opened a new pull request, #1862: URL: https://github.com/apache/maven-resolver/pull/1862
When Resolver 2.x is used with `ScopeManager`, the scope semantics cannot be taken for granted as it was in Maven 3.9 and before, as in this case, scope manager configuration is the one who defines them, and their semantics as well. Hence, any scope related operation, like filtering and selecting (during collection) must be done in with scope manager prepared filter or selector. This PR fixes an issue never addressed in Resolver 2.x so far: it deprecated all the old "utils" that had wired-in scope semantics from Maven 3.9 and before times, but did not provide functionally equivalent replacement. -- 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]
