-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi.
> I think people are missing Nicolas' point here. The class LogManager > is broken, because it is looking in the wrong place for the properties > file. > > Does anyone know what the correct behavior is supposed to be? A certain Jay-too-es-ee implementation loads it's logger configuration property file directly from the filesystem (at least it is stored there). I think this is what is intended to be emulated here. Due to certain packaging problems this would not work anyway on my distribution but this is a separate issue. A real problem is that our logging.properties file lives in java/util/logging inside the glibj.zip or more correctly: it is part of our system class path (remember that zipping the class library is an optional step) and the code is simply not correct. Maybe that is the reason for nicolas' initial problem. I file a bug for this. Thanks nicolas ;) cu Robert -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCjRfvG9cfwmwwEtoRAirNAJ9Zq1uff4DgTvt+Izu042Pfkb5zIwCcCe0W i4FsnhCOWAMFCTu0stJHCGQ= =k4X7 -----END PGP SIGNATURE----- _______________________________________________ Classpath mailing list Classpath@gnu.org http://lists.gnu.org/mailman/listinfo/classpath