[SOLVED] ForgeGradle - Build failed with an exception

[Boofel]

This is the exception I get after I try any gradlew command.

Everything was working fine a few days ago pretty much perfectly so the only thing I can think of is it may be an internet issue that has arisen.

 

If you need any more information to help solve the issue, I'd be happy to provide.

 

G:\Boofel\Minecraft\1.7\TestMod>gradlew

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'TestMod'.
> Could not resolve all dependencies for configuration ':classpath'.
   > Could not resolve net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT.
     Required by:
         :TestMod:unspecified
      > Unable to load Maven meta-data from http://repo1.maven.org/maven2/net/mi
necraftforge/gradle/ForgeGradle/1.2-SNAPSHOT/maven-metadata.xml.
         > Could not GET 'http://repo1.maven.org/maven2/net/minecraftforge/gradl
e/ForgeGradle/1.2-SNAPSHOT/maven-metadata.xml'.
            > Invalid argument: connect
      > Unable to load Maven meta-data from http://files.minecraftforge.net/mave
n/net/minecraftforge/gradle/ForgeGradle/1.2-SNAPSHOT/maven-metadata.xml.
         > Could not GET 'http://files.minecraftforge.net/maven/net/minecraftfor
ge/gradle/ForgeGradle/1.2-SNAPSHOT/maven-metadata.xml'.
            > Invalid argument: connect
      > Unable to load Maven meta-data from https://oss.sonatype.org/content/rep
ositories/snapshots/net/minecraftforge/gradle/ForgeGradle/1.2-SNAPSHOT/maven-met
adata.xml.
         > Could not GET 'https://oss.sonatype.org/content/repositories/snapshot
s/net/minecraftforge/gradle/ForgeGradle/1.2-SNAPSHOT/maven-metadata.xml'.
            > Invalid argument: connect

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

BUILD FAILED

Total time: 3.453 secs

 

Thanks in advance,

Boofel

[Boofel]

No I did not change my build.gradle. This same thing happens when I use a freshly downloaded forge gradle.

[Boofel]

So, what should I do now?

[Eternaldoom]

What command args did you use?

[Boofel]

I've tried things like:

gradlew setupDecompWorkspace

gradlew tasks

gradlew eclipse

gradlew --refresh-dependencies

more I cant remember off the top of my head

 

Everything I did gave the same error.

[Boofel]

I just tried it again with a fresh download of the latest forge - same error.

It must be something on my end but I dont know what

[Eternaldoom]

Are you using some kind of beta software or anything that might be unsupported?

[Boofel]

Not that I can think of but I'm not sure. What could it be that's affecting it and I'll check

 

[Eternaldoom]

Beta OS

[Boofel]

No, my OS is a legit version of Windows 7 Home Premium 64 bit

[bbqd]

Maybe you have a 32x JDK? I don't know if that would change something, but it's the best I can think of.

[Boofel]

I do not have any 32bit Java installed

[Boofel]

If it helps, I tried going the URL's listed in the exception above and many of them say 404 not found.

Im not sure if that's normal or not.

[Brian_Entei]

Maybe try wiping all of your old gradle files including the main folder located in C:\Users\YOURUSERNAME\.gradle then downloading the recommended version of gradle from the minecraft forge file server?

[Boofel]

After wiping my .gradle folder, this is the error im getting.

 

G:\Boofel\Minecraft\1.7\TestMod>gradlew
Downloading https://services.gradle.org/distributions/gradle-2.0-bin.zip

Exception in thread "main" java.net.SocketException: Invalid argument: connect
        at java.net.DualStackPlainSocketImpl.connect0(Native Method)
        at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketI
mpl.java:79)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.ja
va:339)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocket
Impl.java:200)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java
:182)
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:579)
        at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618)
        at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:160
)
        at sun.net.NetworkClient.doConnect(NetworkClient.java:180)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
        at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
        at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:275)
        at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371)
        at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewH
ttpClient(AbstractDelegateHttpsURLConnection.java:191)
        at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne
ction.java:932)
        at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect
(AbstractDelegateHttpsURLConnection.java:177)
        at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon
nection.java:1300)
        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Http
sURLConnectionImpl.java:254)
        at org.gradle.wrapper.Download.downloadInternal(Download.java:56)
        at org.gradle.wrapper.Download.download(Download.java:42)
        at org.gradle.wrapper.Install$1.call(Install.java:57)
        at org.gradle.wrapper.Install$1.call(Install.java:44)
        at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAcc
essManager.java:65)
        at org.gradle.wrapper.Install.createDist(Install.java:44)
        at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:126)
        at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:56)

 

I've tried this on another computer on the same internet and it worked on there - Java is set up exactly the same on both PC's

[Boofel]

So, it looks like I've solved it and everything seems to be back to normal.

The problem was my network card drivers. The drivers that came on the disc with the network card seem to be faulty or incomplete, so as soon as I removed that driver and installed one from their website, everything worked after that.

 

Thanks for all the help to everyone who posted!

Boofel