[cp-patches] RFC: patch to make gconf as default preference backend

2006-07-01 Thread Mario Torre
This patch makes gconf the default backend. The patch works adding a new configure option that let the user to specify a default implementation (like FileBased or GConfBased ones). If the user does not provides this option, than the preference backend is FileBased (current default). Only if the

RE: [cp-patches] RFC: patch to make gconf as default preference backend

2006-07-02 Thread Jeroen Frijters
Mario Torre wrote: > This patch makes gconf the default backend. > > The patch works adding a new configure option that let the user to > specify a default implementation (like FileBased or GConfBased ones). > > If the user does not provides this option, than the preference backend > is FileBased

RE: [cp-patches] RFC: patch to make gconf as default preference backend

2006-07-02 Thread Mario Torre
Il giorno dom, 02/07/2006 alle 10.15 +0200, Jeroen Frijters ha scritto: > We're trying to move away from gnu.classpath.Configuration, so this is > not ideal. Ok, so I need to redo it anyway... but > Also, why are you doing this: > > +System.setProperty("java.util.prefs.PreferencesFactor

[cp-patches] RFC: patch to make gconf as default preference backend, second try

2006-07-02 Thread Mario Torre
This patch makes the gconf backend the default. The configure part of the patch is the same as the one discussed early, but now the backend name is stored under META-INF and loaded at runtime using ServiceFactory. A new file is introduced in the META-INF directory that is used to build the actual