[
https://issues.apache.org/jira/browse/GEODE-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894314#comment-16894314
]
Stephane Nicoll commented on GEODE-6964:
----------------------------------------
Thanks, this is helpful. I think there are a few things that can be done to
help users:
* Make the {{log4j-core}} dependency optional so that you don't have to exclude
it. Of course, this may have several side effects I am not aware of but it
feels to me that if the code is optional, so should be the dependency
* Remove the logging configuration (for instance, by moving it to a location
that is less likely to be used for API usage). If a user decides to use log4j
as their logging infrastructure, the current file can be used depending on
classpath order.
> 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)
