Hi, > On Oct 12, 2017, at 2:54 PM, Mario Torre <neugens.limasoftw...@gmail.com> > wrote: > > 2017-10-12 11:58 GMT+02:00 Cédric Champeau <cedric.champ...@gmail.com>: > >> 1. an API in 18.3 which would let us refresh the environment variables, >> even if inherently unsafe (we can take the risk, if the Javadocs explains >> that if you're really unlucky calling such a method could kill your VM). > > Being a public API we would expose everyone to this risk, and the API > should be supported on all platforms maybe forever. I know other > people have different opinion here, but this seems to be high risk, > high impact to be worth.
As I have stated in post postings, this is behavior is unexpected and IMHO shouldn’t be supported. > >> 2. we change the way Gradle works and force explicit declaration of all >> environment variables a user script can use. Then, we would only spawn a >> new VM if the current daemon environment variables do not match those >> required found by the client. This describes a more appropriate behavior. Kind regards, Kirk Pepperdine
