[
https://issues.apache.org/jira/browse/LOGCXX-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Middleton resolved LOGCXX-524.
-------------------------------------
Resolution: Fixed
At this point I think the error output is better and errors should be properly
propagated to user code.
> Remove silent exceptions
> ------------------------
>
> Key: LOGCXX-524
> URL: https://issues.apache.org/jira/browse/LOGCXX-524
> Project: Log4cxx
> Issue Type: Improvement
> Affects Versions: 0.11.0
> Reporter: Robert Middleton
> Assignee: Robert Middleton
> Priority: Major
> Fix For: 1.0.0
>
>
> There are a number of exceptions that log4cxx can output if something bad
> happens. When this happens, all log4cxx does is to simply output a
> message(to stdout and/or stderr) instead of propagating that error back up to
> user-level code.
> See:
> https://stackoverflow.com/questions/34356804/log4cxx-try-catch-wont-work-on-domconfiguratorconfigure
> This may cause some unexpected behavior with already-existing code, so this
> needs to be effectively communicated with users and may wait until a major
> release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
