Hi, On Tue, 2004-10-19 at 23:02, Bryce McKinlay wrote: > Mark Wielaard wrote: > > >If you remove this could you add a little note to VM Integration Guide > >doc/vmintegration.texinfo about the importance of setting up the system > >property gnu.classpath.home.url and how it is used by Security, > >LogManager and InitialContext to find default configuration files. > > > > Is there a reason to use a non-standard system property here? whats > wrong with java.home?
Maybe we can use something like "java.home" if it has a good standard definition. Since we have separated the implementation of the core class libraries in GNU Classpath from the different runtimes using it and you can basically install different combinations together, which might share the same GNU Classpath glibj installation (that is how I am using it with different runtimes). So I am not sure if using something like "java.home" actually makes sense. Also we wanted to make the gnu.classpath.home.url property more generic by allowing any valid URL so that we can access resources anywhere they are actually installed (which might not be on the file system). But I am not too attached to the current implementation. And the gnu.classpath.home.url property is currently only used for Security, LogManager and the InitialContext properties. So it shouldn't be hard to rewrite it to something else if you care. Cheers, Mark
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
