Jump to content
Currently supported: All versions

gradlew setupDecompWorkspace --refresh-dependencies fail

JMAS

By JMAS
in ForgeGradle

 Share

Recommended Posts

JMAS Tree Puncher

JMAS

Posted
Posted (edited)

I'm learning Java specifically for Minecraft mods for my son.  His preferred version is 1.7.10, because of other mods made for that version that do not exist in other versions of Minecraft.

The forge version is the 1558 build for 1.7.10.  Java version is 1.8.0_231.  Was working with 111 but had repeated issues.
I have installed, uninstalled and re-installed Java repeatedly, making sure that I have a fresh slate for each failed attempt with Forge in Eclipse.
I am attempting to follow the instructions at: https://techwiseacademy.com/minecraft-modding-setting-up-your-environment/ for modding.
I followed the instructions to the letter, and additionally am taking the Mr. Crayfish course at:

 

but when I attempt to "run" the code at 4:03 in the video, I receive the error: "Errors exist in required project(s):  

                                                                                                                                                               forge-1.7.10-10.13.4.1558-1.7.10-src

                                                                                                                                                                Proceed with launch?"

 

which I suspect stems from an incomplete install of the command: gradlew setupDecompWorkspace --refresh-dependencies
(from the first URL).

 

Here is the output from the command window:

H:\MinecraftModding\forge-1.7.10-10.13.4.1558-1.7.10-src>gradlew setupDecompWorkspace --refresh-dependencies
#################################################
         ForgeGradle 1.2-SNAPSHOT-fb514d3
  https://github.com/MinecraftForge/ForgeGradle
#################################################
               Powered by MCP unknown
            http://modcoderpack.com
         by: Searge, ProfMobius, Fesh0r,
         R4wk, ZeuX, IngisKahn, bspkrs
#################################################
:extractMcpData UP-TO-DATE
:getVersionJson
:extractUserDev UP-TO-DATE
:genSrgs SKIPPED
:extractNatives UP-TO-DATE
:getAssetsIndex
:getAssets
:makeStart
[ant:javac] warning: [options] bootstrap class path not set in conjunction with -source 1.6
[ant:javac] 1 warning
:downloadMcpTools SKIPPED
:downloadClient SKIPPED
:downloadServer SKIPPED
:mergeJars SKIPPED
:deobfuscateJar SKIPPED
:decompile SKIPPED
:processSources
Injecting fml files
Applying fml patches
Applying forge patches
:remapJar SKIPPED
:extractMinecraftSrc SKIPPED
:recompMinecraft SKIPPED
:repackMinecraft SKIPPED
:setupDecompWorkspace

BUILD SUCCESSFUL

Total time: 42.894 secs
H:\MinecraftModding\forge-1.7.10-10.13.4.1558-1.7.10-src>

 

You can see a number of things skipped from ":downloadMcpTools" forward.

I have spent the last week troubleshooting, trying to get Eclipse to cooperate, changing the Path and JAVA-HOME, adding and removing Java, updating Java, manually trying to import data files into Eclipse, re-running gradlew repeatedly with different parameters.  I have succeeded in getting Eclipse to change from 200 red X's in the package manager down to just one, but of course it is the critical one that snags my entire operation.  "Minecraft" has never showed up in the package manager.

Half my hair has been pulled out and I have to admit the need for help.
If Eclipse worked with Forge, that would be really great.  I really need your help because I can't get it to do so on my own.

I submitted this as a bug with Eclipse only to have them bounce me to you.

Thanks in advance for helping solve this,
Marc


Dear Marc,

this is the bug tracker of Eclipse. I can't see a bug with Eclipse itself here. It is more a usage problem with the Minecraft project. Please address your issue in their forum:
https://www.minecraftforge.net/forum/

The Gradle command concluded successfully, but there will be reasons why there are still problems in your workspace. I don't see anything here, and please don't expect that we try to follow the mentioned video for reproduction.

You may attach screenshots and maybe the error log here, or ask in the Eclipse foum
https://www.eclipse.org/forums/index.php/i/

Kind regards,
~Karsten
[reply] [−] 
Comment 2 
Karsten Thoms   2019-11-29 03:24:43 EST 

*** Bug 553602 has been marked as a duplicate of this bug. ***

1 Eclipse main workspace.png

2 Eclipse workspace sub.png

3 missing.png

Current errors.png

Edited by JMAS
additional version information added
JMAS Tree Puncher

JMAS

Posted
  • Author
Posted

