Hi there,
I'm a developer at Apache Commons and Charles contacted us about its
issue with ExtendedProperties. ExtendedProperties is no longer evolving
in Commons Collections since it forked to spawn the Commons
Configuration project some years ago. Many features have been
implemented in Commons Configuration like automatic reloading, changes
notifications, custom interpolation, and more.
Do you think it would be possible to support Commons Configuration in
Velocity and deprecate the use of ExtendedProperties ? I may dedicate
some time to provide a patch if this change seems acceptable. The added
flexibility of Commons Configuration has a cost though, it would add 2
dependencies to Velocity (Commons Configuration and Commons Logging).
What do you think ?
Emmanuel Bourg
Will Glass-Husain a écrit :
Hi,
Thanks for your enthusiasm and interest. We're all Velocity developers
here...
I've never played myself with custom implementations of Extended Properties,
but that seems like a reasonable approach.
Will this patch also support system properties? (or are they already
supported). That seems the most useful.
Really, I'd like to see this become part of ExtendedProperties. Makes more
sense to have that kind of substitution occur at the level. One idea would
be to submit your patch to that project, then use the modified version with
Velocity. If you do this, let us know how it is working out. You might even
want to post sample code on our Wiki.
If you still feel that belongs part of Velocity core, then do continue to
speak up and advocate for it being included in the Velocity code directly.
Best, WILL
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
