slachiewicz opened a new pull request, #1735: URL: https://github.com/apache/maven-mvnd/pull/1735
`maven-resolver-transport-wagon` sat in `<dependencyManagement>` but is the only occurrence of that artifactId anywhere in the repository — no module declares it, and it appears in no dependency tree across the 11 modules, so the managed version was pinning nothing. This is not a statement about the transport itself: Resolver still ships it as a first-class transport alongside `-file`, `-classpath` and `-http`, and it is not deprecated. It only stops mvnd holding a version opinion about something it never resolves. Verified: `mvn dependency:tree -Dincludes=org.apache.maven.resolver:maven-resolver-transport-wagon` matches nothing across all 11 modules, and `dependency:list` gives a byte-identical 54-artifact resolved set before and after. *This change was created with AI assistance.* -- 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]
