Conversation
Contributor
Author
|
Go ahead and merge this on my behalf if things look good, this was one of my biggest issues with testing changes in |
Contributor
|
I've been able to make changes without changing version numbers, since mavenLocal() is pulled in before the remote repos. But, this will make things easier than constantly publishing to maven local or if forgetting to run publish. |
LisoUseInAIKyrios
approved these changes
Feb 14, 2026
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
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.
This change makes it so that we don't need to fiddle with publishing to local maven + changing version numbers when testing changes to library or patcher. If those two repos are not checked out, then it will continue to pull the JARs from the defined Maven repositories; else Gradle will rebuild all the modified projects as needed.