Jump to content

Forge Workspace Setup Issue


YSPilot

Recommended Posts

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?

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

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.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

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.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.