slachiewicz opened a new pull request, #942: URL: https://github.com/apache/maven-wagon/pull/942
`wagon-scm` has been on maven-scm 1.11.1, the line whose `maven-scm-manager-plexus` depends on `plexus-container-default` directly. maven-scm 2.0.0 moved that component to JSR-330 and dropped the dependency, so the exclusion added in 0e679c19 no longer belongs where it sits. **Drop the CVS tests.** maven-scm removed every CVS provider in 2.0.0-M1, so the suite cannot survive the upgrade. It already covered less than the git suite that drives the same `ScmWagon` code: `testWagonGetFileList`, `testWagonResourceExists` and `testWagonResourceNotExists` were stubbed out, and `supportsGetIfNewer` returned false. The one branch it exercised alone was `supportsPartialCheckout && isAlwaysRecursive`, a combination no remaining SCM type produces. **Upgrade maven-scm to 2.2.1.** The exclusion moves to `maven-scm-provider-gittest`, where `maven-scm-test` still reaches `plexus-container-default` through `maven-plugin-testing-harness` 3.3.0 and `plexus-archiver` 2.2. apache/maven-scm#1394 tracks that path, and maven-scm master has already replaced the harness with `plexus-testing`, so the exclusion can go once 2.2.1 is superseded. `GitScmTestUtils.setDefaultUser` became `setDefaultGitConfig` and now throws `IOException`. This is a dependency major bump on the 3.x line: anyone pairing `wagon-scm` with maven-scm 1.x provider jars has to move too. The site documentation still describes deploying to CVS. Removing those sections would drop published anchors, so it is left for a separate decision. Verified: `mvn -pl wagon-providers/wagon-scm -am test` → 28 tests green at both commits. *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]
