[jira] [Commented] (LOG4J2-522) Split Logger interface in two with named level methods (info, warn, ...) in the subinterface.

[ https://issues.apache.org/jira/browse/LOG4J2-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886359#comment-13886359 ] Nick Williams commented on LOG4J2-522: -- -0: Paul has suggested we hold off on "Using

[jira] [Commented] (LOG4J2-522) Split Logger interface in two with named level methods (info, warn, ...) in the subinterface.

[ https://issues.apache.org/jira/browse/LOG4J2-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886345#comment-13886345 ] Remko Popma commented on LOG4J2-522: +1: we probably want to do this before 2.0 GA. (

[jira] [Updated] (LOG4J2-522) Split Logger interface in two with named level methods (info, warn, ...) in the subinterface.

[ https://issues.apache.org/jira/browse/LOG4J2-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Gregory updated LOG4J2-522: Attachment: log4j-522.diff Split proposal. > Split Logger interface in two with named level method

[jira] [Created] (LOG4J2-522) Split Logger interface in two with named level methods (info, warn, ...) in the subinterface.

Gary Gregory created LOG4J2-522: --- Summary: Split Logger interface in two with named level methods (info, warn, ...) in the subinterface. Key: LOG4J2-522 URL: https://issues.apache.org/jira/browse/LOG4J2-522

LOG4J2-301 - Add printf methods to Logger API

I'm slightly confused by this addition because it seems redundant with using StringFormattedMessage and StringFormattedMessageFactory Gary -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition JUnit in Action, Sec

[jira] [Commented] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886245#comment-13886245 ] Michael Kloster commented on LOG4J2-323: Yes, I will pull and verify tonight. > T

[jira] [Commented] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886239#comment-13886239 ] Remko Popma commented on LOG4J2-323: Nick, nice catch! Thanks! Mickael, can you veri

[jira] [Resolved] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams resolved LOG4J2-323. -- Resolution: Fixed Fixed with r1562688. Please verify and close. > ThreadLocal-leak on tomcat s

[jira] [Reopened] (LOG4J2-323) ThreadLocal-leak on tomcat shutdown when using async logging

[ https://issues.apache.org/jira/browse/LOG4J2-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Williams reopened LOG4J2-323: -- Remko, Nulling out the reference to the {{ThreadLocal}} is not enough (in fact, it's not even nec

Re: Using Custom Levels with a Custom/Wrapper Interface

I agree. Nick On Jan 29, 2014, at 5:09 PM, Paul Benedict wrote: > I would like to propose not doing anything on this subject until there is a > request from the community. It's probably way too easy to over-engineer and > devise solutions to problems that a small percentage (or zero?) of the u

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Description: {anchor:Extending} *[#Extending] the Logger interface* LOG4J2-41 added support for custo

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Description: {anchor:Extending} *[#Extending] the Logger interface* LOG4J2-41 added support for custo

[jira] [Comment Edited] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13886105#comment-13886105 ] Remko Popma edited comment on LOG4J2-519 at 1/30/14 12:56 AM: --

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Description: *[#Extending] the Logger interface* LOG4J2-41 added support for custom log Levels. Users

[jira] [Comment Edited] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884294#comment-13884294 ] Remko Popma edited comment on LOG4J2-519 at 1/30/14 12:55 AM: --

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Attachment: Generate.java Updated attached file "Generate.java" with code change for the renamed meth

Re: Using Custom Levels with a Custom/Wrapper Interface

I would like to propose not doing anything on this subject until there is a request from the community. It's probably way too easy to over-engineer and devise solutions to problems that a small percentage (or zero?) of the users will need. I am all for ingenuity and passion, but after GA occurs and

[jira] [Updated] (LOG4J2-519) Custom/Extended Loggers

[ https://issues.apache.org/jira/browse/LOG4J2-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-519: --- Attachment: (was: Generate.java) > Custom/Extended Loggers > --- > >

Re: [jira] [Commented] (LOG4J2-518) Logging of nested list uses incorrect charset

>So I agree we can blame Eclipse! Welcome aboard the IntelliJ express! On 28 January 2014 10:53, Remko Popma (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/LOG4J2-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884322#comment-1388432

Re: Using Custom Levels with a Custom/Wrapper Interface

Annotation processing is beyond over-engineered, yet it still lacks some of the neat features from runtime annotation "processing". I've been meaning to look more into it as it might be useful for injecting Loggers using annotations. On 29 January 2014 07:46, Remko Popma wrote: > > > On Wednesd

[jira] [Commented] (LOG4J2-33) Support Annotations

[ https://issues.apache.org/jira/browse/LOG4J2-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885946#comment-13885946 ] Matt Sicker commented on LOG4J2-33: --- I've got a better idea on how to implement this. Two

[jira] [Commented] (LOG4J2-506) Binary logging interface

[ https://issues.apache.org/jira/browse/LOG4J2-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885548#comment-13885548 ] Gregg Donovan commented on LOG4J2-506: -- Remko -- we've been in the middle of a Solr/L

[jira] [Commented] (LOG4J2-508) Add new Levels: NOTICE, DIAG, VERBOSE.

[ https://issues.apache.org/jira/browse/LOG4J2-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885392#comment-13885392 ] Gary Gregory commented on LOG4J2-508: - Yes, leave it open please. > Add new Levels: N

Re: Using Custom Levels with a Custom/Wrapper Interface

On Wednesday, January 29, 2014, Nick Williams wrote: > > On Jan 28, 2014, at 5:43 PM, Remko Popma wrote: > > I would really like everyone's feedback on this. I have two questions: > > 1. Does this fulfill everyone's requirements? > Another way of asking this is: would you use this in your own pro

[jira] [Comment Edited] (LOG4J2-444) Log4j2 eclipselink integration

[ https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885304#comment-13885304 ] Hemri edited comment on LOG4J2-444 at 1/29/14 12:52 PM: Hi, I wan

[jira] [Commented] (LOG4J2-444) Log4j2 eclipselink integration

[ https://issues.apache.org/jira/browse/LOG4J2-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885304#comment-13885304 ] Hemri commented on LOG4J2-444: -- Hi, I want to EclipseLink's internal logging statements go t

[Bug 56086] New: Exceptions not thrown, simply printed to stack trace

https://issues.apache.org/bugzilla/show_bug.cgi?id=56086 Bug ID: 56086 Summary: Exceptions not thrown, simply printed to stack trace Product: Log4j Version: unspecified Hardware: PC Status: NEW Severity: normal

[jira] [Resolved] (LOG4J2-492) MalformedObjectNameException: Invalid escape sequence... under Jetty

[ https://issues.apache.org/jira/browse/LOG4J2-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-492. Resolution: Fixed I've made a change to escape the context name before unregistering the LoggerCon

[jira] [Commented] (LOG4J2-392) Intermittent errors with appenders

[ https://issues.apache.org/jira/browse/LOG4J2-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885182#comment-13885182 ] Andre Bogus commented on LOG4J2-392: Hi again, @Remko: Great to see you working on th

[jira] [Comment Edited] (LOG4J2-492) MalformedObjectNameException: Invalid escape sequence... under Jetty

[ https://issues.apache.org/jira/browse/LOG4J2-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885167#comment-13885167 ] Remko Popma edited comment on LOG4J2-492 at 1/29/14 9:43 AM: -

[jira] [Commented] (LOG4J2-492) MalformedObjectNameException: Invalid escape sequence... under Jetty

[ https://issues.apache.org/jira/browse/LOG4J2-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885167#comment-13885167 ] Remko Popma commented on LOG4J2-492: I reopened this yesterday afternoon as I still ne

Re: ApacheCon CFP

On 29 Jan 2014, at 0:22, Remko Popma wrote: ... I'm still learning proper ML etiquette... Just for the record: i didn't mean you or anyone hear at Logging ;-) Very nice slides, btw. On Wednesday, January 29, 2014, Christian Grobmeier wrote: I would love to go, but i have to deal with a