slachiewicz opened a new issue, #3558: URL: https://github.com/apache/maven-surefire/issues/3558
`mvn dependency:analyze` and a comparison of the root POM against its parent (maven-parent 50) on master report a few POM leftovers. Each item below was checked against the sources. ### Dependencies `maven-surefire-report-plugin`: - `org.codehaus.plexus:plexus-xml` (compile) is declared but nothing in `src` imports `org.codehaus.plexus.util.xml`; it arrives through doxia-core anyway. - `commons-io:commons-io` (test) is declared but not used by any test. - `org.apache.maven.doxia:doxia-integration-tools` and `org.apache.maven.doxia:doxia-module-xhtml5` are used only by tests but reach the module transitively in compile scope; declaring them with `test` scope makes that explicit. - `javax.inject:javax.inject` is used by the main code but not declared. `surefire-report-parser`: - `org.assertj:assertj-core` (test) is declared but no test uses AssertJ. ### Plugin versions - The root POM pins `maven-site-plugin` 3.22.0, the same version maven-parent 50 manages, so the entry can go. ### Project metadata - `ciManagement` still points at the Jenkins job on ci-maven.apache.org, which returns 403 to anonymous visitors; the builds that gate pull requests run on GitHub Actions (`https://github.com/apache/maven-surefire/actions`). -- 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]
