logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Newman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-786) Unit testing with log4j2
Date Mon, 18 Aug 2014 23:45:18 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14101538#comment-14101538
] 

Alex Newman commented on LOG4J2-786:
------------------------------------

So let me be super clear. I am trying to move HBase over to log4j2. HBase produces tons of
INFO statements in the tests. Traditionally we don't want those just spamming the screen when
a user runs mvn test. We have traditionally redirected the output so instead of going directly
to stdout it gets redirected to classname-output.txt. I am trying to recreate that with log4j2.

> Unit testing with log4j2 
> -------------------------
>
>                 Key: LOG4J2-786
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-786
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: Alex Newman
>            Priority: Critical
>
> I still have no idea, how with a maven project with submodules, how to create a separate
file per test with the test output in it. I used to just output to the console and then use
maven.test.redirectTestOutput. This no longer works. 
> It was nice to be able to just turn this on and off with a simple property.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message