Dennis Reedy wrote:
For configuration, use the Jini configuration approach or can we move forward
with adopting the Groovy configuration provider?
I myself never warmed up to the Jini configuration system and feel the
communities I follow want lightweight approaches with low learning
curves. I haven't used the Groovy configuration yet but I think it's
worth a try.
I have submitted the GroovyConfiguration provider to the jira issue, it would
need to be added to the project. The other option is to include the Rio
artifact that provides this support.
I'll add it in the near future, I'd prefer we use a River artifact.
