Forge Workspace Setup Issue

[YSPilot]

I'm not entirely sure how to describe my problem, but I am going to try. Pretty much I was trying to update my 1.7.2 ForgeGradle files, and I deleted everything in the folder, and re did the setup. I did the setupDecompWorkspace and the eclipse Commands in gradle. However, when I get into eclipse, It sees the packages as being there, but its not seeing any classes. Im not sure what I am doing. Any suggestions?

[YSPilot]

forgeSrc-1.7.2-10.12.0.1011-sources.jar? Its there and loaded.

[YSPilot]

Its registering any class files being in there.

 

[Acaeris]

I'm having this issue as well.

 

Forge 1.7.2-10.12.0.1012

 

Both setupDecompWorkspace and eclipse commands completed successfully.

 

In Netbeans I get the following project errors with the example mod:

package net.minecraft.init does not exist
package cpw.mods.fml.common does not exist
package cpw.mods.fml.common.Mod does not exist
package cpw.mods.fml.common.event does not exist

 

In the projects list I can see those packages though:

 

forge1.7.2
+ Dependencies
  + Compile for main
    + forgeSrc-1.7.2-10.12.0.1012.jar
      + cpw.mods.fml.common
          Mod
      + cpw.mods.fml.common.event
          FMLInitializationEvent
      + net.minecraft.init
          Blocks

[YSPilot]

After Much playing around. I found that the following Works:

Clear the Forge folder(the one containing the gradlew.bat) and re-extract from the zip. Run the command:

gradlew setupDevWorkspace eclipse

 

Hope that helps anyone else!

[Acaeris]

After Much playing around. I found that the following Works:

Clear the Forge folder(the one containing the gradlew.bat) and re-extract from the zip. Run the command:

gradlew setupDevWorkspace eclipse

 

Hope that helps anyone else!

 

This didn't solve it in my case.

[GotoLink]

gradlew --refresh-dependencies eclipse

That should set the libraries appropriately.

[Acaeris]

No success with that either.

 

[karyonix]

Info

In #1012, the .classpath file entry forgeSrc is wrong it must be forgeBin.

In #1012, if you run only setupDecompWorkspace eclipse without setupDevWorkspace, it will not build forgeBin jar file.

 

Instruction

1. Delete ".classspath" file in your forge directory.

2. Run gradlew setupDevWorkspace setupDecompWorkspace eclipse

3. edit the file .classpath

change from

<classpathentry sourcepath="C:/Users/user/.gradle/caches/minecraft/net/minecraftforge/forge/1.7.2-10.12.0.1012/forgeSrc-1.7.2-10.12.0.1012-sources.jar" kind="lib" path="C:/Users/user/.gradle/caches/minecraft/net/minecraftforge/forge/1.7.2-10.12.0.1012/forgeSrc-1.7.2-10.12.0.1012.jar" exported="true"/>

to

<classpathentry sourcepath="C:/Users/user/.gradle/caches/minecraft/net/minecraftforge/forge/1.7.2-10.12.0.1012/forgeSrc-1.7.2-10.12.0.1012-sources.jar" kind="lib" path="C:/Users/user/.gradle/caches/minecraft/net/minecraftforge/forge/1.7.2-10.12.0.1012/forgeBin-1.7.2-10.12.0.1012.jar" exported="true"/>

4. Run eclipse -data forgedir\eclipse

[Acaeris]

Unfortunately, that hasn't seemed to work in my case either. After making that change Forge no longer appears in the dependency list at all. I checked the Gradle cache and both the forgeSrc and forgeBin files are there and the .classpath entry points to them correctly but they are not showing in Netbeans, all other entries in the .classpath file are showing fine.

[Noppes]

Info

In #1012, the .classpath file entry forgeSrc is wrong it must be forgeBin.

In #1012, if you run only setupDecompWorkspace eclipse without setupDevWorkspace, it will not build forgeBin jar file.

 

Instruction

1. Delete ".classspath" file in your forge directory.

2. Run gradlew setupDevWorkspace setupDecompWorkspace eclipse

3. edit the file .classpath

change from

<classpathentry sourcepath="C:/Users/user/.gradle/caches/minecraft/net/minecraftforge/forge/1.7.2-10.12.0.1012/forgeSrc-1.7.2-10.12.0.1012-sources.jar" kind="lib" path="C:/Users/user/.gradle/caches/minecraft/net/minecraftforge/forge/1.7.2-10.12.0.1012/forgeSrc-1.7.2-10.12.0.1012.jar" exported="true"/>

to

<classpathentry sourcepath="C:/Users/user/.gradle/caches/minecraft/net/minecraftforge/forge/1.7.2-10.12.0.1012/forgeSrc-1.7.2-10.12.0.1012-sources.jar" kind="lib" path="C:/Users/user/.gradle/caches/minecraft/net/minecraftforge/forge/1.7.2-10.12.0.1012/forgeBin-1.7.2-10.12.0.1012.jar" exported="true"/>

4. Run eclipse -data forgedir\eclipse

That seems to fix my workspace. Whenever I run gradlew build it still gives the errors though

[LexManos]

Abrar fucked another thing up yay -.-

For now though setupCIWorkspace and then build should work. This should only effect decomp workspace as it's trying to recompile the decompiled source so that line numbers match up.

[GotoLink]

This doesn't happen with IntellijIdea for some reason.

[Acaeris]

I eventually got it working. I basically ran setupDecompWorkspace, deleted the .classpath file, setupDevWorkspace and then manually added the sourcepath entries to the new .classpath file. Why it worked this way around and not the other I do not know.

[LexManos]

This seems to be fixed on the gradle end, anyone having issues should make sure to --refresh-dependencies

[Texenox]

This seems to be fixed on the gradle end, anyone having issues should make sure to --refresh-dependencies

 

Will this also work in 10.12.0.1013 with Eclipse?

[LexManos]

ForgeGradle is independent of Forge version. So yes.

We fix something in the Gradle plugin, it fixes it for ALL versions that use the gradle plugin.

That way when shit like Mojang changing server happenes, we can fix it once and not have to deal with the old crap.