You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Slawomir Jaranowski <s....@gmail.com> on 2025/11/08 12:51:00 UTC

Minimum Maven requirements for ASF plugins

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

-- 
Sławomir Jaranowski

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Sergey Chernov <se...@gmail.com>.
+1

On Wed, Nov 12, 2025 at 10:39 AM Benjamin Marwell <bm...@apache.org>
wrote:

> +1 for 3.9.x (we could use a more recent version than 3.9.0 due to bugs in
> early versions of 3.9).
>
> - Ben
>
> On 8 November 2025 13:51:00 CET, Slawomir Jaranowski <
> s.jaranowski@gmail.com> wrote:
> >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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: Minimum Maven requirements for ASF plugins

Posted by Benjamin Marwell <bm...@apache.org>.
+1 for 3.9.x (we could use a more recent version than 3.9.0 due to bugs in early versions of 3.9).

- Ben

On 8 November 2025 13:51:00 CET, Slawomir Jaranowski <s....@gmail.com> wrote:
>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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Olivier Lamy <ol...@apache.org>.
On Sat, 8 Nov 2025 at 23:48, Slawomir Jaranowski <s....@gmail.com> wrote:
>
> I'm also +1 for 3.9.0

+1

>
> On Sat, 8 Nov 2025 at 13:51, Slawomir Jaranowski <s....@gmail.com> wrote:
> >
> > 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
> >
> > --
> > Sławomir Jaranowski
>
>
>
> --
> Sławomir Jaranowski
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Slawomir Jaranowski <s....@gmail.com>.
I'm also +1 for 3.9.0

On Sat, 8 Nov 2025 at 13:51, Slawomir Jaranowski <s....@gmail.com> wrote:
>
> 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
>
> --
> Sławomir Jaranowski



-- 
Sławomir Jaranowski

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Hervé Boutemy <he...@free.fr.INVALID>.
does it mean you don't agree on upgrading minium to 3.9.0 irrespective of it 
being necessary?

Le mercredi 12 novembre 2025, 11:23:50 CET Christoph Läubrich a écrit :
> I won't see this as a requirement (!) so if a plugin is using 3.6.x API
> and is happy with that then fair enough.
> 
> But no one should expect that we do extra work (e.g reflection hacks,
> workarounds, missing APIs...) or test explicitly with 3.6.x when instead
> we could bump to 3.9.x instead.
> 
> So similar with minimum java, one might still use 1.8 but if there is a
> need for new features it can be upgrade without special consideration.
> 
> Am 12.11.25 um 08:40 schrieb Hervé Boutemy:
> > 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: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Christoph Läubrich <ma...@laeubi-soft.de>.
I won't see this as a requirement (!) so if a plugin is using 3.6.x API 
and is happy with that then fair enough.

But no one should expect that we do extra work (e.g reflection hacks, 
workarounds, missing APIs...) or test explicitly with 3.6.x when instead 
we could bump to 3.9.x instead.

So similar with minimum java, one might still use 1.8 but if there is a 
need for new features it can be upgrade without special consideration.

Am 12.11.25 um 08:40 schrieb Hervé Boutemy:
> 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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Hervé Boutemy <he...@free.fr.INVALID>.
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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Manfred Moser <ma...@simpligility.ca>.
+1

On 2025-11-08 09:20, Romain Manni-Bucau wrote:
> +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 <mb...@apache.org> 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: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Romain Manni-Bucau <rm...@gmail.com>.
+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 <mb...@apache.org> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: Minimum Maven requirements for ASF plugins

Posted by Matthias Bünger <mb...@apache.org>.
+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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Slawomir Jaranowski <s....@gmail.com>.
Hi,

Summary:

For requirements as 3.9.0 we have:

+1: Christoph Läubrich, Sylwester Lachiewicz, Slawomir Jaranowski, Matthias
Bünger, Romain Manni-Bucau, Manfred Moser, Olivier Lamy, Hervé Boutemy,
Benjamin Marwell, Sergey Chernov


So I have prepared:
https://github.com/apache/maven-site/pull/1456

On Sat, 8 Nov 2025 at 13:51, Slawomir Jaranowski <s....@gmail.com>
wrote:

> 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
>
> --
> Sławomir Jaranowski
>


-- 
Sławomir Jaranowski

Re: Minimum Maven requirements for ASF plugins

Posted by Slawomir Jaranowski <s....@gmail.com>.
On Sat, 8 Nov 2025 at 13:59, Gary Gregory <ga...@gmail.com> wrote:
>
> Hi,
>
> What will happen on GitHub CI when Maven 4 is released? Do you expect
> CI build to magically switch from 3.9.x to 4.0.0?
>

There are now magic actions ....
We have default matrix builds for plugins until we don't change
nothing will happened.

More plugins also have a Maven 4 in build matrix even though it is
targeted as Maven 3.x - we check compatibility of old plugins with new
Maven versions.
Like in:
https://github.com/apache/maven-clean-plugin/actions/workflows/maven-verify.yml?query=branch%3Amaven-clean-plugin-3.x
we have Maven 3.x and 4.x on build matrix

For the Maven 4 version of plugins we only have a Maven 4 in matrix:
like in:
https://github.com/apache/maven-clean-plugin/actions/workflows/maven-verify.yml?query=branch%3Amaster

The discussion is about what minimum version Maven 3.x plugins should claim.

> TY,
> Gary
>
> On Sat, Nov 8, 2025 at 7:51 AM Slawomir Jaranowski
> <s....@gmail.com> wrote:
> >
> > 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
> >
> > --
> > Sławomir Jaranowski
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>


-- 
Sławomir Jaranowski

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Gary Gregory <ga...@gmail.com>.
Hi,

What will happen on GitHub CI when Maven 4 is released? Do you expect
CI build to magically switch from 3.9.x to 4.0.0?

TY,
Gary

On Sat, Nov 8, 2025 at 7:51 AM Slawomir Jaranowski
<s....@gmail.com> wrote:
>
> 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
>
> --
> Sławomir Jaranowski
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Re: Minimum Maven requirements for ASF plugins

Posted by Sylwester Lachiewicz <sl...@gmail.com>.
+1 for 3.9.0 as minimum for plugins

sob., 8 lis 2025, 14:28 użytkownik Christoph Läubrich <ma...@laeubi-soft.de>
napisał:

> +1 for Maven 3.9 as minimum for plugins
>
> Am 08.11.25 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>

Re: Minimum Maven requirements for ASF plugins

Posted by Christoph Läubrich <ma...@laeubi-soft.de>.
+1 for Maven 3.9 as minimum for plugins

Am 08.11.25 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org