Page 1 of 1

Accessing editor variables from ant

Posted: Fri May 11, 2018 6:28 pm
by dcramer
Hi there,

I know that I can pass in editor variables from a parameter in my transformation scenario. E.g. I can create a parameter foo and pass in

Code: Select all

${oxygenInstallDir}
In my Ant file, I can also access Custom Editor Variables using env. E.g.

Code: Select all

${env.MY_CUSTOM_EDITOR_VAR}
Is there a way I can access non-custom editor variables without passing them in or assigning them to a custom editor variable?

I'm imaging being able to do something like

Code: Select all

<property name="oxygen-install-dir" value="${env.OXY.oxygenInstallDir}"/>
to find the install dir without any extra setup from the user.

Thanks,
David

Re: Accessing editor variables from ant

Posted: Mon May 14, 2018 9:41 am
by Radu
Hi David,

ANT transformations are started as standalone Java processes, so whatever is passed by the Oxygen process either as a parameter or as an environmental variable can be accessed in the child ANT process. Whatever is not passed by the parent Oxygen process cannot be accessed by the child process.

Regards,
Radu