On Oct 6, 2008, at 3:32 PM, Victor Ott wrote:
Hello Hans, thanks for your fast reply. I understand the reasons which make a .exe wrapper like Launch4J necessary, and support that. Therefore I wanted to analize myself the Gradle Launch4J configuration, maybe try other settings, etc, but I couldn't find the Launch4J configuration file (something like "config.xml" mentioned under http://launch4j.sourceforge.net/docs.html ) neither in the source distribution, nor in Subversion repository.
I had been confused by this as well. This config.xml is one way to configure how launch4j _generates_ the gradle.exe at build time.
Wanting to switch to 0.4 Gralde *TODAY*, I finally hacked up a tiny .CMD script (I hate .BAT, and Win9x is obsolete), inpired by the Un*x script from the bin directory. It's small and stupid, but why do more than necessary? Here it is, maybe someone else could use it too:
I share your opinion on Win9x. After all, those niche users would be able to run Gradle via cygwin.
What is the advantage of cmd over bat? Unfortunately I guess it does not solve our main problem. If you call 'cmd /c gradle.exe' it returns 1 if the build fails. If you call 'cmd /c gradle.cmd' it returns 0 in case of a failing build, as far as I can tell. Therefore Teamcity and Bamboo would not recognize this build as failed.
On the other hand we can't leave things as they are. One approach might be to provide again a bat or cmd script and drop launch4j, and additionally focusing of providing Gradle plugins for Teamcity and Bamboo. Another approach would be to provide .exe and .cmd files.
- Hans -- Hans Dockter Gradle Project lead http://www.gradle.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
