Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 20 Feb 2013 11:41:13 +0000 (UTC)
From: "Thomas Neidhart (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12477410.1287098189032.310060.1361360473414@arcas>
In-Reply-To: <JIRA.12477410.1287098189032@arcas>
References: <JIRA.12477410.1287098189032@arcas>
Subject: [jira] [Resolved] (LOGGING-138) Show stacktrace for flawed
 discovery in diagnostic messages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thomas Neidhart resolved LOGGING-138.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.2

Added in r1448097.
Used a StringWriter instead of your patch, thanks for the report!
                
> Show stacktrace for flawed discovery in diagnostic messages
> -----------------------------------------------------------
>
>                 Key: LOGGING-138
>                 URL: https://issues.apache.org/jira/browse/LOGGING-138
>             Project: Commons Logging
>          Issue Type: Improvement
>    Affects Versions: 1.1.0, 1.1.1
>            Reporter: Luke Lu
>             Fix For: 1.1.2
>
>         Attachments: logging-138-trunk-v1.patch
>
>
> It looks like since 1.1, if a custom log appender throws an exception the stack trace is not shown in diagnostic messages, making it harder (than 1.0.4) to find out the root cause of the log initialization problem.
> Here is a simple patch against the trunk to address the issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira