+1 Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Javaccino founder (Java/.NET service - contact via linkedin)
Le sam. 8 nov. 2025 à 15:00, Matthias Bünger <[email protected]> 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] > >
