slachiewicz opened a new issue, #13766:
URL: https://github.com/apache/maven/issues/13766

   Sweep across the Maven estate's tests now that the minimum is Maven 3.9.0: 
IT and test projects stop pinning Maven, plugin and Java versions below that 
baseline where the version is incidental, verify scripts become real 
assertions, and nothing runs JUnit 3 or 4 any more.
   
   ## Inventory (default branches, 2026-10-31)
   
   Across 138 active apache/maven-*, codehaus-plexus and mojohaus repositories:
   
   - 48 repositories had test or IT POMs with Maven below 3.9, 
`<prerequisites>` below 3.9, source/target 1.2–1.7, core plugins below 3.0, 
BeanShell scripts, or JUnit 3/4 tests.
   - JUnit 3/4: 24 test classes (21 in maven-resolver-ant-tasks), 1 Hamcrest 
class, 21 build POMs declaring `junit`, `junit-vintage-engine` or Hamcrest, and 
482 fixture files in 48 repositories.
   
   ## What stays
   
   A fixture keeps its old version when the version is the point of the test, 
and each PR lists those:
   
   - plugins whose job is versions (release rewrite fixtures, enforcer rules, 
version reports);
   - invoker selectors such as `invoker.maven.version`;
   - Java-level fixtures in signature and rule checkers (animal-sniffer, PMD, 
Checkstyle);
   - POM fixtures where `junit:junit` is only a coordinate that is never 
resolved or run (model and inheritance tests, dependency analysis);
   - fixtures that test JUnit 4 handling itself.
   
   ## Pull requests
   
   - [ ] apache/maven-assembly-plugin
   - [ ] apache/maven-javadoc-plugin
   - [ ] apache/maven-checkstyle-plugin
   - [ ] apache/maven-pmd-plugin
   - [ ] apache/maven-filtering
   - [ ] apache/maven-remote-resources-plugin
   - [ ] apache/maven-site-plugin
   - [ ] apache/maven-antrun-plugin
   - [ ] apache/maven-apache-resources
   - [ ] apache/maven-help-plugin
   - [ ] apache/maven-resources-plugin
   
   More follow as the remaining repositories are done. Two items need more than 
a fixture change:
   
   - buildnumber-maven-plugin gets JUnit 4 and Hamcrest only through 
`takari-plugin-testing`, which its IT base class uses; removing them means 
replacing that harness.
   - The quickstart archetype's `junitVersion=4.x` option is a user-facing 
template change and gets its own PR labelled `removed`.
   


-- 
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]

Reply via email to