Fix configuration resolution lock conflicts in parallel builds for Gradle 9#139
Merged
Fix configuration resolution lock conflicts in parallel builds for Gradle 9#139
Conversation
| netflix.nebula.dependency.recommender.provider.MavenBomRecommendationProvider mavenBomProvider = container.getMavenBomProvider(); | ||
| if (mavenBomProvider != null) { | ||
| try { | ||
| mavenBomProvider.getVersion("dummy", "dummy"); // Trigger lazy initialization |
| * @param configuration the Gradle configuration containing BOM dependencies | ||
| * @return a unique cache key based on the BOM coordinates | ||
| */ | ||
| private String createBomKeyFromConfiguration(Configuration configuration) { |
rpalcolea
force-pushed
the
more-gradle-9-work
branch
from
9afb519 to
1766d1a
Compare
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
2 participants
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.
Fix configuration resolution lock conflicts in parallel builds for Gradle 9
Resolves configuration resolution exclusive lock exceptions that occurred
when multiple subprojects attempted to resolve BOM configurations
simultaneously in parallel builds with Gradle 9.
Key changes:
and cache results by BOM coordinates for reuse across projects
exclusive locks are available, preventing resolution during
dependency resolution phase
to handle different subprojects with different BOM configurations
Fixes failing test: "recommendation is defined in root and we can see
proper reasons in submodule dependency insight" in parallel builds.