slachiewicz opened a new pull request, #648:
URL: https://github.com/apache/maven-project-info-reports-plugin/pull/648
The test classpath carried two artifacts to give Resolver a way of speaking
HTTP:
```xml
<artifactId>maven-resolver-transport-wagon</artifactId>
<artifactId>wagon-http-lightweight</artifactId>
```
Resolver has had its own HTTP transport since 1.0, so
`maven-resolver-transport-http` at the same `${resolverVersion}` does the same
job on its own. `maven-resolver-connector-basic` stays as it is — that is the
connector, not the transport.
`wagon-http-lightweight` is additionally marked for removal in Wagon 4.0.0,
and nothing here needs a Wagon provider in particular; it was only ever the
thing on the other side of the wagon transport.
**Verified:** `mvn test` gives 30 tests, 0 failures both before and after.
This came out of a survey of how Maven projects actually depend on Wagon.
The same pattern appears in maven-checkstyle-plugin and
maven-surefire-report-plugin, which are getting the same change. It does
**not** work in maven-doap-plugin, whose tests resolve through the legacy
`maven-compat` `WagonManager` and so genuinely need a Wagon provider registered
for `https` — that one is being left alone.
--
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]
