Volu Posted March 11, 2018 Posted March 11, 2018 Hey there, I decided that I want to try modding a bit but I have problems with the setup: C:\Users\lukas\Modding\forge-1.12.2-14.23.2.2611-mdk>gradlew setupDecompWorkSpac e eclipse To honour the JVM settings for this build a new JVM will be forked. Please consi der using the daemon: https://docs.gradle.org/2.14/userguide/gradle_daemon.html. FAILURE: Build failed with an exception. * What went wrong: Unable to start the daemon process. This problem might be caused by incorrect configuration of the daemon. For example, an unrecognized jvm option is used. Please refer to the user guide chapter on the daemon at https://docs.gradle.org/ 2.14/userguide/gradle_daemon.html Please read the following process output to find out more: ----------------------- Error occurred during initialization of VM Could not reserve enough space for 3145728KB object heap * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Whats weird is that my Pc should have enough RAM: I looked in the task manager and it told me 4 GB RAM were free. I decided to also runn the command with stacktrace to give you more information C:\Users\lukas\Modding\forge-1.12.2-14.23.2.2611-mdk>gradlew setupDecompWorkSpac e eclipse --stacktrace To honour the JVM settings for this build a new JVM will be forked. Please consi der using the daemon: https://docs.gradle.org/2.14/userguide/gradle_daemon.html. FAILURE: Build failed with an exception. * What went wrong: Unable to start the daemon process. This problem might be caused by incorrect configuration of the daemon. For example, an unrecognized jvm option is used. Please refer to the user guide chapter on the daemon at https://docs.gradle.org/ 2.14/userguide/gradle_daemon.html Please read the following process output to find out more: ----------------------- Error occurred during initialization of VM Could not reserve enough space for 3145728KB object heap * Try: Run with --info or --debug option to get more log output. * Exception is: org.gradle.api.GradleException: Unable to start the daemon process. This problem might be caused by incorrect configuration of the daemon. For example, an unrecognized jvm option is used. Please refer to the user guide chapter on the daemon at https://docs.gradle.org/ 2.14/userguide/gradle_daemon.html Please read the following process output to find out more: ----------------------- Error occurred during initialization of VM Could not reserve enough space for 3145728KB object heap at org.gradle.launcher.daemon.bootstrap.DaemonGreeter.parseDaemonOutput( DaemonGreeter.java:34) at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(D efaultDaemonStarter.java:153) at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(De faultDaemonStarter.java:136) at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon( DefaultDaemonConnector.java:111) at org.gradle.launcher.daemon.client.SingleUseDaemonClient.execute(Singl eUseDaemonClient.java:52) at org.gradle.launcher.daemon.client.SingleUseDaemonClient.execute(Singl eUseDaemonClient.java:37) at org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:43) at org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.jav a:173) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction. execute(CommandLineActionFactory.java:239) at org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction. execute(CommandLineActionFactory.java:212) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRunti meValidationAction.java:35) at org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRunti meValidationAction.java:24) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionRep ortingAction.java:33) at org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionRep ortingAction.java:22) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute( CommandLineActionFactory.java:205) at org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute( CommandLineActionFactory.java:169) at org.gradle.launcher.Main.doAction(Main.java:33) at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBoots trap.java:55) at org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.j ava:36) at org.gradle.launcher.GradleMain.main(GradleMain.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.ja va:30) at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:127) at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61) Thanks in advance! Quote
Ugdhar Posted March 11, 2018 Posted March 11, 2018 15 minutes ago, Volu said: Could not reserve enough space for 3145728KB object heap Make sure you have 64 bit java 8, and 4GB+ RAM Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 Just now, Ugdhar said: Make sure you have 64 bit java 8, and 4GB+ RAM I checked already. I got 64bit Jva 8 JRE and JDK and Taks manager tells me about 4.5 GB are free Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 (edited) with a command prompt Edited March 11, 2018 by Volu Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 C:\Users\lukas\Modding\forge-1.12.2-14.23.2.2611-mdk>java -d64 -version java version "1.8.0_161" Java(TM) SE Runtime Environment (build 1.8.0_161-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode) Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 The Java directories on my PC are C:\Program Files\Java\jdk1.8.0_161 C:\Program Files\Java\jre1.8.0_60 C:\Program Files\Java\jre1.8.0_161 C:\Program Files (x86)\Java\jdk1.8.0_161 C:\Program Files (x86)\Java\jre1.8.0_60 C:\Program Files (x86)\Java\jre1.8.0_161 Didnt notice till now I had that many Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 (edited) Is JRE included in JDK? Anyways, Ill deinstall every other Version and try again Edited March 11, 2018 by Volu Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 Thanks! I startd programming Java a year ago, but that is the first time I hear that! Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 Did it now, but now im told the JAVA_HOME variable iswrong. I set it to tthe directory but gradle still fails and tells me its set to the old one Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 19 minutes ago, diesieben07 said: Did you restart the relevant programs? You need to close all File explorer and all command line windows to reload the environment variables. By now I restarted my whole pc and it still doesnt work Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 But now it actually shows the directory set in JAVA_HOME. still its says its invalid ERROR: JAVA_HOME is set to an invalid directory: C:\Program Files\Java\jdk1.8.0 _161 Please set the JAVA_HOME variable in your environment to match the location of your Java installation. Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 It does. when I look in my program directories i find C:\Program Files\Java\jdk1.8.0_161 Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 I did set the System Variable new (nothing changed visually) but now it works Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 I added forge to the build path now, but cant import anything Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 (edited) I imported the folder to eclipse as a projecz and added that to the build path Edited March 11, 2018 by Volu Quote
Volu Posted March 11, 2018 Author Posted March 11, 2018 1 minute ago, diesieben07 said: Do not add stuff to the build path manually. The tutorial I found said I should do it 2 minutes ago, diesieben07 said: You need to run the gradle eclipse task Where can I find it? or do I have to use command lines again? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.