[
https://issues.apache.org/jira/browse/LOG4J2-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659915#comment-16659915
]
Remko Popma commented on LOG4J2-2484:
-------------------------------------
Interesting, thank you for that.
What I mean by use case is an explanation of what the problem is and what
change you propose to solve this problem. I like seeing a few sentences like "I
have an application that does X. I want to do XYZ because ABC. I currently
cannot do XYZ because log4j EDF. I propose we change log4j to allow people to
do XYZ." but it does not need to be this exact format.
Note that I don't consider _the problem is that I cannot point the StatusLogger
to another stream. I propose allowing people to point the StatusLogger to
another stream to solve this_ to be a valid use case; it does not give any
background or explain why you want to do this/what problem this solves for you.
> Allow setting of output stream on StatusLogger
> ----------------------------------------------
>
> Key: LOG4J2-2484
> URL: https://issues.apache.org/jira/browse/LOG4J2-2484
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Reporter: Robert Ross
> Priority: Minor
> Labels: StatusLogger, debugging
>
> The StatusLogger internally uses a SimpleLogger. SimpleLogger offers the
> ability to control the output stream, but StatusLogger encapsulates and hides
> this capability, always using System.err as the output stream.
> It would be useful to expose this option so that the API offers some control
> over the output stream used by StatusLogger.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
