Do not apply PomDependencyManagementConfigurer when POM customization is disabled #392
Conversation
This file contains 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
Move each Gradle model types from execution phase to configuration phase
… is disabled Currently, PomDependencyManagementConfigurer is always applied even if it is manually disabled, which breaks the configuration cache
…ompatible with configuration cache way Remove Gradle model types from StandardPomDependencyManagementConfigurer, but allow overridden dependencies to be resolved eagerly or lazily
artemy-osipov
force-pushed
the
precache
branch
from
b229f7b
to
d1f6db6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In continuation of #391 (comment)
This PR is divided into 3 parts