> > But to ensure backward comp, file from store if exists must win. >> > > I would say if it's in the store, migrate it to the other configuration and > then remove it. The new file would always win. > > I still like commons-configuration as a way to source the information, > especially since you can pull values from JNDI and system properties that > makes it straight forward to overrides some configuration. > > I'm totally agree. If we use commons-configuration, maybe it would be good to remove plexus-registry
Emmanuel
