mx env file processing
Tom Rodriguez
tom.rodriguez at oracle.com
Tue May 17 23:51:10 UTC 2016
> On May 17, 2016, at 3:20 PM, Stefan Marr <java at stefan-marr.de> wrote:
>
> Hi Tom:
>
>> On 17 May 2016, at 22:40, Tom Rodriguez <tom.rodriguez at oracle.com> wrote:
>>
>> I made a minor change to the processing of env files that shouldn’t impact most people. Previously mx.mx/env happened to function as a global env file that was read by all suites but this was really an unintended behavior. There is now an optional per user ~/.mx/env file that can hold global options and mx.mx/env is only read when it is the primary suite. https://ol-bitbucket.us.oracle.com/projects/G/repos/mx/browse/README.md <https://ol-bitbucket.us.oracle.com/projects/G/repos/mx/browse/README.md> explains the env file loading process in more detail.
>
> I assume you refer to this https://github.com/graalvm/mx/blob/master/README.md#mx-environment-variable-processing
Yes, sorry for sending out the wrong link. Forgot that wasn’t externally visible.
tom
>
> Best regards
> Stefan
>
>
>
> --
> Stefan Marr
> Johannes Kepler Universität Linz
> http://stefan-marr.de/research/
>
>
>
More information about the graal-dev
mailing list