logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joachim Zobel (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4NET-342) Add a way to prevent silent failure
Date Tue, 22 May 2012 17:25:40 GMT

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

Joachim Zobel updated LOG4NET-342:
----------------------------------

    Description: 
I spent most of the day trying to find out why logging is not working on my dev system but
not on test. There should be a way to force error reporting by throwing (possibly unhandled)
exceptions. This could be done by adding a required flag to the appenders and another flag
that requires a least one working appender.

I am not sure about a good way to implement this, I would just love it if my favourite tool
to end silent failure could stop failing silently. 


    
> Add a way to prevent silent failure
> -----------------------------------
>
>                 Key: LOG4NET-342
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-342
>             Project: Log4net
>          Issue Type: New Feature
>            Reporter: Joachim Zobel
>
> I spent most of the day trying to find out why logging is not working on my dev system
but not on test. There should be a way to force error reporting by throwing (possibly unhandled)
exceptions. This could be done by adding a required flag to the appenders and another flag
that requires a least one working appender.
> I am not sure about a good way to implement this, I would just love it if my favourite
tool to end silent failure could stop failing silently. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message