Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Cannot run .\gradlew setupDecompWorkspace on 1.14.4


Diociae
 Share

Recommended Posts

For some reason, I cannot run .\gradlew setupDecompWorkspace and it always fails to build. I don't know the error, obviously. It has the build.gradle file in the folder, and everything I've read online says that it should work.

Here's the 'what went wrong' section of the powershell report

 

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'mod2'.
> Could not resolve all files for configuration ':_compileJava_1'.
   > Could not resolve java3d:vecmath:1.5.2.
     Required by:
         project :
      > Could not resolve java3d:vecmath:1.5.2.
         > Could not get resource 'https://libraries.minecraft.net/java3d/vecmath/1.5.2/vecmath-1.5.2.jar'.
            > Could not HEAD 'https://libraries.minecraft.net/java3d/vecmath/1.5.2/vecmath-1.5.2.jar'.
               > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   > Could not resolve com.mojang:patchy:1.1.
     Required by:
         project : > net.minecraft:client:1.14.4
      > Could not resolve com.mojang:patchy:1.1.
         > Could not get resource 'https://libraries.minecraft.net/com/mojang/patchy/1.1/patchy-1.1.jar'.
            > Could not HEAD 'https://libraries.minecraft.net/com/mojang/patchy/1.1/patchy-1.1.jar'.
               > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   > Could not resolve oshi-project:oshi-core:1.1.
     Required by:
         project : > net.minecraft:client:1.14.4
      > Could not resolve oshi-project:oshi-core:1.1.
         > Could not get resource 'https://libraries.minecraft.net/oshi-project/oshi-core/1.1/oshi-core-1.1.jar'.
            > Could not HEAD 'https://libraries.minecraft.net/oshi-project/oshi-core/1.1/oshi-core-1.1.jar'.
               > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   > Could not resolve com.ibm.icu:icu4j-core-mojang:51.2.
     Required by:
         project : > net.minecraft:client:1.14.4
      > Could not resolve com.ibm.icu:icu4j-core-mojang:51.2.
         > Could not get resource 'https://libraries.minecraft.net/com/ibm/icu/icu4j-core-mojang/51.2/icu4j-core-mojang-51.2.jar'.
            > Could not HEAD 'https://libraries.minecraft.net/com/ibm/icu/icu4j-core-mojang/51.2/icu4j-core-mojang-51.2.jar'.
               > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   > Could not resolve com.mojang:javabridge:1.0.22.
     Required by:
         project : > net.minecraft:client:1.14.4
      > Could not resolve com.mojang:javabridge:1.0.22.
         > Could not get resource 'https://libraries.minecraft.net/com/mojang/javabridge/1.0.22/javabridge-1.0.22.jar'.
            > Could not HEAD 'https://libraries.minecraft.net/com/mojang/javabridge/1.0.22/javabridge-1.0.22.jar'.
               > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   > Could not resolve com.mojang:brigadier:1.0.17.
     Required by:
         project : > net.minecraft:client:1.14.4
      > Could not resolve com.mojang:brigadier:1.0.17.
         > Could not get resource 'https://libraries.minecraft.net/com/mojang/brigadier/1.0.17/brigadier-1.0.17.jar'.
            > Could not HEAD 'https://libraries.minecraft.net/com/mojang/brigadier/1.0.17/brigadier-1.0.17.jar'.
               > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   > Could not resolve com.mojang:datafixerupper:2.0.24.
     Required by:
         project : > net.minecraft:client:1.14.4
      > Could not resolve com.mojang:datafixerupper:2.0.24.
         > Could not get resource 'https://libraries.minecraft.net/com/mojang/datafixerupper/2.0.24/datafixerupper-2.0.24.jar'.
            > Could not HEAD 'https://libraries.minecraft.net/com/mojang/datafixerupper/2.0.24/datafixerupper-2.0.24.jar'.
               > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   > Could not resolve com.mojang:authlib:1.5.25.
     Required by:
         project : > net.minecraft:client:1.14.4
      > Could not resolve com.mojang:authlib:1.5.25.
         > Could not get resource 'https://libraries.minecraft.net/com/mojang/authlib/1.5.25/authlib-1.5.25.jar'.
            > Could not HEAD 'https://libraries.minecraft.net/com/mojang/authlib/1.5.25/authlib-1.5.25.jar'.
               > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   > Could not resolve com.mojang:text2speech:1.11.3.
     Required by:
         project : > net.minecraft:client:1.14.4
      > Could not resolve com.mojang:text2speech:1.11.3.
         > Could not get resource 'https://libraries.minecraft.net/com/mojang/text2speech/1.11.3/text2speech-1.11.3.jar'.
            > Could not HEAD 'https://libraries.minecraft.net/com/mojang/text2speech/1.11.3/text2speech-1.11.3.jar'.
               > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 5.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/4.9/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 1m 11s

 

Link to comment
Share on other sites

18 minutes ago, diesieben07 said:

Correct.

I am asking what you mean. Am I not supposed to unpack the MDK into its own folder? If not, then where am I supposed to unpack it? I apologize for being.. Slow, but this is my first time in trying to do this. 

Link to comment
Share on other sites

1 hour ago, Exabyte314 said:

I'm using Eclipse for my modding, where would I put my build.gradle - inside the workspace folder or do i need to place it inside further folders?

You unpack the MDK to a folder of your choosing (it should be empty).

You import the build.gradle into your IDE.

 

Anything else is irrelevant, otherwise it would have been mentioned in the necessary steps.

Link to comment
Share on other sites

12 hours ago, diesieben07 said:

You unpack the MDK to a folder of your choosing (it should be empty).

You import the build.gradle into your IDE.

 

Anything else is irrelevant, otherwise it would have been mentioned in the necessary steps.

yes i read that before, where in the IDE is what i am asking.

Link to comment
Share on other sites

The extracted MDK folder is considered your mod workspace, you don't move anything out of it, just open Eclipse, Import, Import Existing Gradle Project, select your mod workspace (not your Eclipse workspace, which is more of a user settings folder than a workspace), click next, and Eclipse will scan the folder for Gradle project files, it should find the build.gradle provided by the MDK.

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]

 

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
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.

 Share



×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.