[jira] [Commented] (GEODE-6964) Log4j configuration can be altered by adding geode-core to the classpath

["Kirk Lund (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16901296#comment-16901296 ] 

Kirk Lund commented on GEODE-6964:
----------------------------------

Notes for fixing this ticket:
* All code that uses {{log4j-core}} should move to new submodule {{geode-log4j}} which will create its own jar file
* The {{log4j2.xml}} should move to either {{geode-log4j}} or {{geode-log4j-config}} -- users might want to use {{log4j2.xml}} without the log4j-core code in {{geode-log4j}} especially for geode clients
* Backport the above changes to {{1.9.x}} (and above) maintenance branches

> Log4j configuration can be altered by adding geode-core to the classpath
> ------------------------------------------------------------------------
>
>                 Key: GEODE-6964
>                 URL: https://issues.apache.org/jira/browse/GEODE-6964
>             Project: Geode
>          Issue Type: Bug
>          Components: logging
>            Reporter: Stephane Nicoll
>            Priority: Major
>
> {{geode-core}} ships with a {{log4j2.xml}} at the standard location which means that it is a candidate for bootstraping the logging infrastructure of any app using that library. See also #GEODE-189
> This is a problem when embedding this library in application that relies on the absence of such a file to derive a sensible default configuration (typically a Spring Boot app).
> In general, the hard dependency on log4j is a bit annoying for the embedded use case. There is more context available here: https://github.com/spring-projects/spring-boot-data-geode/issues/42



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)