Update site content for Apache Project Branding Requirements
Key: LOG4J2-45
URL: https://issues.apache.org/jira/browse/LOG4J2-45
Project: Log4j 2
Issue Type: Task
Repor
[
https://issues.apache.org/jira/browse/LOG4J2-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-tabpanel&focusedCommentId=12874415#action_12874415
]
Curt Arnold commented on LOG4J2-41:
---
Both java.util.logging and log4j 1.2 support user def
Improving log4j so it can easily be used with servlet logging
-
Key: LOG4J2-42
URL: https://issues.apache.org/jira/browse/LOG4J2-42
Project: Log4j 2
Issue Type: Wish
Compo
Support getLogger(Object)
-
Key: LOG4J2-37
URL: https://issues.apache.org/jira/browse/LOG4J2-37
Project: Log4j 2
Issue Type: Task
Components: API
Reporter: Curt Arnold
Suggested at http://wiki.
[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873295#action_12873295
]
Curt Arnold commented on LOG4J2-10:
---
A few resources from browsing, haven't processed them
[
https://issues.apache.org/jira/browse/LOG4J2-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871004#action_12871004
]
Curt Arnold commented on LOG4J2-36:
---
Layout should be part of the Channel since some appen
Appender interface should be refactored
---
Key: LOG4J2-36
URL: https://issues.apache.org/jira/browse/LOG4J2-36
Project: Log4j 2
Issue Type: Wish
Components: Appenders
Reporter: Curt
log4j 2 should be modular
-
Key: LOG4J2-34
URL: https://issues.apache.org/jira/browse/LOG4J2-34
Project: Log4j 2
Issue Type: Wish
Reporter: Curt Arnold
See
http://mail-archives.apache.org/mod_mbox/loggi
Author tags
---
Key: LOG4J2-30
URL: https://issues.apache.org/jira/browse/LOG4J2-30
Project: Log4j 2
Issue Type: Wish
Reporter: Curt Arnold
Priority: Minor
Logging this as a bug so that it eventually gets re
Increased support for properties
Key: LOG4J2-28
URL: https://issues.apache.org/jira/browse/LOG4J2-28
Project: Log4j 2
Issue Type: Wish
Components: API
Reporter: Curt Arnold
On Dec 3, 2
[
https://issues.apache.org/jira/browse/LOG4J2-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curt Arnold updated LOG4J2-27:
--
Attachment: jspwiki-log.pdf
PDF version of OpenOffice document referenced in mailing list post. Origi
log4j 2 should implement the SLF4J API directly
---
Key: LOG4J2-27
URL: https://issues.apache.org/jira/browse/LOG4J2-27
Project: Log4j 2
Issue Type: Wish
Components: API
Repor
[
https://issues.apache.org/jira/browse/LOG4J2-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curt Arnold resolved LOG4J2-26.
---
Resolution: Invalid
This is a question about chainsaw behavior which should have been asked on
log4j-
[
https://issues.apache.org/jira/browse/LOG4J2-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curt Arnold resolved LOG4J2-25.
---
Resolution: Invalid
This JIRA is for log4j 2.0 development. To report a bug against log4j 1.2,
pleas
Have an API method that does a deeper evaluation than Logger.isDebugEnabled()
of whether logging will occur
---
Key: LOG4J2-24
URL: https://issues.apache.org/j
log4j 2.0 should work without an explicit configuration file
Key: LOG4J2-23
URL: https://issues.apache.org/jira/browse/LOG4J2-23
Project: Log4j 2
Issue Type: Wish
Compone
[
https://issues.apache.org/jira/browse/LOG4J2-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620988#action_12620988
]
Curt Arnold commented on LOG4J2-22:
---
You do not mention what appender you are using. I'm
[
https://issues.apache.org/jira/browse/LOG4J2-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curt Arnold resolved LOG4J2-22.
---
Resolution: Invalid
Marking this bug as INVALID as it is not related to log4j 2.0. This JIRA
project
LoggingEvent message lost on serialization
--
Key: LOG4J2-21
URL: https://issues.apache.org/jira/browse/LOG4J2-21
Project: Log4j 2
Issue Type: Wish
Components: Appenders
Reporter:
[
https://issues.apache.org/jira/browse/LOG4J2-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607140#action_12607140
]
Curt Arnold commented on LOG4J2-16:
---
I think that this can fit into the "context" concept
log4j 2 should have clean separation of configuration from function
---
Key: LOG4J2-20
URL: https://issues.apache.org/jira/browse/LOG4J2-20
Project: Log4j 2
Issue Type: Test
[
https://issues.apache.org/jira/browse/LOG4J2-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607138#action_12607138
]
Curt Arnold commented on LOG4J2-19:
---
The pattern parsing is a specialized form of configur
log4j 2.0 development initation
---
Key: LOG4J2-14
URL: https://issues.apache.org/jira/browse/LOG4J2-14
Project: Log4j 2
Issue Type: Task
Reporter: Curt Arnold
Start of log4j/branches/BRANCH_2_0_EXPE
Appenders, layouts, etc should support deferred processing
--
Key: LOG4J2-13
URL: https://issues.apache.org/jira/browse/LOG4J2-13
Project: Log4j 2
Issue Type: Wish
Reporter:
log4j 2.0 should provide an API that is generally source compatible with log4j
1.2
--
Key: LOG4J2-12
URL: https://issues.apache.org/jira/browse/LOG4J2-12
Project: Log4j 2
log4j 2.0 should provide a log4j 1.2 emulation that is reasonably binary
compatible with client applications
Key: LOG4J2-11
URL: https://issues.apache.org
log4j 2.0 should work well with OSGi and Apache Felix
-
Key: LOG4J2-10
URL: https://issues.apache.org/jira/browse/LOG4J2-10
Project: Log4j 2
Issue Type: Wish
Reporter: Curt Arno
[
https://issues.apache.org/jira/browse/LOG4J2-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606558#action_12606558
]
Curt Arnold commented on LOG4J2-9:
--
On Jun 19, 2008, at 3:58 PM, Jess Holle wrote:
I'd also
log4j 2.0 should leverage existing (preferably ASF) configuration frameworks
Key: LOG4J2-9
URL: https://issues.apache.org/jira/browse/LOG4J2-9
Project: Log4j 2
Issu
log4j 2.0 should support recursion
--
Key: LOG4J2-8
URL: https://issues.apache.org/jira/browse/LOG4J2-8
Project: Log4j 2
Issue Type: Wish
Components: Core
Reporter: Curt Arnold
log4j 1.
Java 5 idioms should be used in preference to earlier Java idioms
-
Key: LOG4J2-7
URL: https://issues.apache.org/jira/browse/LOG4J2-7
Project: Log4j 2
Issue Type: Wish
log4j 2.0 should support all capabilities of java.util.logging.
---
Key: LOG4J2-6
URL: https://issues.apache.org/jira/browse/LOG4J2-6
Project: Log4j 2
Issue Type: Wish
Com
Appenders, Layouts and other back-end classes should be independent of logging
API
--
Key: LOG4J2-5
URL: https://issues.apache.org/jira/browse/LOG4J2-5
Project: Log4j 2
Prefer java.nio to java.io
--
Key: LOG4J2-4
URL: https://issues.apache.org/jira/browse/LOG4J2-4
Project: Log4j 2
Issue Type: Wish
Components: Appenders
Reporter: Curt Arnold
java.nio classes sh
Minimal (aka fine grained) locking
--
Key: LOG4J2-3
URL: https://issues.apache.org/jira/browse/LOG4J2-3
Project: Log4j 2
Issue Type: Wish
Components: Core
Reporter: Curt Arnold
Most com
[
https://issues.apache.org/jira/browse/LOG4J2-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Curt Arnold resolved LOG4J2-2.
--
Resolution: Invalid
This JIRA is for capturing the requirements for the design of log4j 2.0. Bugs
again
Custom rendering of exception associated with logging event
---
Key: LOG4J2-1
URL: https://issues.apache.org/jira/browse/LOG4J2-1
Project: Log4j 2
Issue Type: Improvement
Comp
38 matches
Mail list logo