On 10/17/13 7:16 PM, Mandy Chung wrote:
On 10/16/13 5:35 AM, Daniel Fuchs wrote:
Hi,
Please find below the new revision:
http://cr.openjdk.java.net/~dfuchs/webrev_8026499/webrev.01/
Looks good.
As for the test, LoggingSupport.getLogger is just a layer to support the
PlatformLogger be
On 10/16/13 5:35 AM, Daniel Fuchs wrote:
Hi,
Please find below the new revision:
http://cr.openjdk.java.net/~dfuchs/webrev_8026499/webrev.01/
Looks good.
As for the test, LoggingSupport.getLogger is just a layer to support the
PlatformLogger be called in the absence of java.util.logging
Hi Mandy,
On 10/16/13 12:58 AM, Mandy Chung wrote:
On 10/15/2013 9:48 AM, Daniel Fuchs wrote:
Hi,
Please find below a fix for:
8026499: Root Logger level can be reset unexpectedly
https://bugs.openjdk.java.net/browse/JDK-8026499
Hi,
Please find below the new revision:
http://cr.openjdk.java.net/~dfuchs/webrev_8026499/webrev.01/
- added comment in LogManager
- renamed hasLocalLevel() into isLevelInitialized()
- fixed the test, including Logger.global, with and
without SecurityManager
-- daniel
On 10/16/13 11:47
Hi,
Please find below a fix for:
8026499: Root Logger level can be reset unexpectedly
https://bugs.openjdk.java.net/browse/JDK-8026499
http://cr.openjdk.java.net/~dfuchs/webrev_8026499/webrev.00/
The issue here is that calling a method like e.g. URL.openConnection()
will trigger the
On 10/15/2013 9:48 AM, Daniel Fuchs wrote:
Hi,
Please find below a fix for:
8026499: Root Logger level can be reset unexpectedly
https://bugs.openjdk.java.net/browse/JDK-8026499
http://cr.openjdk.java.net/~dfuchs/webrev_8026499/webrev.00/
The issue here is that calling a method like