On Tue, May 16, 2017 at 12:31 PM, Cédric Champeau <cedric.champ...@gmail.com > wrote:
> > So far the only suitable workaround I can think of is an agent that would > rewrite `System.getenv` to call our internal APIs. I'll suggest that in our > next meeting (which is happening 30 mins from now). > Yes, given that you have control over your java processes, I think this is what you should do, at least medium-term. Longer-term, figure out some way to migrate to a strategy that does not involve accessing jdk internals.