Hi Anatole,
first, let us exclude the discussion on stages. In generell I think this
a usefull and needed feature.
But why do we need to read the properties in a specific order?
Futhermore does it help if there a many differente jars. How do we
handle this?
And just as a question? Why is the ordinal (priority) not enough?
Just questions.
Bye,
Oliver
Am 03.03.15 um 09:19 schrieb Anatole Tresch:
Dear all
I am currently updating the site and documentation, to approach further a
first release. I am not happy with the current default config setup in
Core. I would propose to provide the following setup (PropertySources and
providers), from weakest to strongest:
1. Read *environment properties* and add them prefixed with "env."
2. Read all files found in *META-INF/cfg/defaults.properties*
3. Read all files found in* META-INF/cfg/${stage}/defaults.properties*
4. Read all files found in *META-INF/cfg/config.properties*
5. Read all files found in *META-INF/cfg/${stage}/config.properties*
6. Read current *system properties*.
Given that we have simple and enough powerful variant, which can be
implemented very easily.
If no stage is set, the stage specific parts are not read. The stage can be
set by applying a
environment property or (overriding) system property, named
*tamaya.stage*
I expect the Core and API module together not exceed 100k in Java 8 ;)
WDYT?
Anatole
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E [email protected]
S oliver.b.fischer
J [email protected]
X http://xing.to/obf
