You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2019/09/24 16:19:00 UTC
[jira] [Commented] (GEODE-6964) Log4j configuration can be altered
by adding geode-core to the classpath
[ https://issues.apache.org/jira/browse/GEODE-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936960#comment-16936960 ]
ASF subversion and git services commented on GEODE-6964:
--------------------------------------------------------
Commit efc2362d2bae0877a427ce2c29beae94118d6567 in geode's branch refs/heads/develop from Kirk Lund
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=efc2362 ]
GEODE-6964: Move geode log4j core classes to geode-log4j
Introduce new Logging and Alerting SPIs. Extract all log4j-core code to
geode-log4j module.
The geode-core module no longer contains log4j2.xml and no longer has a
dependency on log4j-core.
All code that uses log4j-core has moved to the new module geode-log4j.
The log4j2.xml for Geode now lives in geode-log4j as well. These
changes ensure that users have better control over logging including
which backend to use. This should improve user experience when using
Spring Boot.
Co-authored-by: Mark Hanson <mh...@pivotal.io>
> 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
> 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)