[
https://issues.apache.org/jira/browse/ARIES-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved ARIES-1264.
------------------------------------
Resolution: Duplicate
Assignee: Guillaume Nodet (was: Jean-Baptiste Onofré)
Fix Version/s: ARIES-1311
> blueprint-ext could support ${env:USER} notation (for OS env variables)
> -----------------------------------------------------------------------
>
> Key: ARIES-1264
> URL: https://issues.apache.org/jira/browse/ARIES-1264
> Project: Aries
> Issue Type: Improvement
> Components: Blueprint
> Reporter: Jean-Baptiste Onofré
> Assignee: Guillaume Nodet
> Fix For: ARIES-1311
>
>
> In a blueprint descriptor, it's possible to use blueprint-ext to use Java
> System variable (the ones passed as argument using -Duser=$USER) and used
> with something like:
> {code}
> <ext:property-placeholder placeholder-prefix="$[" placeholder-suffix="]"/>
> ...
> <bean ...><property name="user" value="$[user]"/></bean>
> {code}
> In the org.apache.aries.blueprint.ext.PropertyPlaceholder, we do:
> {code}
> v = System.getProperty(val);
> {code}
> Additionnaly, it would be great to do System.getenv() to access the OS env
> variables, and so being able to do:
> {code}
> <ext:property-placeholder placeholder-prefix="$[" placeholder-suffix="]"/>
> ...
> <bean ...><property name="user" value="$[USER]"/></bean>
> {code}
> where USER has been set with something like this, for instance:
> {code}
> export USER=my
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
