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/07/09 07:17:21 UTC
[HEADS UP] Maven 3.9.11 release
Hi,
I would like to release Maven 3.9.11
We have resolved issues in Maven core:
https://github.com/apache/maven/issues?q=milestone%3A3.9.11
and in reslover 1.9.24
https://github.com/apache/maven-resolver/releases/tag/maven-resolver-1.9.24
I published a build at:
https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.11-SNAPSHOT/
--
Sławomir Jaranowski
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] Maven 3.9.11 release
Posted by Matthias Bünger <mb...@apache.org>.
No - Maven 3.9. is not EoL.
Only 3.8 is close to it (preparations are in work)
Am 31.07.2025 um 15:13 schrieb Sergey Chernov:
> I thought Maven 3.9.x is EoL.
> The 3.9.11 was released mostly because of the critical issue fix.
>
> On Thu, Jul 31, 2025 at 11:17 AM Mark Derricutt <ma...@talios.com> wrote:
>
>> Doh, got my email replies mixed up - thought this was referring to a new
>> patch release - tho I’ve been running 11/12-SNAPHOT with Guice 6 ok still
>> stands for a upcoming patch release...
>>
>>
>>
>> On 31 Jul 2025 at 9:14:11 PM, Mark Derricutt <ma...@talios.com> wrote:
>>
>>> I’ve been running locally with Guice updated to version 6 with no issues.
>>> Sadly, it doesn’t resolve any warnings when running under new JDKs, but
>> it
>>> would still be nice to see it updated, perhaps.
>>>
>>> Not for any specific reason or need, I've been having dependency updates
>>> on my mind lately.
>>>
>>> Should I raise a ticket?
>>>
>>> --
>>> "Great artists are extremely selfish and arrogant things" — Steven
>> Wilson,
>>> Porcupine Tree
>>>
>>>
>>> On 10 Jul 2025 at 2:49:29 AM, Sergey Chernov <se...@gmail.com>
>>> wrote:
>>>
>>>> +1 :)
>>>>
>>>> On Wed, Jul 9, 2025 at 2:53 PM Tamás Cservenák <ta...@cservenak.net>
>>>> wrote:
>>>>
>>>> I think not, Sergey?
>>>>
>>>>
>>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] Maven 3.9.11 release
Posted by Sergey Chernov <se...@gmail.com>.
I thought Maven 3.9.x is EoL.
The 3.9.11 was released mostly because of the critical issue fix.
On Thu, Jul 31, 2025 at 11:17 AM Mark Derricutt <ma...@talios.com> wrote:
> Doh, got my email replies mixed up - thought this was referring to a new
> patch release - tho I’ve been running 11/12-SNAPHOT with Guice 6 ok still
> stands for a upcoming patch release...
>
>
>
> On 31 Jul 2025 at 9:14:11 PM, Mark Derricutt <ma...@talios.com> wrote:
>
> > I’ve been running locally with Guice updated to version 6 with no issues.
> > Sadly, it doesn’t resolve any warnings when running under new JDKs, but
> it
> > would still be nice to see it updated, perhaps.
> >
> > Not for any specific reason or need, I've been having dependency updates
> > on my mind lately.
> >
> > Should I raise a ticket?
> >
> > --
> > "Great artists are extremely selfish and arrogant things" — Steven
> Wilson,
> > Porcupine Tree
> >
> >
> > On 10 Jul 2025 at 2:49:29 AM, Sergey Chernov <se...@gmail.com>
> > wrote:
> >
> >> +1 :)
> >>
> >> On Wed, Jul 9, 2025 at 2:53 PM Tamás Cservenák <ta...@cservenak.net>
> >> wrote:
> >>
> >> I think not, Sergey?
> >>
> >>
> >>
>
Re: [HEADS UP] Maven 3.9.11 release
Posted by Mark Derricutt <ma...@talios.com>.
Doh, got my email replies mixed up - thought this was referring to a new
patch release - tho I’ve been running 11/12-SNAPHOT with Guice 6 ok still
stands for a upcoming patch release...
On 31 Jul 2025 at 9:14:11 PM, Mark Derricutt <ma...@talios.com> wrote:
> I’ve been running locally with Guice updated to version 6 with no issues.
> Sadly, it doesn’t resolve any warnings when running under new JDKs, but it
> would still be nice to see it updated, perhaps.
>
> Not for any specific reason or need, I've been having dependency updates
> on my mind lately.
>
> Should I raise a ticket?
>
> --
> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
> Porcupine Tree
>
>
> On 10 Jul 2025 at 2:49:29 AM, Sergey Chernov <se...@gmail.com>
> wrote:
>
>> +1 :)
>>
>> On Wed, Jul 9, 2025 at 2:53 PM Tamás Cservenák <ta...@cservenak.net>
>> wrote:
>>
>> I think not, Sergey?
>>
>>
>>
Re: [HEADS UP] Maven 3.9.11 release
Posted by Mark Derricutt <ma...@talios.com>.
I’ve been running locally with Guice updated to version 6 with no issues.
Sadly, it doesn’t resolve any warnings when running under new JDKs, but it
would still be nice to see it updated, perhaps.
Not for any specific reason or need, I've been having dependency updates on
my mind lately.
Should I raise a ticket?
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On 10 Jul 2025 at 2:49:29 AM, Sergey Chernov <se...@gmail.com> wrote:
> +1 :)
>
> On Wed, Jul 9, 2025 at 2:53 PM Tamás Cservenák <ta...@cservenak.net>
> wrote:
>
> I think not, Sergey?
>
>
>
Re: [HEADS UP] Maven 3.9.11 release
Posted by Sergey Chernov <se...@gmail.com>.
+1 :)
On Wed, Jul 9, 2025 at 2:53 PM Tamás Cservenák <ta...@cservenak.net> wrote:
> I think not, Sergey?
>
> T
>
> On Wed, Jul 9, 2025 at 2:41 PM Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > I'm confused, does the -1 still stand?
> >
> > Gary
> >
> > On Wed, Jul 9, 2025, 05:28 Sergey Chernov <se...@gmail.com>
> wrote:
> >
> > > I tested 3.9.10 and thought that the problem was still relevant (my
> > > mistake).
> > > Decided to reinsure to prevent releasing this.
> > >
> > > binaries staged by Slawek should not be affected
> > >
> > > On Wed, Jul 9, 2025 at 2:22 PM Tamás Cservenák <ta...@cservenak.net>
> > > wrote:
> > >
> > > > Cool, good to hear this and many thanks!
> > > >
> > > > But now I am a bit confused: what did you test then?
> > > > Or you say that binaries staged by Slawek are affected?
> > > >
> > > > Thanks
> > > > T
> > > >
> > > > On Wed, Jul 9, 2025 at 2:19 PM Sergey Chernov <
> serega.morph@gmail.com>
> > > > wrote:
> > > > >
> > > > > Just checked the latest master of Maven4 (66e96ffcbeec9), the
> problem
> > > is
> > > > > not reproducible here.
> > > > > And it's not reproducible on latest maven-3.9.x (a8a44dc0ad3b)
> anymore.
> > > > > I bisected the fixing commit, it's this one
> > > > > https://github.com/apache/maven/pull/2489 by Alan Zimmer.
> > > > > Great news, it's okay now and thanks Alan.
> > > > >
> > > > > So, the only affected release is 3.9.10 and 3.9.11 is not under
> risk
> > > (at
> > > > > least with mentioned problem).
> > > > > Will do more tests to cover other scenarios.
> > > > >
> > > > >
> > > > > On Wed, Jul 9, 2025 at 12:46 PM Tamás Cservenák <
> tamas@cservenak.net>
> > > > wrote:
> > > > >
> > > > > > Wow, thanks Sergey for testing!
> > > > > >
> > > > > > Can you please check Maven master as well (with your project, as
> > > there
> > > > > > is no reproducer yet)?
> > > > > >
> > > > > > As if Maven 4/master behaves the same, I propose to rollback
> > > > > > https://github.com/apache/maven/issues/10553 fully (from Maven
> 3 and
> > > > > > 4).
> > > > > >
> > > > > > But if Maven 4 behaves, it would mean that Maven 3 and Maven 4
> > > > > > "drifted" apart so much that the "simple backport" is not
> enough, and
> > > > > > Maven 3 needs more, much more.
> > > > > >
> > > > > >
> > > > > > Thanks
> > > > > > T
> > > > > >
> > > > > > On Wed, Jul 9, 2025 at 12:07 PM Sergey Chernov <
> > > serega.morph@gmail.com
> > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > I forgot to mention, that if this commit is reverted
> > > > > > https://github.com/apache/maven/commit/45201347c4 the problem
> is
> > > > gone.
> > > > > > So it’s obviously related.
> > > > > > >
> > > > > > > > On 9 Jul 2025, at 12:05, Sergey Chernov <
> serega.morph@gmail.com>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > https://github.com/apache/maven/commit/45201347c4
> > > > > > >
> > > > > >
> > > > > >
> ---------------------------------------------------------------------
> > > > > > 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: [HEADS UP] Maven 3.9.11 release
Posted by Tamás Cservenák <ta...@cservenak.net>.
I think not, Sergey?
T
On Wed, Jul 9, 2025 at 2:41 PM Gary Gregory <ga...@gmail.com> wrote:
>
> I'm confused, does the -1 still stand?
>
> Gary
>
> On Wed, Jul 9, 2025, 05:28 Sergey Chernov <se...@gmail.com> wrote:
>
> > I tested 3.9.10 and thought that the problem was still relevant (my
> > mistake).
> > Decided to reinsure to prevent releasing this.
> >
> > binaries staged by Slawek should not be affected
> >
> > On Wed, Jul 9, 2025 at 2:22 PM Tamás Cservenák <ta...@cservenak.net>
> > wrote:
> >
> > > Cool, good to hear this and many thanks!
> > >
> > > But now I am a bit confused: what did you test then?
> > > Or you say that binaries staged by Slawek are affected?
> > >
> > > Thanks
> > > T
> > >
> > > On Wed, Jul 9, 2025 at 2:19 PM Sergey Chernov <se...@gmail.com>
> > > wrote:
> > > >
> > > > Just checked the latest master of Maven4 (66e96ffcbeec9), the problem
> > is
> > > > not reproducible here.
> > > > And it's not reproducible on latest maven-3.9.x (a8a44dc0ad3b) anymore.
> > > > I bisected the fixing commit, it's this one
> > > > https://github.com/apache/maven/pull/2489 by Alan Zimmer.
> > > > Great news, it's okay now and thanks Alan.
> > > >
> > > > So, the only affected release is 3.9.10 and 3.9.11 is not under risk
> > (at
> > > > least with mentioned problem).
> > > > Will do more tests to cover other scenarios.
> > > >
> > > >
> > > > On Wed, Jul 9, 2025 at 12:46 PM Tamás Cservenák <ta...@cservenak.net>
> > > wrote:
> > > >
> > > > > Wow, thanks Sergey for testing!
> > > > >
> > > > > Can you please check Maven master as well (with your project, as
> > there
> > > > > is no reproducer yet)?
> > > > >
> > > > > As if Maven 4/master behaves the same, I propose to rollback
> > > > > https://github.com/apache/maven/issues/10553 fully (from Maven 3 and
> > > > > 4).
> > > > >
> > > > > But if Maven 4 behaves, it would mean that Maven 3 and Maven 4
> > > > > "drifted" apart so much that the "simple backport" is not enough, and
> > > > > Maven 3 needs more, much more.
> > > > >
> > > > >
> > > > > Thanks
> > > > > T
> > > > >
> > > > > On Wed, Jul 9, 2025 at 12:07 PM Sergey Chernov <
> > serega.morph@gmail.com
> > > >
> > > > > wrote:
> > > > > >
> > > > > > I forgot to mention, that if this commit is reverted
> > > > > https://github.com/apache/maven/commit/45201347c4 the problem is
> > > gone.
> > > > > So it’s obviously related.
> > > > > >
> > > > > > > On 9 Jul 2025, at 12:05, Sergey Chernov <se...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > https://github.com/apache/maven/commit/45201347c4
> > > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > 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: [HEADS UP] Maven 3.9.11 release
Posted by Gary Gregory <ga...@gmail.com>.
I'm confused, does the -1 still stand?
Gary
On Wed, Jul 9, 2025, 05:28 Sergey Chernov <se...@gmail.com> wrote:
> I tested 3.9.10 and thought that the problem was still relevant (my
> mistake).
> Decided to reinsure to prevent releasing this.
>
> binaries staged by Slawek should not be affected
>
> On Wed, Jul 9, 2025 at 2:22 PM Tamás Cservenák <ta...@cservenak.net>
> wrote:
>
> > Cool, good to hear this and many thanks!
> >
> > But now I am a bit confused: what did you test then?
> > Or you say that binaries staged by Slawek are affected?
> >
> > Thanks
> > T
> >
> > On Wed, Jul 9, 2025 at 2:19 PM Sergey Chernov <se...@gmail.com>
> > wrote:
> > >
> > > Just checked the latest master of Maven4 (66e96ffcbeec9), the problem
> is
> > > not reproducible here.
> > > And it's not reproducible on latest maven-3.9.x (a8a44dc0ad3b) anymore.
> > > I bisected the fixing commit, it's this one
> > > https://github.com/apache/maven/pull/2489 by Alan Zimmer.
> > > Great news, it's okay now and thanks Alan.
> > >
> > > So, the only affected release is 3.9.10 and 3.9.11 is not under risk
> (at
> > > least with mentioned problem).
> > > Will do more tests to cover other scenarios.
> > >
> > >
> > > On Wed, Jul 9, 2025 at 12:46 PM Tamás Cservenák <ta...@cservenak.net>
> > wrote:
> > >
> > > > Wow, thanks Sergey for testing!
> > > >
> > > > Can you please check Maven master as well (with your project, as
> there
> > > > is no reproducer yet)?
> > > >
> > > > As if Maven 4/master behaves the same, I propose to rollback
> > > > https://github.com/apache/maven/issues/10553 fully (from Maven 3 and
> > > > 4).
> > > >
> > > > But if Maven 4 behaves, it would mean that Maven 3 and Maven 4
> > > > "drifted" apart so much that the "simple backport" is not enough, and
> > > > Maven 3 needs more, much more.
> > > >
> > > >
> > > > Thanks
> > > > T
> > > >
> > > > On Wed, Jul 9, 2025 at 12:07 PM Sergey Chernov <
> serega.morph@gmail.com
> > >
> > > > wrote:
> > > > >
> > > > > I forgot to mention, that if this commit is reverted
> > > > https://github.com/apache/maven/commit/45201347c4 the problem is
> > gone.
> > > > So it’s obviously related.
> > > > >
> > > > > > On 9 Jul 2025, at 12:05, Sergey Chernov <se...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > https://github.com/apache/maven/commit/45201347c4
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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: [HEADS UP] Maven 3.9.11 release
Posted by Tamás Cservenák <ta...@cservenak.net>.
Nice, and many thanks for being vigilant here!
Thanks
T
On Wed, Jul 9, 2025 at 2:28 PM Sergey Chernov <se...@gmail.com> wrote:
>
> I tested 3.9.10 and thought that the problem was still relevant (my
> mistake).
> Decided to reinsure to prevent releasing this.
>
> binaries staged by Slawek should not be affected
>
> On Wed, Jul 9, 2025 at 2:22 PM Tamás Cservenák <ta...@cservenak.net> wrote:
>
> > Cool, good to hear this and many thanks!
> >
> > But now I am a bit confused: what did you test then?
> > Or you say that binaries staged by Slawek are affected?
> >
> > Thanks
> > T
> >
> > On Wed, Jul 9, 2025 at 2:19 PM Sergey Chernov <se...@gmail.com>
> > wrote:
> > >
> > > Just checked the latest master of Maven4 (66e96ffcbeec9), the problem is
> > > not reproducible here.
> > > And it's not reproducible on latest maven-3.9.x (a8a44dc0ad3b) anymore.
> > > I bisected the fixing commit, it's this one
> > > https://github.com/apache/maven/pull/2489 by Alan Zimmer.
> > > Great news, it's okay now and thanks Alan.
> > >
> > > So, the only affected release is 3.9.10 and 3.9.11 is not under risk (at
> > > least with mentioned problem).
> > > Will do more tests to cover other scenarios.
> > >
> > >
> > > On Wed, Jul 9, 2025 at 12:46 PM Tamás Cservenák <ta...@cservenak.net>
> > wrote:
> > >
> > > > Wow, thanks Sergey for testing!
> > > >
> > > > Can you please check Maven master as well (with your project, as there
> > > > is no reproducer yet)?
> > > >
> > > > As if Maven 4/master behaves the same, I propose to rollback
> > > > https://github.com/apache/maven/issues/10553 fully (from Maven 3 and
> > > > 4).
> > > >
> > > > But if Maven 4 behaves, it would mean that Maven 3 and Maven 4
> > > > "drifted" apart so much that the "simple backport" is not enough, and
> > > > Maven 3 needs more, much more.
> > > >
> > > >
> > > > Thanks
> > > > T
> > > >
> > > > On Wed, Jul 9, 2025 at 12:07 PM Sergey Chernov <serega.morph@gmail.com
> > >
> > > > wrote:
> > > > >
> > > > > I forgot to mention, that if this commit is reverted
> > > > https://github.com/apache/maven/commit/45201347c4 the problem is
> > gone.
> > > > So it’s obviously related.
> > > > >
> > > > > > On 9 Jul 2025, at 12:05, Sergey Chernov <se...@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > https://github.com/apache/maven/commit/45201347c4
> > > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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: [HEADS UP] Maven 3.9.11 release
Posted by Sergey Chernov <se...@gmail.com>.
I tested 3.9.10 and thought that the problem was still relevant (my
mistake).
Decided to reinsure to prevent releasing this.
binaries staged by Slawek should not be affected
On Wed, Jul 9, 2025 at 2:22 PM Tamás Cservenák <ta...@cservenak.net> wrote:
> Cool, good to hear this and many thanks!
>
> But now I am a bit confused: what did you test then?
> Or you say that binaries staged by Slawek are affected?
>
> Thanks
> T
>
> On Wed, Jul 9, 2025 at 2:19 PM Sergey Chernov <se...@gmail.com>
> wrote:
> >
> > Just checked the latest master of Maven4 (66e96ffcbeec9), the problem is
> > not reproducible here.
> > And it's not reproducible on latest maven-3.9.x (a8a44dc0ad3b) anymore.
> > I bisected the fixing commit, it's this one
> > https://github.com/apache/maven/pull/2489 by Alan Zimmer.
> > Great news, it's okay now and thanks Alan.
> >
> > So, the only affected release is 3.9.10 and 3.9.11 is not under risk (at
> > least with mentioned problem).
> > Will do more tests to cover other scenarios.
> >
> >
> > On Wed, Jul 9, 2025 at 12:46 PM Tamás Cservenák <ta...@cservenak.net>
> wrote:
> >
> > > Wow, thanks Sergey for testing!
> > >
> > > Can you please check Maven master as well (with your project, as there
> > > is no reproducer yet)?
> > >
> > > As if Maven 4/master behaves the same, I propose to rollback
> > > https://github.com/apache/maven/issues/10553 fully (from Maven 3 and
> > > 4).
> > >
> > > But if Maven 4 behaves, it would mean that Maven 3 and Maven 4
> > > "drifted" apart so much that the "simple backport" is not enough, and
> > > Maven 3 needs more, much more.
> > >
> > >
> > > Thanks
> > > T
> > >
> > > On Wed, Jul 9, 2025 at 12:07 PM Sergey Chernov <serega.morph@gmail.com
> >
> > > wrote:
> > > >
> > > > I forgot to mention, that if this commit is reverted
> > > https://github.com/apache/maven/commit/45201347c4 the problem is
> gone.
> > > So it’s obviously related.
> > > >
> > > > > On 9 Jul 2025, at 12:05, Sergey Chernov <se...@gmail.com>
> > > wrote:
> > > > >
> > > > > https://github.com/apache/maven/commit/45201347c4
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > 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: [HEADS UP] Maven 3.9.11 release
Posted by Tamás Cservenák <ta...@cservenak.net>.
Cool, good to hear this and many thanks!
But now I am a bit confused: what did you test then?
Or you say that binaries staged by Slawek are affected?
Thanks
T
On Wed, Jul 9, 2025 at 2:19 PM Sergey Chernov <se...@gmail.com> wrote:
>
> Just checked the latest master of Maven4 (66e96ffcbeec9), the problem is
> not reproducible here.
> And it's not reproducible on latest maven-3.9.x (a8a44dc0ad3b) anymore.
> I bisected the fixing commit, it's this one
> https://github.com/apache/maven/pull/2489 by Alan Zimmer.
> Great news, it's okay now and thanks Alan.
>
> So, the only affected release is 3.9.10 and 3.9.11 is not under risk (at
> least with mentioned problem).
> Will do more tests to cover other scenarios.
>
>
> On Wed, Jul 9, 2025 at 12:46 PM Tamás Cservenák <ta...@cservenak.net> wrote:
>
> > Wow, thanks Sergey for testing!
> >
> > Can you please check Maven master as well (with your project, as there
> > is no reproducer yet)?
> >
> > As if Maven 4/master behaves the same, I propose to rollback
> > https://github.com/apache/maven/issues/10553 fully (from Maven 3 and
> > 4).
> >
> > But if Maven 4 behaves, it would mean that Maven 3 and Maven 4
> > "drifted" apart so much that the "simple backport" is not enough, and
> > Maven 3 needs more, much more.
> >
> >
> > Thanks
> > T
> >
> > On Wed, Jul 9, 2025 at 12:07 PM Sergey Chernov <se...@gmail.com>
> > wrote:
> > >
> > > I forgot to mention, that if this commit is reverted
> > https://github.com/apache/maven/commit/45201347c4 the problem is gone.
> > So it’s obviously related.
> > >
> > > > On 9 Jul 2025, at 12:05, Sergey Chernov <se...@gmail.com>
> > wrote:
> > > >
> > > > https://github.com/apache/maven/commit/45201347c4
> > >
> >
> > ---------------------------------------------------------------------
> > 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: [HEADS UP] Maven 3.9.11 release
Posted by Sergey Chernov <se...@gmail.com>.
Just checked the latest master of Maven4 (66e96ffcbeec9), the problem is
not reproducible here.
And it's not reproducible on latest maven-3.9.x (a8a44dc0ad3b) anymore.
I bisected the fixing commit, it's this one
https://github.com/apache/maven/pull/2489 by Alan Zimmer.
Great news, it's okay now and thanks Alan.
So, the only affected release is 3.9.10 and 3.9.11 is not under risk (at
least with mentioned problem).
Will do more tests to cover other scenarios.
On Wed, Jul 9, 2025 at 12:46 PM Tamás Cservenák <ta...@cservenak.net> wrote:
> Wow, thanks Sergey for testing!
>
> Can you please check Maven master as well (with your project, as there
> is no reproducer yet)?
>
> As if Maven 4/master behaves the same, I propose to rollback
> https://github.com/apache/maven/issues/10553 fully (from Maven 3 and
> 4).
>
> But if Maven 4 behaves, it would mean that Maven 3 and Maven 4
> "drifted" apart so much that the "simple backport" is not enough, and
> Maven 3 needs more, much more.
>
>
> Thanks
> T
>
> On Wed, Jul 9, 2025 at 12:07 PM Sergey Chernov <se...@gmail.com>
> wrote:
> >
> > I forgot to mention, that if this commit is reverted
> https://github.com/apache/maven/commit/45201347c4 the problem is gone.
> So it’s obviously related.
> >
> > > On 9 Jul 2025, at 12:05, Sergey Chernov <se...@gmail.com>
> wrote:
> > >
> > > https://github.com/apache/maven/commit/45201347c4
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [HEADS UP] Maven 3.9.11 release
Posted by Tamás Cservenák <ta...@cservenak.net>.
Wow, thanks Sergey for testing!
Can you please check Maven master as well (with your project, as there
is no reproducer yet)?
As if Maven 4/master behaves the same, I propose to rollback
https://github.com/apache/maven/issues/10553 fully (from Maven 3 and
4).
But if Maven 4 behaves, it would mean that Maven 3 and Maven 4
"drifted" apart so much that the "simple backport" is not enough, and
Maven 3 needs more, much more.
Thanks
T
On Wed, Jul 9, 2025 at 12:07 PM Sergey Chernov <se...@gmail.com> wrote:
>
> I forgot to mention, that if this commit is reverted https://github.com/apache/maven/commit/45201347c4 the problem is gone. So it’s obviously related.
>
> > On 9 Jul 2025, at 12:05, Sergey Chernov <se...@gmail.com> wrote:
> >
> > https://github.com/apache/maven/commit/45201347c4
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] Maven 3.9.11 release
Posted by Sergey Chernov <se...@gmail.com>.
I forgot to mention, that if this commit is reverted https://github.com/apache/maven/commit/45201347c4 the problem is gone. So it’s obviously related.
> On 9 Jul 2025, at 12:05, Sergey Chernov <se...@gmail.com> wrote:
>
> https://github.com/apache/maven/commit/45201347c4
Re: [HEADS UP] Maven 3.9.11 release
Posted by Sergey Chernov <se...@gmail.com>.
-1 (nb)
I’ve discovered an issue with module subset running (when we specify “-pl” with multiple modules) and running CLI style “surefire:test” instead of phase style).
So my command looks like “mvn surefire:test -pl :module1,:module2,:module3,:module4"
The problem appears since this commit https://github.com/apache/maven/commit/45201347c4 [MNG-8256]
I’ve already complained that Maven hangs and there was a fix https://github.com/apache/maven/commit/1da6ce5123 [MNG-8396]
Now it does not hang, but there is another issue: many logs like this
[INFO] --- surefire:3.4.0:test (default-cli) @ Spaces ---
[WARNING] *************************************************************
[WARNING] * The *
[WARNING] * org.apache.maven.plugins:maven-surefire-plugin:3.4.0:test *
[WARNING] * mojo is already being executed on the project *
[WARNING] * platform.server.core.general:Spaces. This mojo execution *
[WARNING] * will be blocked until the mojo is done. *
[WARNING] *************************************************************
[WARNING] *************************************************************
[WARNING] * The *
[WARNING] * org.apache.maven.plugins:maven-surefire-plugin:3.4.0:test *
[WARNING] * mojo is already being executed on the project *
[WARNING] * platform.server.core.general:Spaces. This mojo execution *
[WARNING] * will be blocked until the mojo is done. *
[WARNING] *************************************************************
and then I can see that some of the goals are executed more than once, some are skipped.
This problem is SEVERE! And this bug appeared in 3.9.10, no issues with 3.9.9.
This only happens with parallel execution (like -bmultithreaded), no issues with single thread. And it happens in huge multi-module build. My bet it’s a race condition.
Just in case: it’s not related to Turbo builder (that was discussed in another topic)
I planned to submit an issue, but could not make a project reproducing the problem so wanted to inspect it myself (as didn’t expect 3.9.11 so far).
Any advice how to inspect this is welcome.
My advise is to postpone the 3.9.11.
> On 9 Jul 2025, at 09:17, Slawomir Jaranowski <s....@gmail.com> wrote:
>
> Hi,
>
> I would like to release Maven 3.9.11
>
> We have resolved issues in Maven core:
> https://github.com/apache/maven/issues?q=milestone%3A3.9.11
>
> and in reslover 1.9.24
> https://github.com/apache/maven-resolver/releases/tag/maven-resolver-1.9.24
>
> I published a build at:
> https://dist.apache.org/repos/dist/dev/maven/maven-3/3.9.11-SNAPSHOT/
>
>
> --
> Sławomir Jaranowski
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>