"#5978: Maven/priming optimization" breaks loading broken project #6176
Labels
kind:bug
Bug report or fix
Maven
[ci] enable "build tools" tests
priority:critical
Showstopper issue that requires fixing in next release
Regression
This used to work!
Milestone
Body
While loading a project to test the jakartaEE support I noticed this issue:
The projects has a parent pom, that is loaded from an internal repository. I configured my
settings.xml
, so that this repository is only added if I run with the corresponding profile loaded. By default the special profile is not loaded and thus the project gets loaded without the right repository present.This situation can be simulated like this:
mvn install
from thedemo
repositorydemo
(I used my problematic artifact as basis for this hypothesis)master
from sourceant tryme
brokenmavenproject
maven projectYou can observe on the CLI output:
The UI becomes unresponsive, CPU usage as reported by VisualVM is around 10%, with spikes to 30%, heap usage is steadily growing. The Threaddump also seems to lead to maven.
Threaddump
I reached the conclusion, that #5978 is the offending commit, because I checked the commits related to maven and build that commit and its predecessor. The problem is reproducible with the commit and not without it.
As verifier I build master, reproduced the problem and reverted ad99e85 and could not reproduce it anymore.
@sdedic could you please have a look at this? Could there be a loop, that causes, the "broken" project to load in a loop and explain this problem?
Committer
The text was updated successfully, but these errors were encountered: