-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
support gradle 6 #10
support gradle 6 #10
Conversation
…o reduce warning.
…ctSet.<init>(Class) if possible
@NeRdTheNed Can you try with this branch? To try with this branch,
I know there're many warnings about features to be removed in 7.0. The warning will be fixed soon on another branch I will make. |
I've made a branch of my port of the More Bows mod to test the ForgeGradle snapshot, and it is compiling perfectly with Github actions! I've also tested the snapshot on my computer by removing all Gradle directories (Gradle home, build directory, .gradle), and then re-adding a Gradle 6.7 wrapper and compiling my mod, which works perfectly as well! The only "issue" I've found is that Gradle 6.7's new Java toolchain feature doesn't work with the snapshot. This is because setting sourceCompatibility or targetCompatibility is incompatible with toolchains, and ForgeGradle probably sets targetCompatibility when building a file. Here's some sample log output:
You can test this by changing these lines in the Gradle build script of my mod. This isn't a big issue (no one was able to use toolchains until Gradle 6.7, so no one was already using them with this fork!), and everything else works perfectly! |
I've just discovered a new issue: runClient doesn't work! Here's the output:
This should be reproducible by running "gradle runClient". runServer ("gradle runServer") has a similar issue:
|
Thanks for your testing! I can't remove setting sourceCompatibility and runtimeCompatibility because of backwards compatibility but I've found a workaround. The forge plugin sets sourceCompatibility and runtimeCompatibility only during applying so please set both sourceCompatibility and runtimeCompatibility as null after applying forge plugin. I tested with your project and this workaround works well. |
I'm sorry to forget to test runClient. I fixed this issue so please test with new version. |
I've now tested this with a new snapshot, and everything is working fine! I've even got GitHub actions to work with toolchains after a bit of work, which compiles perfectly! runClient is also now working perfectly fine, although I discovered a new bug that already exists in 1.2-1.0.2 during testing! I've written a seperate issue for it, because it's not caused by the new snapshot. |
Thanks for testing this plugin. I merge this branch! |
Fixes #9
Currently, build task runs successfully but deprecated Gradle features are used so I should fix it.
log of build with ForgeGradle-example: