This is a Gradle project of a .exe launcher for Gradle. It has no build time dependencies on Gradle, and at runtime it uses JAVA_HOME and GRADLE_HOME and dynamic class loading to start Gradle. Of course it fixes the problem with a scirpt either closing console on error or never returning anything other than 0. The application should run Gradle without a need to be rebuilt, as long as Gradle's entry class is org.gradle.ToolsMain.

The only dependency (build time) of this project is Launch4J - the version specific to users operating system is downloaded at build time. This behaviour can be overridden by specifying either LAUNCH4J_HOME environment variable, or launch4j.dir system property. The project's output is Windows specific, but nevertheless it should be building properly on other platforms such as Linux and MacOS.

I'm also attaching the built .exe file - if you have JAVA_HOME and GRADLE_HOME set on your machine, you can download it anywhere on your hard drive and be able to run it.

Sorry it took me so long to post this solution - I had a lot of stuff going on for the past week, but I guess it's better later than never

Cheers,
Adam

Thank you so much, Adam. This finally solves a very annoying problem. For example the windows build on our CI server is always successful even if it fails.

I'm looking forward to releasing 0.1.5 with your launcher stuff.

I'm not happy about this but I have to postpone the implementation. The problem are our gradlew wrapper scripts which do call more than one Java application. I gonna comment more on this later.

Finally this is implemented. Thanks a lot Adam, for laying out the base for this.