search

MinecraftForge / ForgeGradle

Minecraft mod development framework used by Forge and FML for the gradle build system
GNU Lesser General Public License v2.1
514 stars 443 forks source link

Cannot setup 1.7.10-forge1614 decompWorkspace #506

Closed FirokOtaku closed 6 years ago

FirokOtaku commented 6 years ago

I downloaded the latest src file, and tried to setup the decompWorkspace run with gradlew.bat setupDecompWorkspace -Dhttps.proxyHost=12 7.0.0.1 -Dhttp.proxyHost=127.0.0.1 -Dhttps.proxyPort=1080 -Dhttp.proxyPort=1080 -Dorg.gradle.jvmargs=-Xms2000m --info ( you can ignore the proxy settings) but it always failed with exception

how to fix this?

here is more information

D:\OneDrive\MinecraftForgeSRC\forge-1.7.10-10.13.4.1614-1.7.10-src>gradlew.bat setupDecompWorkspace -Dhttps.proxyHost=12 7.0.0.1 -Dhttp.proxyHost=127.0.0.1 -Dhttps.proxyPort=1080 -Dhttp.proxyPort=1080 -Dorg.gradle.jvmargs=-Xms2000m --info -- stacktrace To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: http://gradle.org/ docs/2.0/userguide/gradle_daemon.html. Starting Gradle daemon Starting daemon process: workingDir = C:\Users\a3517.gradle\daemon\2.0, daemonArgs: [C:\Program Files\Java\jdk1.8.0_121 \bin\java.exe, -Xms2000m, -Dfile.encoding=GBK, -cp, C:\Users\a3517.gradle\wrapper\dists\gradle-2.0-bin\5h57m9vra0mjv9qs 45oqtsb5c0\gradle-2.0\lib\gradle-launcher-2.0.jar, org.gradle.launcher.daemon.bootstrap.GradleDaemon, 2.0, C:\Users\a351 7.gradle\daemon, 120000, 79449938-2dee-499e-a478-3db5c4342c8e, -Xms2000m, -Dfile.encoding=GBK] Starting process 'Gradle build daemon'. Working directory: C:\Users\a3517.gradle\daemon\2.0 Command: C:\Program Files\J ava\jdk1.8.0_121\bin\java.exe -Xms2000m -Dfile.encoding=GBK -cp C:\Users\a3517.gradle\wrapper\dists\gradle-2.0-bin\5h57 m9vra0mjv9qs45oqtsb5c0\gradle-2.0\lib\gradle-launcher-2.0.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 2.0 C:\U sers\a3517.gradle\daemon 120000 79449938-2dee-499e-a478-3db5c4342c8e -Xms2000m -Dfile.encoding=GBK Successfully started process 'Gradle build daemon' An attempt to start the daemon took 4.348 secs. Connected to the daemon. Dispatching BuildAndStop{id=f9e358a3-0fcf-443d-ac00-cdbab2bd14ef.1, currentDir=D:\OneDrive\Mine craftForgeSRC\forge-1.7.10-10.13.4.1614-1.7.10-src} request. The client will now receive all logging from the daemon (pid: 16280). The daemon log file: C:\Users\a3517.gradle\daemon \2.0\daemon-16280.out.log Executing build with daemon context: DefaultDaemonContext[uid=79449938-2dee-499e-a478-3db5c4342c8e,javaHome=C:\Program F iles\Java\jdk1.8.0_121,daemonRegistryDir=C:\Users\a3517.gradle\daemon,pid=16280,idleTimeout=120000,daemonOpts=-Xms2000m ,-Dfile.encoding=GBK] Starting Build Settings evaluated using empty settings script. Projects loaded. Root project using build file 'D:\OneDrive\MinecraftForgeSRC\forge-1.7.10-10.13.4.1614-1.7.10-src\build .gradle'. Included projects: [root project 'forge-1.7.10-10.13.4.1614-1.7.10-src'] Evaluating root project 'forge-1.7.10-10.13.4.1614-1.7.10-src' using build file 'D:\OneDrive\MinecraftForgeSRC\forge-1.7 .10-10.13.4.1614-1.7.10-src\build.gradle'.

FAILURE: Build failed with an exception.

BUILD FAILED

Total time: 23.432 secs

braddevans commented 6 years ago

there is an error in the build.gradle could you send a copy of your build.gradle to check for the issue?

on line 18 is : 

apply plugin: 'forge'

are you using java 8?

liach commented 6 years ago

gradle clean cleanCache and then try again

FirokOtaku commented 6 years ago

there is an error in the build.gradle could you send a copy of your build.gradle to check for the issue?

on line 18 is :

apply plugin: 'forge'

are you using java 8?

I was using the default build.gradle downloaded from files.minecraftforge.net without making any changes. I followed the steps of the documentationhttps://mcforge.readthedocs.io/en/latest/gettingstarted/#terminal-free-intellij-idea-configuration Yes, I'm using java8, and the ide is IntelliJ IDEA.

Actually, after 40-hours trying now my workspace has successfully been set up, though I still dont know what happened. It seems all the things get running after I changed the "gradle wrapper" setting to "Use default gradle wrapper". Maybe there's some conflicts between forge gradle and offical gradle on my pc.

jriwanek commented 6 years ago

ForgeGradle uses Gradle, for 1.7.10, you can use 2.14-~4.4.1, if you're using newer than 4.4.1 for 1.7.10 it will NOT work.

LexManos commented 6 years ago

Use the forums.

FirokOtaku commented 6 years ago

ForgeGradle uses Gradle, for 1.7.10, you can use 2.14-~4.4.1, if you're using newer than 4.4.1 for 1.7.10 it will NOT work.

Ohh, that might be the point. The offical gradle I have is 4.8. Maybe you should remind us to pay attention in documentation, there are so many people meet the same problem.

Use the forums.

On this problem, forum has not provided any help. Every answer is in the same word: "you should run cleanCache" or "redownload the mdk", even "you should uninstall java8"

Anyway, thank you so much, guys!