Hi Jonathan, Bazel is a cathedral when Gradle is a bazaar, Bazel uses a controlled subset of Python as build language, and a strictly defined API that do not let you extend Bazel in an arbitrary way.
Those two approaches, a strict DSL or a general purpose languages retargeted to be used as a DSL have both there advantages and inconveniences, but i'm sure that everybody will agree that for the extensions/plugins migration, it's better to have a cleanly sandboxed environment. Rémi ----- Mail original ----- > De: "Jonathan Bluett-Duncan" <jbluettdun...@gmail.com> > À: "Cédric Champeau" <cedric.champ...@gmail.com> > Cc: "core-libs-dev" <core-libs-dev@openjdk.java.net> > Envoyé: Mardi 16 Mai 2017 22:03:49 > Objet: Re: Getting a live view of environment variables (Gradle and JDK 9) > Hi Cédric, > > I don't know if it's been considered, but has anyone from the Gradle team > asked the Bazel team about this problem? > > They may have useful insight about this problem with `System.getenv`, > considering that Bazel is apparently very fast and (partially) written in > Java. > > I hope this helps. > > Best regards, > Jonathan
