Skip to content
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

[EXPERIMENT] Update resolver and use newly introduced method #428

Closed
wants to merge 1 commit into from

Conversation

cstamas
Copy link
Member

@cstamas cstamas commented Jan 8, 2021

Update resolver and make use of newly introduced method in apache/maven-resolver#87

This PR is NOT meant for merge as is, is more just an example.

@cstamas cstamas self-assigned this Jan 8, 2021
@slachiewicz
Copy link
Member

I'm really interested in how this will work (ie use the newer resolver method) in plugins - that run in older maven 3.6.3 (as a replacement to m-artifact-transfer.

@cstamas
Copy link
Member Author

cstamas commented Jan 8, 2021

Was m-a-t initial goal to "hide" org.sonatype vs org.eclipse resolver diffs? So to say maven 3.0 vs maven 3.1. Also, it is sitting between maven (core) and resolver (core), but m-a-t is not in core? -- correct me if am wrong.

@cstamas cstamas closed this Oct 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants