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

[Dan Berindei (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Berindei resolved ISPN-2976.
--------------------------------
           Labels:   (was: core)
         Assignee: Tristan Tarrant
    Fix Version/s: 8.0.0.Beta2
       Resolution: Done


The dependencies in SampleConfigFilesCorrectnessTest, CompressedFileAppender, and ThreadNameFilter are required, but were updated to the log4j 2.0 SPI.

> Log4J dependencies in codebase to be cleaned up
> -----------------------------------------------
>
>                 Key: ISPN-2976
>                 URL: https://issues.jboss.org/browse/ISPN-2976
>             Project: Infinispan
>          Issue Type: Task
>          Components: Core
>    Affects Versions: 5.2.5.Final
>            Reporter: Manik Surtani
>            Assignee: Tristan Tarrant
>             Fix For: 8.0.0.Beta2
>
>
> 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 was sent by Atlassian JIRA
(v6.3.15#6346)