Fix: make ProjectIndex thread-safe for parallel builds (backport #12832) - #12926
Merged
Conversation
Backport of #12832 to maven-4.0.x. Switch ProjectIndex backing maps from HashMap to ConcurrentHashMap to fix root cause of index corruption under parallel builds (-T). Add forkedProject null guard and enriched error messages. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Aug 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backport of #12832 to
maven-4.0.x.ProjectIndexbacking maps fromHashMaptoConcurrentHashMapto fix root cause of index corruption under parallel builds (-T)forkedProjectnull guard (theindicesnull guard was already backported via Handle missing project index in forked executions #12911)Test plan
MojoExecutorForkedExecutionTestcovers the null-guard behavior🤖 Generated with Claude Code