summary of previous episodes (over years):
- because why impose a restriction when it just works without that 
restriction?
- because in the past, we did not help users find what plugin version they 
could use: this was solved with System Requirements history feature 
(implemented not so long ago)


which does not mean today is not the right day to go from Maven 3.6.3 to 3.9.x
and update our plan accordingly:
https://maven.apache.org/developers/compatibility-plan.html

Just remembering everybody the result of years of discussions on that exact 
topic

Regards,

Hervé

Le samedi 8 novembre 2025, 15:00:05 CET Matthias Bünger a écrit :
> +1 (nb)
> 
> I never understood why we keep the long EOL version 3.6.x as a minimum
> for plugins.
> 
> Matthias
> 
> Am 08.11.2025 um 13:51 schrieb Slawomir Jaranowski:
> > Hi,
> > 
> > Maven 3.8.x is now marked as EOL [1]
> > 
> > We have a page which describes the minimum requirements for a plugin
> > [2] after the Maven version marking EOL.
> > Last time we used the last EOL version, so consequently we should
> > start using 3.8.3 for it.
> > 
> > Currently we only use Maven 3.9.x in GitHub CI [3], so if we dedicate
> > to use 3.8.3 we need to add it to be sure that plugins still support
> > such a version.
> > 
> > We also can start using 3.9.0 for plugins and not need to test the EOL
> > version.
> > 
> > The question is which version of Maven should be now used as minimum
> > requirements in plugins?
> > 
> > 1. 3.8.3 - with add to CI matrix
> > 2. 3.8.3 - without  adding in CI matrix
> > 3. 3.9.0 - no extra version in CI matrix is needed
> > 4. don't care about it ... take a hope that will be not a problem
> > 
> > So which one way do you prefer?
> > 
> > [1] https://github.com/apache/maven-site/pull/842
> > [2] https://maven.apache.org/developers/compatibility-plan.html
> > [3] https://github.com/apache/maven-gh-actions-shared/pull/207
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to