Use Resolver's own HTTP transport in tests - #1361
Merged
Merged
Conversation
The test repository session was wired through maven-resolver-transport-wagon and a shaded wagon-http, which is the transport Resolver keeps for build extensions that contribute a Wagon. Tests need none of that: they resolve over plain HTTPS, which maven-resolver-transport-http does directly. This is the stack maven-project-info-reports-plugin already uses.
michael-o
approved these changes
Aug 16, 2026
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.
The test repository session went through
maven-resolver-transport-wagonplus a shadedwagon-http. That transport exists so build extensions can contribute a Wagon provider; the tests resolve over plain HTTPS, whichmaven-resolver-transport-httpdoes on its own.Same stack
maven-project-info-reports-pluginalready uses.wagonVersionhad no other reader, so it goes too.Verified:
mvn clean test→ 69 tests, 0 failures, anddependency:treeno longer mentions Wagon at any scope.This change was created with AI assistance.