I have what seems to me to be a similar issue. I'm using properties defined in .properties resource as follow:
PROFILE = unit-test
LOG_PATH = /var/log/$
{PROFILE}
MAIN_LOG_PATH = $
{LOG_PATH}/server
MONITOR_LOG_PATH = ${LOG_PATH}
/monitor
This way properties MAIN_LOG_PATH and MONITOR_LOG_PATH are not resolved. If I reduce the nesting level (by inlining either PROFILE or LOG_PATH properties) it works pretty fine.
I couldn't find any documented restriction on nesting levels - quite the contrary, documentation reinforces the idea of unrestricted nesting variables.
I'm using version 1.0.13
[]s
Heleno
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
I have what seems to me to be a similar issue. I'm using properties defined in .properties resource as follow:
PROFILE = unit-test
{PROFILE}LOG_PATH = /var/log/$
MAIN_LOG_PATH = $
{LOG_PATH}/serverMONITOR_LOG_PATH = ${LOG_PATH}
/monitor
This way properties MAIN_LOG_PATH and MONITOR_LOG_PATH are not resolved. If I reduce the nesting level (by inlining either PROFILE or LOG_PATH properties) it works pretty fine.
I couldn't find any documented restriction on nesting levels - quite the contrary, documentation reinforces the idea of unrestricted nesting variables.
I'm using version 1.0.13
[]s
Heleno