-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.jaranow...@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-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 

Reply via email to