Isn't it easier just to have a script that copy the 2 sets of configuration directories on top of each other. Depending on the order, it would be the overriding properties?
Regards, Edward Yakop On 2/23/07, David Leangen <[EMAIL PROTECTED]> wrote: > > I was having a discussion with Boon Ping recently regarding optional > properties. > > The problem is this: > > I want to have default properties for a bundle sitting in a > properties file that is committed to the svn repository (as is done > presently). > > In addition, I want each user/developer to have the possibility of > using an optional properties file if they want to change any of the > default values. Such optional properties file would only be saved > locally on that developer's machine so it would not "interfere" with > anybody else. > > Upon startup, pax-ConfigAdmin would first check for the existence of > such optional file. If it exists, these would override the props of > the default file. Otherwise, it would use the props in the default > file (if any). > > > I think this is a reasonable use case, but Boon Ping does not. > > > wdyat... could something like this be a candidate for pax-ConfigAdmin? > > If so, can we go ahead and make this change? > > > Cheers, > Dave > > > > _______________________________________________ > general mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/general > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
