[#663] move to maven-resolver-api#668
Merged
laurentschoelens merged 2 commits intomasterfrom Jan 27, 2026
Merged
Conversation
laurentschoelens
added
enhancement
maven-plugin
laurentschoelens
force-pushed
the
jt-663
branch
from
4903a10 to
bcde457
Compare
Collaborator
|
I like this change -- get to a more modern Maven internal. Since we are a Maven plugin, we should bump at least the minor version to 4.2.0 or possibly move to 5.0.0 |
mattrpav
reviewed
Jan 24, 2026
laurentschoelens
changed the title
Collaborator
Author
I'll bump to 4.1.0 after merging this if you want 😉 |
laurentschoelens
force-pushed
the
jt-663
branch
from
bcde457 to
18a33af
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #663
Fix weird dependency resolution by moving to non-deprecated
maven-resolver-api