[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832584#comment-13832584
]
Gary Gregory commented on LOG4J2-41:
(c) is not much of an argument as Log4J itself is
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831753#comment-13831753
]
Nick Williams commented on LOG4J2-41:
-
So I hate to reopen old wounds, but I'm going to
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832166#comment-13832166
]
Gary Gregory commented on LOG4J2-41:
Well, now is a good time to review since we are
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13832363#comment-13832363
]
Noel Grandin commented on LOG4J2-41:
Hmmm,
I don't see this issue keep coming up.
I am not in favor of adding 9 or 10 new sets of methods to the Logger interface.
Ralph
On Mar 26, 2013, at 11:10 AM, Gary Gregory wrote:
Hm, I can see having an API that let's in custom int levels would satisfy
some cases. But why not consider adding more built-in levels? See the thread
on
I think we can discuss both issues separately: (1) more level and (2) how
they show up in the API.
(1) Let's discuss the merits how more log levels. Should we go the Apache
HTTPD route? version 2.2? 2.4?
(2) Then let's discuss if and how they should show up in the API.
v2 is the best time to
On Mar 27, 2013, at 9:36 AM, Gary Gregory wrote:
I think we can discuss both issues separately: (1) more level and (2) how
they show up in the API.
(1) Let's discuss the merits how more log levels. Should we go the Apache
HTTPD route? version 2.2? 2.4?
(2) Then let's discuss if and
My $0.02...
It seems to me that the only immediate decision that needs to be made is what
the Level class should consist of. Should it be a straight-up enum or Nick's
extensible enum?
Given that Nick's extensible enum allows for so much more
flexibility/extensibility, it also seems to me
On 2013-03-27 16:36, Gary Gregory wrote:
I think we can discuss both issues separately: (1) more level and (2)
how they show up in the API.
(1) Let's discuss the merits how more log levels. Should we go the
Apache HTTPD route? version 2.2? 2.4?
My 2c is that the people requiring more levels
On 27.03.2013 16:55, Noel Grandin wrote:
On 2013-03-27 16:36, Gary Gregory wrote:
I think we can discuss both issues separately: (1) more level and (2)
how they show up in the API.
(1) Let's discuss the merits how more log levels. Should we go the
Apache HTTPD route? version 2.2? 2.4?
My 2c
Hm, I can see having an API that let's in custom int levels would satisfy
some cases. But why not consider adding more built-in levels? See the
thread on the ML.
Apache HTTPD 2.2 has 8 levels:
https://httpd.apache.org/docs/2.2/mod/core.html#loglevel
Apache HTTPD 2.2 has 16 levels:
Blame Gary for not commenting in JIRA, which lead me not to comment in
JIRA. I guess that makes me a Lemming!
On Tue, Mar 26, 2013 at 3:34 PM, Nick Williams
nicho...@nicholaswilliams.net wrote:
This can be confusing, following both this email chain and the bug
comments. :-P
In case you have
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13612306#comment-13612306
]
Nick Williams commented on LOG4J2-41:
-
Since there was discussion on the user list
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13612307#comment-13612307
]
Nick Williams commented on LOG4J2-41:
-
Apparently this JIRA has disabled code
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12926611#action_12926611
]
Ralph Goers commented on LOG4J2-41:
---
After more work and thought I am more inclined to
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893952#action_12893952
]
Ralph Goers commented on LOG4J2-41:
---
I'm not suggesting that this issue be closed at this
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893616#action_12893616
]
Ralph Goers commented on LOG4J2-41:
---
A brief discussion just took place on the Logback
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893924#action_12893924
]
Curt Arnold commented on LOG4J2-41:
---
I agree that most urges to use extensible levels are
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12874415#action_12874415
]
Curt Arnold commented on LOG4J2-41:
---
Both java.util.logging and log4j 1.2 support user
19 matches
Mail list logo
