falafel

I was able to get Forge Gradle working fine with Java8 - at least on the command line - by adding this snippet to my build.gradle: configurations.all { resolutionStrategy.eachDependency { DependencyResolveDetails details -> if (details.requested.group == 'org.ow2.asm' && details.requested.name == 'asm-debug-all' && details.requested.version == '4.1') { //prefer different version which contains some necessary fixes details.useVersion '5.0.1' } } } This makes Gradle use the Java8 compatible version of the asm lib. I still had some issues with IntelliJ integration (didn't try eclipse). Forge seems to work, but it gets tons of warnings because the ClassLoader isn't set up correctly. Running ./gradlew debugClient and remote debugging from IntelliJ seems to work perfectly though. I have no idea if a mod you make with this trick actually works with a binary Forge install, but it at least unblocks debugging until Forge has full support for Java8.

Hello everyone. *Full disclosure, I am a noob @ Gradle & brute-forced my way through this I am working on a mod that requires Java 1.8 (Nashorn JS Engine) - and had trouble getting MC Forge to compile and run for me. It seems that Forge's version of objectweb's bytecode manipulation library has issues with Java 1.8. Objectweb's latest version fixes the issues & you can use their latest library by adding the following code to your mod's build.gradle: Before adding this, I got build errors like: and I also got runtime errors after IntelliJ builds about class load errors (seemingly also related to the objectweb bytecode manipulation libs) but I couldn't reproduce the logs after fixing the issue (I still don't understand Gradle caching ) Hope this helps those working with Java 8.