[
https://issues.apache.org/jira/browse/LOG4NET-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679336#comment-13679336
]
Dominik Psenner commented on LOG4NET-342:
-----------------------------------------
Yes it should stay focused on being the interface to log messages, but there's
already the IsEnabled stuff and therefore people expect a IsConfigured.
LogManager.GetRepository().Configured is easy enough for someone who knows it,
but hard to find and since people are lazy, they look at the ILog instance and
subsequently ask silly questions. I agree that there's still work to be done on
the ConfigurationMessages, but that's should probably be coped with a separate
issue.
> 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
> Assignee: Dominik Psenner
> Priority: Minor
> Fix For: 1.2.12
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
