Jump to content

[1.15.2] Gradle Build Fail


ElerosVecchio

Recommended Posts

I am trying to setup modding for 1.15.2 using Eclipse. Whenever I try to use the gradlew commands, it gives me a Build Fail error. Attached to this is a screenshot I got of it. The window doesn't stay open long enough for me to copy the text, so this was all I could get.

The commands I have tried:

  • gradlew setupDecompWorkspace
  • gradlew genEclipseRuns
  • gradlew eclipse
  • gradlew --refresh-dependencies
  • gradlew clean

All of these give the same error.

The error says "Could not resolve all artifacts for configuration ':classpath'."

stupidgradle.png.2d37fddafdaa57ebea9bd48d05310420.png

Link to comment
Share on other sites

setupDecompWorkspace does not exist anymore, for eclipse it's eclipse and genEclipseRuns.

I believe running it adding --stacktrace will provide more information that could help find the issue.

 

*edit: Post logs as text, if your window doesn't stay open, that's the first issue to resolve. What OS?

Edited by Ugdhar
Link to comment
Share on other sites

2 minutes ago, Ugdhar said:

setupDecompWorkspace does not exist anymore, for eclipse it's eclipse and genEclipseRuns.

I believe running it adding --stacktrace will provide more information that could help find the issue.

 

*edit: Post logs as text, if your window doesn't stay open, that's the first issue to resolve. What OS?

 

I did use genEclipseRuns. I tried stacktrace and it still wont stay open. I am using Windows 10 Pro.

Link to comment
Share on other sites

Ok, then open the folder your mod project is in, hold shift and right-click in a blank spot, and you should have a menu with an open to open powershell window here. Do that, then run ./gradlew eclipse

 

*edit: might want --debug instead of --stacktrace, it looks like it gives more info. I've never really had any issues getting a workspace setup, so I'm just thinking of how I'd try to solve it if it were me.

Edited by Ugdhar
Link to comment
Share on other sites

1 minute ago, Ugdhar said:

Ok, then open the folder your mod project is in, hold shift and right-click in a blank spot, and you should have a menu with an open to open powershell window here. Do that, then run ./gradlew eclipse

 

I was actually able to get it to stay open using call and pause commands. Anyways here is the pastebin: https://pastebin.com/4Jy0rR4e

Link to comment
Share on other sites

2 minutes ago, ElerosVecchio said:

 

I was actually able to get it to stay open using call and pause commands. Anyways here is the pastebin: https://pastebin.com/4Jy0rR4e

Ah ok, so you're running your gradle commands from a batch file.

Anhyhow, I'm not sure what's going on there to be honest, looks like some sort of SSL error trying to get https://files.minecraftforge.net/maven/net/minecraftforge/gradle/ForgeGradle/maven-metadata.xml

Quote

Caused by: org.gradle.internal.resource.transport.http.HttpRequestException: Could not GET 'https://files.minecraftforge.net/maven/net/minecraftforge/gradle/ForgeGradle/maven-metadata.xml'.

...

Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

 

Can you go to that link manually in a browser?

Link to comment
Share on other sites

1 minute ago, Ugdhar said:

Ah ok, so you're running your gradle commands from a batch file.

Anhyhow, I'm not sure what's going on there to be honest, looks like some sort of SSL error trying to get https://files.minecraftforge.net/maven/net/minecraftforge/gradle/ForgeGradle/maven-metadata.xml

 

Can you go to that link manually in a browser?

 

Yes I can.

Link to comment
Share on other sites

2 minutes ago, ElerosVecchio said:

 

Yes I can.

Hmm. Which version of Java are you using? From the commandline in your project folder (batch files are good for some stuff, but definitely not for this situation :) ) run java -version

Doesn't matter what versions are installed, it depends on the command to tell which versions is actually being used.

 

*edit: Googling has some people getting this error with really old java versions. I'd say make sure you have the latest Java 8 JDK.

Edited by Ugdhar
Link to comment
Share on other sites

1 minute ago, Ugdhar said:

Hmm. Which version of Java are you using? From the commandline in your project folder (batch files are good for some stuff, but definitely not for this situation :) ) run java -version

