[IDEA-367321] Find new custom handlers on recursive dependency discovery #3010
+30
−4
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.
The
GradleOrderEnumeratorHandler
would not be present in the root module as its not managed by Gradle. When the Gradle dependency is visited, we begin to recursively add its dependencies and pass in the old set of handlers from the original module. This leads to Gradle specific behavior not lighting up and resulting to incomplete classpath.Fixes this by discovering the new set of handlers before we start recursively adding the dependencies.