Re: [gradle-dev] GUI

[Adam Murdoch]

John Murph wrote:
On Wed, Sep 16, 2009 at 5:19 PM, Adam Murdoch <a...@rubygrapefruit.net 
<mailto:a...@rubygrapefruit.net>> wrote:


    Needing a custom launcher script sounds like a problem to me. What
    goes in the custom script and the init script that couldn't go in
    the build file?


Steve was not being very precise.  Our custom script sets the 
following things:

    * JAVA_HOME
    * GRADLE_HOME
    * --project-dir command line option

It's done this way so that everyone doesn't need to adjust machine 
wide settings for Java and Gradle when building the project (java and 
gradle are in our version control so that we all get/share the same 
versions).  The project dir is set in the script so that we don't need 
to type it every time we run Gradle.


It seems like you only need a custom script to launch the GUI itself. 
When the GUI forks Gradle, it should use the Java home and Gradle home 
it was launched with. It should also honour the --project-dir 
command-line option, plus a bunch of other command-line options, such as 
--no-search-upwards, --gradle-user-home, possibly -d, -i, -s, -S.

Then, there's no reason for the GUI to use the custom script to fork 
Gradle. It can fork Gradle however it likes.


Adam