Hi

think we have to make min=oldest supported branch/release otherwise it will
bite us for good reasons

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 <https://javaccino.dev/> founder (Java/.NET service - contact via
linkedin)


Le mer. 7 oct. 2026 à 23:33, Slawomir Jaranowski <[email protected]> a
écrit :

> Hi,
>
> Today I will go with 3.10.0 we have new API [1] like
>  - MessageBuilderFactory - we can drop maven-shared in many plugins
>  - we have java version in JavaToolchain
>
> 3.10.0 was released 2026-09-27 and I can see many issues with it ...
> form some of days 3.10.0 is default on GH runners [2]
>
>
> [1]
>
> https://maven.apache.org/docs/3.10.0/release-notes.html#new-api-and-updates-for-maven-plugins
> [2] https://github.com/actions/runner-images/releases
>
>
> On Wed, 7 Oct 2026 at 23:09, Sylwester Lachiewicz <[email protected]>
> wrote:
>
> > Hi,
> >
> > A year ago we discussed the minimum Maven version for ASF plugins [1].
> > Slawomir proposed four options, and his summary on 2025-11-13 lists ten
> > +1s for
> > 3.9.0. The compatibility plan was updated accordingly [2][3]:
> >
> > "In October 2025, Maven before 3.8.3 has been marked as EOL, meaning that
> > plugins should use 3.9.0 as minimum (as per Mailing List)"
> >
> > Many plugins still declare <prerequisites><maven>3.6.3</maven>, so I
> would
> > like
> > to clarify what that thread decided. Two questions:
> >
> > 1. Was that thread a formal vote, or a show of hands to be confirmed by a
> > [VOTE]?
> > 2. Should we raise the prerequisite to 3.9.0 across our plugins, or keep
> > the existing 3.6.3 and update the compatibility plan to reflect that?
> >
> > This is only about the outcome of last year's thread. This is only about
> > the outcome of last year's thread. It is not Maven 3.10.0 or about
> adopting
> > new APIs.
> >
> > [1] https://lists.apache.org/thread/s2dvm1jg37vhrkkkplfknk494c68zfyv
> > [2] https://github.com/apache/maven-site/pull/1456
> > [3] https://maven.apache.org/developers/compatibility-plan.html
> >
> > Regards,
> > Sylwester
> >
>
>
> --
> Sławomir Jaranowski
>

Reply via email to