-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modify the project structure & update various portions #151
Conversation
# Conflicts: # build.gradle # gradle.properties
whoops i deleted a line or two too many
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A very needed change, thanks a lot. After this I'll add support for refreshVersions
as well.
Please also add to TESTING.md
information about how the test mods can be used by uncommenting lines in fabric/build.gradle
and forge/build.gradle
now.
I seem to be getting this warning whenever I build when the test mod is included with
Can we do anything about this? |
It seems like loom just doesn't work very well when referencing other subprojects. Don't add that stuff for now (keep TESTING.md as-is as well). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
def cf = libs.versions.overrides.curseforge.get() | ||
def mr = libs.versions.overrides.modrinth.get() | ||
|
||
ext.curseforge_mc_version = cf == 'mc' ? minecraft_version : cf |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
gradle/libs.versions.toml
Test mods and individual modules are less likely to fall out of sync with each other now, and with one single version location management, it is likely a lot easier to update versions in the future.