[commit-cp] [bug #13129] logging system configured from wrong location

[Robert Schuster]

URL:
  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=13129>

                 Summary: logging system configured from wrong location
                 Project: classpath
            Submitted by: rschuster
            Submitted on: Thu 05/19/2005 at 22:54
                Category: classpath
                Severity: 4 - Important
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
        Platform Version: None

    _______________________________________________________

Details:

According to the documentation of java.util.logging.LogManager (whose
official doc can be found here
http://developer.classpath.org/doc/java/util/logging/LogManager.html ;) ) the
configuration should be loaded in this way:

"If the system property java.util.logging.config.file  is not set, however,
the contents of the URL "{gnu.classpath.home.url}/logging.properties" are
passed to readConfiguration(InputStream). Here, "{gnu.classpath.home.url}"
stands for the value of the system property gnu.classpath.home.url"

That means reading of a physical file like
/usr/share/classpath/logging/logging.properties should happen. 

However currently our logging.properties file is part of the system classpath
and lies at java/util/logging (e.g. within glibj.zip).

To be correct with the specificatio above the file should be taken out of the
classpath and installed at ${prefix}/lib/logging.

However I have to admit that this would mean /usr/lib/logging on many systems
and I am not sure whether this is a suitable place. I suggest
/usr/lib/classpath/logging instead.






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?func=detailitem&item_id=13129>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/