Jenkins Maven installation clean up
## Summary
For each Jenkins instance, there is a list of Maven tool installations available to make it easy to select different Maven versions for a build job and avoid having to download Maven separately for each build.
Over the years, this list has accumulated many Maven versions. **It's time to clean them up.**
Here is the plan:
* Maven versions 3.8.x and before have reached their end of life and are no longer supported. Those versions will be removed on **September 14, 2026**.
* Only the last three minor versions of Maven 3.9.x will be kept (currently 3.9.16, 3.9.12 and 3.9.11). Older versions of Maven 3.9.x will be removed on **September 14, 2026**
* Projects that still need to support Maven versions that we are planning to remove will need to provide those specific Maven versions for their builds themselves.
* If you want to avoid updating your build configurations, we recommend always using `apache-maven-latest`.
* In the light of the upcoming 4.x release of Maven, we have added two new Maven installations (as requested in https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/work_items/7696):
* `apache-maven-3-latest` - pointing to the latest Maven 3.x version
* `apache-maven-4-latest` - pointing to the latest Maven 4.x version (currently pointing to Maven version 4.0.0-rc-5)
Here is a list of Maven versions that are still used by Jenkins instances:
| Maven version | Count | JIPPs |
|---------------|-------|-------|
| apache-maven-3.9.16 | 1 | technology.m2e |
| apache-maven-3.9.12 | 6 | modeling.mwe<br/>modeling.xpect<br/>science.statet<br/>technology.rdf4j<br/>tools.shellwax<br/>tools.tracecompass |
| apache-maven-3.9.11 | 8 | ee4j.agentic-ai<br/>ee4j.glassfish<br/>ee4j.jpa<br/>ee4j.validation<br/>iot.kura<br/>modeling.hawk<br/>science.statet<br/>technology.rdf4j |
| apache-maven-3.9.9 | 12 | adoptium.mc<br/>ee4j.glassfish<br/>ee4j.jakartaee-platform<br/>iot.kura<br/>modeling.henshin<br/>modeling.xtext<br/>rt.virgo<br/>technology.efxclipse<br/>technology.lsat<br/>technology.scout<br/>technology.tea<br/>technology.trace4cps |
| apache-maven-3.9.6 | 7 | iot.kura<br/>modeling.viatra<br/>rt.ecf<br/>science.statet<br/>technology.dash<br/>technology.lyo |
| apache-maven-3.9.5 | 3 | modeling.edapt<br/>modeling.epsilon<br/>tools.tracecompass |
| apache-maven-3.9.3 | 2 | modeling.qvtd<br/>technology.simrel |
| apache-maven-3.9.2 | 2 | rt.rap<br/>technology.osee |
| apache-maven-3.9.1 | 13 | ee4j.agentic-ai<br/>ee4j.glassfish<br/>ee4j.jpa<br/>ee4j.validation<br/>iot.kura<br/>modeling.hawk<br/>modeling.mwe<br/>modeling.xpect<br/>science.statet<br/>technology.m2e<br/>technology.rdf4j<br/>tools.shellwax<br/>tools.tracecompass |
| apache-maven-3.9.0 | 2 | ee4j.glassfish<br/>technology.microprofile |
| apache-maven-3.8.6 | 7 | ecd.emfcloud<br/>modeling.edapt<br/>modeling.gemoc<br/>modeling.viatra<br/>modeling.xtext<br/>technology.microprofile<br/>tools.mylyn |
| apache-maven-3.8.5 | 2 | modeling.xtext<br/>technology.osee |
| apache-maven-3.8.4 | 1 | ee4j.jakartaee-platform |
| apache-maven-3.8.3 | 0 | not used |
| apache-maven-3.8.2 | 1 | technology.lyo |
| apache-maven-3.8.1 | 1 | ecd.emfcloud |
| apache-maven-3.6.3 | 8 | ecd.jkube<br/>iot.embed-cdt<br/>locationtech.spatial4j<br/>rt.rap<br/>science.statet<br/>technology.osee<br/>tools.orbit |
| apache-maven-3.6.0 | 1 | ee4j.eclipselink |
| apache-maven-3.5.4 | 4 | iot.kura<br/>technology.egit<br/>technology.osee<br/>technology.xwt |
| apache-maven-3.3.9 | 3 | modeling.egf<br/>rt.rap<br/>technology.xwt |
| apache-maven-3.2.5 | 0 | not used |
Please note that the scan results might not be conclusive. It can also contain false-positives.
issue