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 Tue, 19 Aug 2014 02:08:18 GMT

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

Alex Newman commented on LOG4J2-786:

Calling this out as a major problem. Perhaps I am missing a lot here. Afaik this requires
that we add a testrule to every test class(about one thousand files in our case). I don't
mind that so much however, if the developer forgets to put the rule in, basically we just
spam the logs.

I don't know if I have a better answer other than supporting maven.test.redirectTestOutputToFile,
but I am pretty worried that the upgrade just isn't worth it.

> 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

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

View raw message