Cannot create dev environment due to maven issue

[ThePwnd]

####What type of issue is this? (e.g. bug, feature request)
Crash

####Issue Description:
The game crashes to desktop after loading a world.

####Steps to Reproduce: (if applicable)
Create a new Minecraft instance, install Forge, create a new world.

####System info: (only needed for bug reports)

Java version:
According to my Minecraft log: 1.8.0_131

Minecraft version:
1.7.10

Deeper Caves version:
1.0.0

Other mods (if any):
None

Crash report:
https://pastebin.com/e7Sx7Yh2
https://pastebin.com/E9nEXPBt (Contains an excerpt from the log file with more errors; the whole file was too big for pastebin, and couldn't be processed by GitHub)

That's really all there is to it... I'm really confused because I have no other mods installed and I can't even get into the world... I've looked at the CurseForge page, the MinecraftForum page, and the GitHub issues, and I appear to be the only person experiencing this issue... I must be missing something very basic, but I can't figure out what it is. I tried the latest version of Forge for 1.7.10 (build 1614), and also the version you listed in your notes (build 1291), but that didn't fix the problem either.

[ThePwnd]

Alright, so I followed the stack trace in my log file to the getNewestVersionID() method, found on line 17 of this file - https://github.com/Valiec/DeeperCaves/blob/master/src/main/java/com/kpabr/DeeperCaves/DeeperVersionChecker.java - and it looks like what's happening is that the URL listed in the code, www.kpabr.com, is no longer operational, which causes the code to throw an exception and ultimately crash the game.

Should be a simple fix. I would love to do it myself, but, oh so wonderfully, I can't setup an eclipse environment with Forge on 1.7.10 anymore, because the Maven repo only accepts https requests, but the gradle wrapper for 1.7.10 sends http requests.

I'm trying to find a workaround.....

[BaccarWozat]

I've spoken with Valiec and he intends to bring back the website as a stopgap measure so the mod can continue for now, until he has the chance to find out why the mod crashes just because the website is down, and release a fix.

[BaccarWozat]

How to switch to Gradle wrapper 4.4.1

[ThePwnd]

Ah nice! Thanks for the tutorial. Where did you find that, btw? I had actually reached out to another mod author about the issue, and he suggested the same thing, just without the specifics. I couldn't figure out how to tell Forge to use that version of Gradle, but I had just added another maven URL to the build.gradle file like:

maven {
	url = "https://repo1.maven.org/maven2/"
}

And that got around the error too. Though it may have been more of a hack I worry. >.>

At any rate, from what I can see it looks like the issue is that the getNewestVersionID() method is checking for an IOException, but the exception being thrown is different, so it gets missed by that method, and caught by a different method in Forge somewhere, and you get the weird crash report that I got. I'm not sure what type of error it should be checking for, but I wrote a quick and dirty fix that just returns the newestVersionStr no matter what. That worked. There's already logic in place in the onUpdateMessage() method that doesn't blow up if the string is garbage.

It's certainly not a long term solution, but if Valiec wants, I can push my code, or put it in my own repo for him to look at.

[Valiec]

Is this still broken? I don't recall at this point if I patched this, but I don't have build issues myself.

[Valiec]

The update checker is deactivated in new versions, so it's not an issue, but the dev env thing I need to check.