[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13599: --------------------------------------------- Here is a pullrequest (https://github.com/jbosstools/jbosstools-central/pull/75) which incorporates majority of the concerns raised in here. basic usage/sytax is the same as described by Snjezana. But to answer the concerns which seemed to have drowned: 1) There is no longer any need to have this be a maven only test thus made it so can test with built-in properties PLUS I just set the system properties from within the test since the values does not need to point to anything for the tests. 2) "I can also see that DMR would throw an exception if something wrong is resolved - is that the behavior we need" - I think it makes sense, but we need to add code to handle this error case so the user can know what is going on. (simple to do I think, just a todo) 3) "DMR actually does seem to handle multiple values", yes - ${foo,bar} now works. 4) "the default replacement seem to treat file seperators and path seperators as a special case and return different results based on OS values" This just means that {:} and {/} can be used to specify portal file locations (i.e. {/}file{/}path becomes /file/path on Linux, \file\path on Windows. Not something we need for this but I kept it in for consistency. 4) "But why we want to add a direct dependency on this library for this simple functionality I do not grok." - no dependency on this anymore. 5) "We should just copy the code and adjust it for what we need (looks like no changes needed except a few for the above issues) - note, this is tough LGPL so need to adjust for that." -- this is now done, put in internal package since its not to be a public API for now and put in .xpl package and with no dependencies to EPL to oblige to LGPL/EPL. If you could give this a try it would be great - I'll try add the error handling; but if you have time to do it that would be great too :) -- 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