Wow I really feel with you my dear Java developers.

Since I am working on a Custom Launcher for devCraft I now know how bad gradle is.

You came in the write time, checkout Android Studio 3.0 with the latest Gradle plugin, it is faster but ya never trust @gradle

android studio for a non android project? Also the devCraft Launcher is the only Java Project I am working at, so android studio is an overkill

@Torbuntu you are one of the few lucky ones. For me it works good for an hour then it just starts fucking around and takes 30 minutes per build, I must close android studio, all openJDK processes (usually two with 1.8GB memory usage per process) then it will be back to normal

@Torbuntu I'm writing a new project still haven't completed it :(
and I have SSD + 16GB RAM yet it fucks up everyone once and a while

@Torbuntu Windows :\
it does the same on macOS though, at work, but the thing at work I have an 8GB RAM and 5400RPM 1TB HDD :\

Well the launcher takes about 2:30 to build but that's quite a long time for such a small project

Devcraft? Sounds cool, got a link for it?

@coolq devcraft.ml - the site is outdated but the server is new, it was originally hosted by @ParkCity on his laptop but was moved to my server recently

@dsteiner pretty nifty!

Try a different gradle version I've solved some of these problems in the past by upgrading or downgrading. Use sdkman.io or the gradle wrapper.

@Torbuntu I'm gonna try it on a Linux machine and see if I face similar issue, hoping that I don't

@Torbuntu I sure will, lets hope I don't face issues :\