[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-525) Consider shipping log4j jar in root lib/ directory

[Manik Surtani (JIRA)]

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

Manik Surtani resolved ISPN-525.
--------------------------------

    Resolution: Done


> Consider shipping log4j jar in root lib/ directory
> --------------------------------------------------
>
>                 Key: ISPN-525
>                 URL: https://jira.jboss.org/browse/ISPN-525
>             Project: Infinispan
>          Issue Type: Task
>            Reporter: Galder Zamarreno
>            Assignee: Manik Surtani
>             Fix For: 4.1.0.CR1
>
>
> Look into adding a log4 jar to root lib/ directory in distribution in order for modifications to etc/log4j.xml to have immediate effect.
> If log4j jar cannot be found, Infinispan uses JDK logging by default and it's not very obvious that a log4j jar is missing and that's why log4j.xml changes have no impact.
> This happens with any modules executed except: gui, ec2 and lucene-directory modules.
> These modules don't have this issue cos they ship a log4 jar:
> ./modules/ec2/lib/log4j-1.2.14.jar
> ./modules/gui/lib/log4j-1.2.14.jar
> ./modules/lucene-directory-demo/lib/log4j-1.2.14.jar

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira