[ https://issues.apache.org/jira/browse/GEODE-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Hanson closed GEODE-6964. ------------------------------ Transition from Resolved to Closed for Apache Geode 1.11.0 RC4 release. > 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 > Affects Versions: 1.0.0-incubating, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.2.1, > 1.4.0, 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.9.0, 1.9.1, 1.10.0 > Reporter: Stephane Nicoll > Assignee: Kirk Lund > Priority: Major > Fix For: 1.11.0 > > Time Spent: 20h > Remaining Estimate: 0h > > {{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 (v8.3.4#803005)