Doesn't matter what versions are installed, it depends on the command to tell which versions is actually being used.

 

java version "1.8.0_241"
Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.241-b07, mixed mode)

Link to comment
Share on other sites

1 minute ago, ElerosVecchio said:

 

java version "1.8.0_241"
Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.241-b07, mixed mode)

Well then. I guess I'm at a loss, the only thing I can think of at this point is reinstalling the JDK fresh, but I truly don't even know if that is really the issue. Sorry :( Hopefully someone else will see this and know what it's all about!

Link to comment
Share on other sites

1 minute ago, Ugdhar said:

Well then. I guess I'm at a loss, the only thing I can think of at this point is reinstalling the JDK fresh, but I truly don't even know if that is really the issue. Sorry :( Hopefully someone else will see this and know what it's all about!

 

Thanks for the replies though. I tried installing the JDK for Java 14 but I couldn't find the jre and I tried getting JDK 8 but it was locked unless I signed up for a subscription.

Link to comment
Share on other sites

8 minutes ago, ElerosVecchio said:

I tried installing the JDK for Java 14 but I couldn't find the jre

Use Java 8, there's a library or something used by forge that requires it. Also, you don't need a JRE if you download a JDK, it comes with it.

The Oracle account you need to download Java 8 is free, but if you don't want one you could try OpenJDK, lots of people on here are using it just fine: https://adoptopenjdk.net/

Link to comment
Share on other sites

7 hours ago, Ugdhar said:

Use Java 8, there's a library or something used by forge that requires it. Also, you don't need a JRE if you download a JDK, it comes with it.

The Oracle account you need to download Java 8 is free, but if you don't want one you could try OpenJDK, lots of people on here are using it just fine: https://adoptopenjdk.net/

 

I was able to get the most recent OpenJDK 8, but I am still getting the same error (but it did take more time).

Edited by ElerosVecchio
Link to comment
Share on other sites

The issue is that whatever JDK you're using does not have LetsEncrypt's root certificate.

Be sure you are using jdk-8.0.242.08-hotspot or newer, as that is garenteed {I use it} to have LetsEncrypt AND AWS's certs which are needed for Forge's and Mojang's servers to work.

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

13 minutes ago, LexManos said:

The issue is that whatever JDK you're using does not have LetsEncrypt's root certificate.

Be sure you are using jdk-8.0.242.08-hotspot or newer, as that is garenteed {I use it} to have LetsEncrypt AND AWS's certs which are needed for Forge's and Mojang's servers to work.

 

That is the version of Java I am running

Link to comment
Share on other sites

8 hours ago, ElerosVecchio said:

java version "1.8.0_241"

24 minutes ago, LexManos said:

Be sure you are using jdk-8.0.242.08-hotspot or newer

Close but not the same.

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

I'm running the same version and I don't have the issue.

Try a clean reinstall of Java, force it to reset the cert store

 

Edit: Listen to Lex before you listen to me

Edited by DaemonUmbra

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

4 minutes ago, LexManos said:

Then you would not be getting this error.

Verify that is the actual version gradle is finding. 

Run:

 


echo %JAVA_HOME%

gradlew -version

 

 

That's why. Its using jdk 1.8.0_77, but I'm not sure why because I don't have that jdk.

Edited by ElerosVecchio
Link to comment
Share on other sites

See... this is why we don't like people when they argue with us.

We KNOW that our solution will fix the issue, that's why you came to us.

Arguing that you did what we said and still getting the issues is just lieing to us.

  • Like 1

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

4 minutes ago, LexManos said:

See... this is why we don't like people when they argue with us.

We KNOW that our solution will fix the issue, that's why you came to us.

Arguing that you did what we said and still getting the issues is just lieing to us.

 

I fixed it. I was installing it, but I was updating the system wide Path and JAVA_HOME variables, not the user ones. Now that I've changed those, it now works.

Thank you for helping me fix this.

Link to comment
Share on other sites

To my knowledge you shouldn't even have user level ones unless you're a non-admin without access to the system level

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