Lower mavenLocal priority in test projects of gradle-plugin#5208
Merged
Lower mavenLocal priority in test projects of gradle-plugin#5208
Conversation
This avoids some conflicts with caches
MatkovIvan
requested changes
Jan 21, 2025
Member
MatkovIvan
left a comment
MatkovIvan
left a comment
There was a problem hiding this comment.
It doesn't seem right. Locally built 0.0.0-SNAPSHOT should be used instead of one from dev repo
Member
Author
|
@MatkovIvan I didn't change the repositories order for plugins. Only for libraries. |
MatkovIvan
approved these changes
Jan 21, 2025
Member
MatkovIvan
left a comment
MatkovIvan
left a comment
There was a problem hiding this comment.
Not a big deal anyway. If it helps with CI cache issue - let's merge it
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.
mavenLocal as a top prirotiy in the list of library repositories causes some cache issues on CI. And sometimes locally