Konstantin Kolinko <> changed:

           What    |Removed                     |Added
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #2 from Konstantin Kolinko <> ---
I am OK with the feature, but I am -1 on the approach implemented in this patch

1). Consider the following properties:

If you have value="${first}${second}" my expectation is that result of
substitution will be value="${bar}". Your algorithm will yield value="baz".

I think the replacement loop should be inside of
looking for replacements in the value of a property.

Instead of looping over resulting value.

2). It would be better to have some hard limit on recursion depth. E.g. 20.
(Not a showstopper requirement, but a "nice to have" one).

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to