GradleStart not generated/recognised

[Big_Bad_E]

When I run genIntellijRuns I get this error:

java.lang.NullPointerException
        at net.minecraftforge.gradle.common.Constants.addXml(Constants.java:297)
        at net.minecraftforge.gradle.user.UserBasePlugin.injectIntellijRuns(UserBasePlugin.java:1305)
        at net.minecraftforge.gradle.user.UserBasePlugin$14.execute(UserBasePlugin.java:1213)
        at net.minecraftforge.gradle.user.UserBasePlugin$14.execute(UserBasePlugin.java:1176)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:621)

So I saw a report on the GitHub saying delete .idea files and run gradlew idea genIntellijRuns.

Same error, but a client/server configuration are created. It worked for a 1.8.9 project, and I get the run config in this 1.12.2 project, but when I run it I get this error:

Error: Could not find or load main class GradleStart

gradlew runClient works once but it stops (I am trying to run ThermalDynamics with the files from their github) with an error that there are two jei jars.

If I run it again no window opens and I get the "task success" message.

If I run genIntellijRuns and idea genIntellijRuns it says task successful without the error.

 

I tried deleting the .gradle and reruning setupDecompWorkspace and genIntellijRuns, this time it made the StartGradle file but Intellij doesn't find it.

Edited August 24, 2019 by Big_Bad_E

[DaemonUmbra]

Chances are you need to set the module in the runConfig to the main module.

[Big_Bad_E]

  On 8/24/2019 at 12:58 AM, DaemonUmbra said:

Chances are you need to set the module in the runConfig to the main module.

Expand  

I set it to main

 

FIGURED IT OUT! Intellij decided to set my JDK to none instead of JDK 1.8 for some reason.

Edited August 24, 2019 by Big_Bad_E

[DaemonUmbra]

Oh this is on the task and not actually running it, I see.

When you say it worked for 1.8.9, you're not using the same build.gradle are you?

[Big_Bad_E]

  On 8/24/2019 at 1:04 AM, DaemonUmbra said:

Oh this is on the task and not actually running it, I see.

When you say it worked for 1.8.9, you're not using the same build.gradle are you?

Expand  

No no no, definitely not. It was the lack of a Java JDK.