[PR] Drop maven-compat by moving the Maven baseline to 3.9.16 [maven-reporting-exec]

["slachiewicz (via GitHub)" <gi...@apache.org>]

slachiewicz opened a new pull request, #163:
URL: https://github.com/apache/maven-reporting-exec/pull/163

   Three things kept `maven-compat` in the test scope, and each goes with a different change:
   
   - maven-core 3.6.3 injects the compat `RepositorySystem` into `DefaultProjectBuildingHelper`, so the plugin-testing container would not boot without it; 3.9.12 removed that. `mavenVersion` moves to 3.9.16 with the matching `resolverVersion` 1.9.27.
   - `TestDefaultMavenReportExecutor` loaded maven-javadoc-plugin 3.4.0, which needs the compat `DefaultRepositoryMetadataManager`; the pin moves to 3.12.0.
   - The same test looked up `ArtifactRepositoryFactory`, a compat component; the static `MavenRepositorySystem.createArtifactRepository` in maven-core takes the same arguments.
   
   Part of apache/maven#8177.
   
   Verified: `mvn verify` → 4 tests, 0 failures, same as master.


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Drop maven-compat by moving the Maven baseline to 3.9.16 [maven-reporting-exec]

["slachiewicz (via GitHub)" <gi...@apache.org>]

slachiewicz merged PR #163:
URL: https://github.com/apache/maven-reporting-exec/pull/163


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org