[
https://issues.jboss.org/browse/ARQ-921?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on ARQ-921:
-------------------------------
I thought about allowing the prefix to be customized in the engine configuration, as
follows:
{code:xml}
<engine>
<property name="environment">env</property>
</engine>
{code}
However, this seems like excessive configuration. I don't really think developers care
what the prefix is, as long as it's documented.
The only question is whether we should allow disabling (or enabling) the automatic
transfer of environment variables to the system property table. If so, we could do
something like:
{code:xml}
<engine>
<property name="useEnvironment">true</property>
</engine>
{code}
Make environment variables available for property replacement in
configuration
------------------------------------------------------------------------------
Key: ARQ-921
URL:
https://issues.jboss.org/browse/ARQ-921
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 1.0.0.Final
Reporter: Dan Allen
Copy all the environment variables to the base property "env" in the system
property table. Using the base property avoids conflicts with property names. This
strategy is typical in build systems.
For example, assume the following environment variable is defined:
{code}
JBOSS_HOME=/opt/jboss-as
{code}
This environment variable can be referenced from the configuration (arquillian.xml) as
follows:
{code}
${env.JBOSS_HOME}
{code}
A system property may be used to override an environment variable, as follows:
{code}
-Denv.JBOSS_HOME=/home/user/opt/jboss-as
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira