Steve Appling wrote:
Adam Murdoch wrote:
A better solution would be for the UI to not use the scripts.
Adam
We originally were planning to not use them, but if we didn't, we
needed to reproduce the logic that is now in the scripts inside gradle.
Or move the bits you need into Java. I suspect you only need to worry
about JAVA_HOME, which we know already, and GRADLE_OPTS.
We're going to need to do this for forking Gradle builds.
We also had our own internal use case of a custom build script that
provides init scripts and other options. If we were going to allow
the ability to specify a custom script to run, it seemed best to
normally fork by using the built in script.
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?
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
