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.mo...@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.mo...@gmail.com> > wrote: > > > > > > https://github.com/apache/maven/commit/45201347c4 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
