[
https://issues.apache.org/jira/browse/TAMAYA-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508572#comment-16508572
]
ASF subversion and git services commented on TAMAYA-340:
--------------------------------------------------------
Commit 97c5630e5747ffeea2b7a60f1bb03577ee8ca449 in
incubator-tamaya-extensions's branch refs/heads/master from [~wlieurance]
[
https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=97c5630
]
TAMAYA-340 Environment properties vs PropertySourceChangeTest
On looking for the System property "java.home" in the Environment, we
are now also looking for "JAVA_HOME". The Environment variable is often
a symlink while the System property is often the resolution of that
symlink. That causes a surprising update event. Test both sides of the
surprise.
> Alternative property keys for environment variables
> ---------------------------------------------------
>
> Key: TAMAYA-340
> URL: https://issues.apache.org/jira/browse/TAMAYA-340
> Project: Tamaya
> Issue Type: New Feature
> Reporter: Harald Wellmann
> Assignee: Philipp Ottlinger
> Priority: Major
> Fix For: 0.4-incubating
>
>
> h3. Background
> Some operating systems (e.g. Windows) do not support dots in environment
> variable names.
> h3. Goals
> When looking up a config value for key {{foo.bar.blah}}, Tamaya should also
> try the fallback key {{FOO_BAR_BLAH}}.
> This is also part of the [Config JSR
> requirements|https://github.com/eclipse/ConfigJSR/blob/25edda2914155ac6b30f821f9ef13e92b7350a3a/spec/src/main/asciidoc/configsources.asciidoc],
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
