Ignore constraints of own projects ("DefaultProjectDependencyConstraint") #724
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
|
This looks like a nice improvement to me and sounds like a reasonable change to me. @anuraaga added this feature so maybe he should review it to make sure it's a good idea, as I am a little more naive about constraints and best practices there. |
|
Released in v46 |
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 multimodule projects having external constraints but also constraints to own sub projects it makes no sense to check for updates of the these own subprojects (when using checkConstraints=true)
Dependening on the number of own suprojects and also the network performance of the repositories this can give a huge performance boost (for example a few minutes vs. >2 hours in a concrete project)