+1 :)
On Wed, Jul 9, 2025 at 2:53 PM Tamás Cservenák wrote:
> I think not, Sergey?
>
> T
>
> On Wed, Jul 9, 2025 at 2:41 PM Gary Gregory
> wrote:
> >
> > I'm confused, does the -1 still stand?
> >
> > Gary
> >
> > On Wed, Jul 9, 2025, 05:28 Sergey Chernov
> wrote:
> >
> > > I tested 3.9.10 and
I think not, Sergey?
T
On Wed, Jul 9, 2025 at 2:41 PM Gary Gregory wrote:
>
> I'm confused, does the -1 still stand?
>
> Gary
>
> On Wed, Jul 9, 2025, 05:28 Sergey Chernov wrote:
>
> > I tested 3.9.10 and thought that the problem was still relevant (my
> > mistake).
> > Decided to reinsure to p
I'm confused, does the -1 still stand?
Gary
On Wed, Jul 9, 2025, 05:28 Sergey Chernov 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,
Nice, and many thanks for being vigilant here!
Thanks
T
On Wed, Jul 9, 2025 at 2:28 PM Sergey Chernov 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
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 wrote:
> Cool, good to hear this and many thanks!
>
> But now I am a bit c
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 wrote:
>
> Just checked the latest master of Maven4 (66e96ffcbeec9), the problem is
> not
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
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 mea
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 wrote:
>
> https://github.com/apache/maven/commit/45201347c4
-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
h
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/di
11 matches
Mail list logo
