I made a simple multi-module project generator which has some size
parameters.
Please see project description here
https://github.com/maven-turbo-reactor/maven-multiproject-generator
The good news is that it highlights the performance problem in comparison
between Maven3 and Maven4.
The generated project (which has 4k modules with default config, but zero
java source classes) takes 30sec on Maven3 and 1m40s on Maven4.
I'd like to point that it also declares usage of maven-enforcer-plugin with
this config:
```
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>3.3.0</version>
<executions>
<execution>
<id>enforce</id>
<configuration>
<rules>
<DependencyConvergence>
<uniqueVersions>false</uniqueVersions>
</DependencyConvergence>
</rules>
</configuration>
<goals>
<goal>enforce</goal>
</goals>
</execution>
</executions>
</plugin>
```
This plugin was my main suspect for the slowness, but it seems that any
plugin that iterates the dependencies (including any compilation plugin)
are affecting performance on Maven4. If enforcer plugin is removed, the
build is still slow on Maven4 (2.5x slower than Maven3).
On Thu, Jun 12, 2025 at 1:33 PM Martijn Dashorst <martijn.dasho...@gmail.com>
wrote:
> On Thu, Jun 12, 2025 at 1:48 AM Michael Bien <mbie...@gmail.com> wrote:
>
> > If there is a public project which hits this bottleneck I could take a
> > look and play
> > with some ideas to try to make this scale better. (I don't really want to
> > spam this thread
> > too much)
> >
>
> You could take a look at https://github.com/wicketstuff/core
>
> Lots and lots of projects..
>
> Martijn
>
