September 2013 - logback-dev

[JIRA] (LOGBACK-384) Mixing periods and dollar signs in a logger name causes IllegalArgumentException from LoggerFactory.getLogger
by Tony Trinh (JIRA) 07 Sep '13

07 Sep '13

1 0

[JIRA] (LOGBACK-384) Mixing periods and dollar signs in a logger name causes IllegalArgumentException from LoggerFactory.getLogger
by Tony Trinh (JIRA) 07 Sep '13

07 Sep '13

1 0

[JIRA] (LOGBACK-384) Mixing periods and dollar signs in a logger name causes IllegalArgumentException from LoggerFactory.getLogger
by Chetan Mehrotra (JIRA) 05 Sep '13

05 Sep '13

1 0

[JIRA] (LOGBACK-384) Mixing periods and dollar signs in a logger name causes IllegalArgumentException from LoggerFactory.getLogger
by Bertrand Delacretaz (JIRA) 05 Sep '13

05 Sep '13

1 0

[JIRA] (LOGBACK-896) SocketAppender causes Deadlock
by Arnd Hannemann (JIRA) 05 Sep '13

05 Sep '13

1 0

[JIRA] (LOGBACK-896) SocketAppender causes Deadlock
by Arnd Hannemann (JIRA) 05 Sep '13

05 Sep '13

1 0

[JIRA] (LOGBACK-747) maxHistory doesnot normally work in SizeAndTimeBasedFNATP
by Phi Vu Nguyen (JIRA) 03 Sep '13

03 Sep '13

1 0

Patch Submitted to JDK for Public getCallerClass Replacement (Cross-Posted from Log4j Dev Mailing List)
by Nick Williams 01 Sep '13

01 Sep '13

Guys, If you have been following any of the discussions on the Log4j or Java 8 Core-Libs-Dev mailing list, you likely know what's going on with sun.reflect.Reflection#getCallerClass(int). My understanding is that these issues directly affect the Logback team. After about a month of work (not full-time; balancing with $work and writing), I have completed a new public API that replaces Reflection#getCallerClass(int). As of last night, I have submitted my patch to the JDK mailing list: http://mail.openjdk.java.net/pipermail/core-libs-dev/2013-September/020477.… I appreciate anyone who can support it verbally on the list, but of course the most critical test is whether we can get a committer to sponsor the change. There hasn't been a whole lot of /apparent/ willingness to cooperate on the development and refinement of the API from the people in charge over there, so I'm hoping with enough voices we can get this patch taken seriously and prevent the impending catastrophe of losing getCallerClass. :-) Thanks, Nick Williams Apache Logging

1 0