By default the properties component will only resolve properties from properties files.
But sometimes you may want to be able to set a JVM system property with either override or is used as fallback in case of a key. Such as if a key is missing it can fallback to a JVM key. Or a JVM key can override an existing key in the properties file.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|66d 7h 50m||1||Ashwin Karpe||09/Aug/10 23:02|
|24d 16h 12m||1||Ashwin Karpe||03/Sep/10 15:15|
|232d 19h 42m||1||Claus Ibsen||24/Apr/11 10:57|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Project Import||Sat Nov 27 00:14:50 EST 2010 [ 1290834890113 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
[ Hi Claus,
Instead of an override or fallback, I was wondering whether we should introduce a "system:...". We already support "file:...", "ref:..." and use classpath search as a default.
Can you let me know what you think...?
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Field||Original Value||New Value|
|Assignee||Ashwin Karpe [ akarpe ]|