[infinispan-issues] [JBoss JIRA] (ISPN-2976) Log4J dependencies in codebase to be cleaned up

[Adrian Nistor (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769794#comment-12769794 ] 

Adrian Nistor commented on ISPN-2976:
-------------------------------------

log4j 1.x also has some concurrency bugs like this one https://issues.apache.org/bugzilla/show_bug.cgi?id=50213 that leads to hanged test suites very often. It wold be good to move away from it.
                
> Log4J dependencies in codebase to be cleaned up
> -----------------------------------------------
>
>                 Key: ISPN-2976
>                 URL: https://issues.jboss.org/browse/ISPN-2976
>             Project: Infinispan
>          Issue Type: Task
>    Affects Versions: 5.2.5.Final
>            Reporter: Manik Surtani
>            Assignee: Mircea Markus
>             Fix For: 5.3.0.Beta1, 5.3.0.Final
>
>
> When attempting to move to Log4J 2.0, I've noticed a number of hard deps on log4j classes.
> {{SampleConfigFilesCorrectnessTest}} - this class makes use of a custom appender to analyse what a user is being warned of when a config file is parsed.  Why are we using Log4J for this?  Our own logging interface should be mocked and messages captured directly.
> {{RehashStressTest}} and {{NucleotideCache}} - seems like a bug, I presume the author intended to use {{org.infinispan.logging.Log}}.
> {{CompressedFileAppender}} and {{ThreadNameFilter}}- can this be written in a way that works with Log4J 1.x as well as 2.x?  Or have the SPIs changed that much?

--
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