Hi,
3/4 stack traces you posted contained the constructor frame with the
Objects.hash() call.
Hash code over so many collections can scale badly once the collections grow:
https://github.com/apache/maven-resolver/blob/145588be6d5b2c0111b5f367787d4c9347c326da/maven-resolver-util/src/main/java/or
closing this as obviously no interest from the dev team to have quality at
all.
We continue to strive in chaos.
This is the beginning of the end.
> On 7 Jun 2025, at 12:04, Claude Warren wrote:
>
> As a user.of the various libraries i for one appreciate this effort.
>
> Thank you to all
Hello,
I wanted to corroborate the performance issue in Maven 4-rc-3; I had sent a
message on the users@ list toward the end of December looking into
something similar, but lost track of it over the holidays and never came
back around to it. I do still have a jfr scan
https://drive.google.com/file/
On Sun, 25 May 2025 at 07:32, Olivier Lamy wrote:
>
> On Sat, 24 May 2025 at 19:36, Slawomir Jaranowski
> wrote:
> >
> > Hi,
> >
> > Simple question - where oficial release notes should be?
> >
>
> What do you mean by official :)
>
> > Are there some policies or recommendations for ASF projects g
I was able to run the Maven build (~900 modules) with the profiler.
Used `Apache Maven 4.0.0-rc-3` and the simplest possible command `mvn
initialize` which demonstrates reproducible degradation, the build is using
6 worker threads.
Maven 3 runs this command in 5 sec, Maven 4 - 6 minutes (no mistake
