There's some initial discussion on this @ http://issues.gradle.org/browse/GRADLE-1240
I can't see a clear way forward here so am putting it up for discussion. There's a larger issue here about configuring the daemon in general, but I think we should focus on memory args and then move on to other properties. I can definitely see that people will want very different memory configurations for the daemon and the “client”. However, when running without the daemon you are probably going to want what memory configuration you would normally want for the daemon for the client. That is, I want a memory configuration for Gradle when it runs a build no matter how it does it. There's a problem here though in that we don't know if we are using the daemon until the JVM has started and then it is too late. I am not sure that we need to make the JVM that just talks to the daemon very configurable. We might be able to detect that the JVM we are starting isn't going to be doing any building and use a preconfigured set of options for the JVM, and just use the GRADLE_OPTS for the daemon jvm or if the JVM is going to be doing the building then also use GRADLE_OPTS. It seems like this would come down to sniffing the args in the launching shell scripts though which seems a bit nasty. Another option along these lines is to have different shell scripts for building with or without the daemon which would make this a bit easier. I actually quite like this idea but need to think about it a bit more. I might move on to the stdin problem while we discuss this issue. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
