-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use the new resolver provider #1483
Conversation
@Provides | ||
static VersionScheme getVersionScheme() { | ||
return new GenericVersionScheme(); | ||
private final VersionScheme delegate = new GenericVersionScheme(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cstamas fwiw, it would be easier if GenericVersionScheme
was not final
...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any other thing to make non final in resolver? Resolver was notorious about making all stuff final, and I did not want to change a lot there... I can do a sweeping change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any other thing to make non final in resolver? Resolver was notorious about making all stuff final, and I did not want to change a lot there... I can do a sweeping change
That's really the one that needed a workaround in my recent changes...
@cstamas I wonder if we should deprecate all the classes in |
Agreed, if maven-api-impl
|
The But there's no urge to deprecate those, we can do that after beta-1...
|
79059ba
to
c09dcea
Compare
There's a mix of usage between the v3 maven-resolver-provider and the new one located in maven-api-impl...