logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1379) Documentation is subzero quality as far as yaml config files are concerned
Date Mon, 11 Jul 2016 09:28:10 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370441#comment-15370441

Remko Popma commented on LOG4J2-1379:

Good stuff, thanks!

Quick comments:
* status logger level is different (but that is a detail, easy to fix)
* AppenderRef elements in XML have a level attribute. You may want to show how to do that
in YAML also.
* Interesting that \{\} needs to be specified for TimeBasedTriggeringPolicy.

By the way, how would one specify a comment in a YAML file?

This is very good, keep 'em coming!

> Documentation is subzero quality as far as yaml config files are concerned
> --------------------------------------------------------------------------
>                 Key: LOG4J2-1379
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1379
>             Project: Log4j 2
>          Issue Type: Bug
>            Reporter: piero de salvia
>         Attachments: log4j2.xml, log4j2.yaml
> Documentation for yaml config files 
> http://logging.apache.org/log4j/2.x/manual/configuration.html
> fails to mention that this dependency must be added to actually use yaml config files:
> {code}
>         <dependency>
>             <groupId>com.fasterxml.jackson.dataformat</groupId>
>             <artifactId>jackson-dataformat-yaml</artifactId>
>             <version>2.7.4</version>
>         </dependency>
> {code}
> It also fails to mention that the equivalent basic config in yaml is the following:
> {code}
> Configuration:
>   status: warn
>   Appenders:
>     Console:
>       name: Console
>       target: SYSTEM_OUT
>       PatternLayout:
>         Pattern: "%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} - %msg%n"
>   Loggers:
>     Root:
>       level: info
>       AppenderRef:
>         ref: Console
> {code}
> At runtime, log4j2 "does not find" the config file (useless and misleading error message),
which in reality means it does not find the needed dependencies.
> To actually fix this, one must debug log4j2.
> So basically failing to mention something in documentation (effort = 0) causes users
to have to debug log4j (effort >> 0).
> This gives the whole project an amateurish and unkempt feel.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message