On 17.05.2017 00:53, Kirk Pepperdine wrote:
println System.getenv('MY_VAR')
doesn't print "foo" after doing:
MY_VAR=foo gradle printVar
I disagree, this would be totally expected behavior. The daemon and this
process would run in different shells and I am unaware of any daemon process
that auto-magically reconfigures it’s self to adapt to any other arbitrary
shell’s changed environment variables. In fact, IMHO, this seems like a
fundamentally flawed way for the deamon process to behave. I believe the client
communicating with the deamon that should be providing information to the
daemon.
It might open a grab bag of exciting behavior depending on what, if any,
filtering is done on the type and content of environment variables being
set.
The $PATH to /tmp/.dr0pp3r/.h3ll/ is paved with good intentions.
cheers,
dalibor topic
--
<http://www.oracle.com> Dalibor Topic | Principal Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961>
ORACLE Deutschland B.V. & Co. KG | Kühnehöfe 5 | 22761 Hamburg
ORACLE Deutschland B.V. & Co. KG
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRA 95603
Komplementärin: ORACLE Deutschland Verwaltung B.V.
Hertogswetering 163/167, 3543 AS Utrecht, Niederlande
Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697
Geschäftsführer: Alexander van der Ven, Jan Schultheiss, Val Maher
<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment
