[jboss-jira] [JBoss JIRA] Resolved: (JGRP-1071) Allow JDK Logger Imp use even if Log4j available on classpath (Patch Attached)

[Bela Ban (JIRA)]

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

Bela Ban resolved JGRP-1071.
----------------------------

    Resolution: Done


Applied, changed the system property to jgroups.use.jdk_logger

> Allow JDK Logger Imp use even if Log4j available on classpath (Patch Attached)
> ------------------------------------------------------------------------------
>
>                 Key: JGRP-1071
>                 URL: https://jira.jboss.org/jira/browse/JGRP-1071
>             Project: JGroups
>          Issue Type: Feature Request
>    Affects Versions: 2.7
>         Environment: Linux 2.6.28-15-generic #49-Ubuntu SMP,x86_64 GNU/Linux, java version "1.6.0_16",Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
>            Reporter: Seamus Donohue
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 2.8
>
>         Attachments: sd.patch
>
>
> The org.jgroups.logging.LogFactory.getLog(Class clazz) will return a Log4j impl if the org.apache.log4j.Logger class is available.
> It would be nice to allow the implementer to force the use of the JDK logger even if this log4j class is available. 
> One way is to support a VM argmument -Djgroups.use.jdk.logger=true to force the use of the JDK log impl (Patch attached).

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