[logback-dev] [JIRA] Commented: (LBCLASSIC-58) Print Logback own erros to System.out if debug is enabled?

Diego Louzán (JIRA) noreply-jira at qos.ch
Fri Aug 8 11:44:25 CEST 2008

    [ http://jira.qos.ch/browse/LBCLASSIC-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10637#action_10637 ] 

Diego Louzán commented on LBCLASSIC-58:

Maybe one solution would be, if the system property is not set, fallback to check if a logback defined equivalent env-entry parameter is set using jndi? That way any j2ee container will be able to add listeners without using system properties. Furthermore, this setting would be context-limited as env-entry params are defined per webapp context, unlike system properties which are global to the application.

Anyway, this still feels "overkill" to me, I mean, it should be default behaviour to log logback status if any problem occurs while initializating.

> Print Logback own erros to System.out if debug is enabled?
> ----------------------------------------------------------
>                 Key: LBCLASSIC-58
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-58
>             Project: logback-classic
>          Issue Type: Improvement
>            Reporter: Anton Tagunov
>            Assignee: Logback dev list
>            Priority: Minor
> Hello Ceki, when debug is enabled lots of messages to to System.out anyway.
> Do you think it would be a good idea to also print messages going to StatusManager to System.out?
> Apparently there is huge demand for this feature.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the logback-dev mailing list