using Velocity to externalize configuration properties ?

[Tom Zeller]

> Seems potentially heavyweight but maybe. What would be the inputs to the
> template to perform the replacement? A properties file?

Yes, Velocity seems heavyweight, but I think the idea is to be
consistent with the templates.

Input would be one or more properties files, yes.

>>I believe the idea is to use Velocity similar to the v2
>>PropertyReplacement ResourceFilter. The Spring
>>PropertyPlaceholderConfigurer also seems relevant.
>
> I've never looked at the code, what does the current filter use?

I think it simply does String.replace(...) using a pattern, nothing fancy.