Additionally, I installed this off of the "C:" drive because Microsoft permissions issues were adding a ton of errors, which were resolved by installing as Administrator on the H: drive.

DaemonUmbra Reality Controller

DaemonUmbra

Posted
Posted

1.7.10 is no longer supported on this forum due to its age.

Please update to a modern version of Minecraft to receive support.

This is my Forum Signature, I am currently attempting to transform it into a small guide for fixing easier issues using spoiler blocks to keep things tidy.

 

As the most common issue I feel I should put this outside the main bulk:

The only official source for Forge is https://files.minecraftforge.net, and the only site I trust for getting mods is CurseForge.

If you use any site other than these, please take a look at the StopModReposts project and install their browser extension, I would also advise running a virus scan.

 

For players asking for assistance with Forge please expand the spoiler below and read the appropriate section(s) in its/their entirety.

Spoiler

Logs (Most issues require logs to diagnose):

Spoiler

Please post logs using one of the following sites (Thank you Lumber Wizard for the list):

https://gist.github.com/: 100MB Requires member (Free)

https://pastebin.com/: 512KB as guest, 10MB as Pro ($$$)

https://hastebin.com/: 400KB

Do NOT use sites like Mediafire, Dropbox, OneDrive, Google Drive, or a site that has a countdown before offering downloads.

 

What to provide:

...for Crashes and Runtime issues:

Minecraft 1.14.4 and newer:

Post debug.log

Older versions:

Please update...

 

...for Installer Issues:

Post your installer log, found in the same place you ran the installer

This log will be called either installer.log or named the same as the installer but with .log on the end

Note for Windows users:

Windows hides file extensions by default so the installer may appear without the .jar extension then when the .log is added the log will appear with the .jar extension

 

Where to get it:

Mojang Launcher: When using the Mojang launcher debug.log is found in .minecraft\logs.

 

Curse/Overwolf: If you are using the Curse Launcher, their configurations break Forge's log settings, fortunately there is an easier workaround than I originally thought, this works even with Curse's installation of the Minecraft launcher as long as it is not launched THROUGH Twitch:

Spoiler
  1. Make sure you have the correct version of Forge installed (some packs are heavily dependent on one specific build of Forge)
  2. Make a launcher profile targeting this version of Forge.
  3. Set the launcher profile's GameDir property to the pack's instance folder (not the instances folder, the folder that has the pack's name on it).
  4. Now launch the pack through that profile and follow the "Mojang Launcher" instructions above.

Video:

Spoiler

 

 

 

or alternately, 

 

Fallback ("No logs are generated"):

If you don't see logs generated in the usual place, provide the launcher_log.txt from .minecraft

 

Server Not Starting:

Spoiler

If your server does not start or a command window appears and immediately goes away, run the jar manually and provide the output.

 

Reporting Illegal/Inappropriate Adfocus Ads:

Spoiler

Get a screenshot of the URL bar or copy/paste the whole URL into a thread on the General Discussion board with a description of the Ad.

Lex will need the Ad ID contained in that URL to report it to Adfocus' support team.

 

Posting your mod as a GitHub Repo:

Spoiler

When you have an issue with your mod the most helpful thing you can do when asking for help is to provide your code to those helping you. The most convenient way to do this is via GitHub or another source control hub.

When setting up a GitHub Repo it might seem easy to just upload everything, however this method has the potential for mistakes that could lead to trouble later on, it is recommended to use a Git client or to get comfortable with the Git command line. The following instructions will use the Git Command Line and as such they assume you already have it installed and that you have created a repository.

 

  1. Open a command prompt (CMD, Powershell, Terminal, etc).
  2. Navigate to the folder you extracted Forge’s MDK to (the one that had all the licenses in).
  3. Run the following commands:
    1. git init
    2. git remote add origin [Your Repository's URL]
      • In the case of GitHub it should look like: https://GitHub.com/[Your Username]/[Repo Name].git
    3. git fetch
    4. git checkout --track origin/master
    5. git stage *
    6. git commit -m "[Your commit message]"
    7. git push
  4. Navigate to GitHub and you should now see most of the files.
    • note that it is intentional that some are not synced with GitHub and this is done with the (hidden) .gitignore file that Forge’s MDK has provided (hence the strictness on which folder git init is run from)
  5. Now you can share your GitHub link with those who you are asking for help.

[Workaround line, please ignore]

 

Guest
This topic is now closed to further replies.
 Share
Go to topic listing

Announcements



×
×
  • Create New...

Important Information

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

  I accept