You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2017/06/25 01:33:00 UTC

[jira] [Updated] (LOG4J2-1811) Log4j 2 configuration/usage ergonomics

     [ https://issues.apache.org/jira/browse/LOG4J2-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Remko Popma updated LOG4J2-1811:
--------------------------------
    Description: 
The vast majority of StackOverflow Log4j 2 questions is related to configuration. The Log4j 2 site offers an extensive manual but apparently many questions remain.

This ticket aims to make Log4j 2 easier to configure and use. This can take many forms: 
* detecting and addressing inconsistencies
* facilitating debugging
* showing richer error messages that help users diagnose problems
* adding documentation
* making documentation easier to find
* ... etc

I am making this an epic so the effort can span multiple releases and include many big or small changes.

  was:
The vast majority of StackOverflow Log4j 2 questions is related to configuration. The Log4j 2 site offers an extensive manual but apparently many questions remain.

This ticket aims to make Log4j 2 easier to configure and use. This can take many forms: 
* adding documentation
* making documentation easier to find
* detecting and addressing inconsistencies
* facilitating debugging
* showing richer error messages that help users diagnose problems
* ... etc

I am making this an epic so the effort can span multiple releases and include many big or small changes.


> Log4j 2 configuration/usage ergonomics
> --------------------------------------
>
>                 Key: LOG4J2-1811
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1811
>             Project: Log4j 2
>          Issue Type: Epic
>          Components: Configurators, Core
>            Reporter: Remko Popma
>
> The vast majority of StackOverflow Log4j 2 questions is related to configuration. The Log4j 2 site offers an extensive manual but apparently many questions remain.
> This ticket aims to make Log4j 2 easier to configure and use. This can take many forms: 
> * detecting and addressing inconsistencies
> * facilitating debugging
> * showing richer error messages that help users diagnose problems
> * adding documentation
> * making documentation easier to find
> * ... etc
> I am making this an epic so the effort can span multiple releases and include many big or small changes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)