Off the top of my head, 1 way would be to do the following (I think :-)...
compile
("org.springframework.data:spring-data-gemfire:1.7.0.APACHE-GEODE-EA-SNAPSHOT")
{
exclude module : 'org.apache.geode:gemfire-core'
}
compile ("org.apache.geode:gemfire-core:1.0.0-incubating-SNAPSHOT") {
exclude module : 'org.apache.logging.log4j:log4j-slf4j-impl'
}
So, for the SDG dependency, you shouldn't need to exclude any of the other
Geode deps (a.k.a. modules, e.g. gemfire-jgroups, etc because they don't
declare
<https://repository.apache.org/content/repositories/snapshots/org/apache/geode/gemfire-jgroups/1.0.0-incubating-SNAPSHOT/gemfire-jgroups-1.0.0-incubating-20150715.080727-26.pom>
[0]
a SLF4J dependency binding), just gemfire-core, which is the module that pulls
in the SLF4J binding
<https://repository.apache.org/content/repositories/snapshots/org/apache/geode/gemfire-core/1.0.0-incubating-SNAPSHOT/gemfire-core-1.0.0-incubating-20150715.080719-27.pom>(s)
[1]. Then you "explicitly" declare gemfire-core dependency (because you
need it) with the SLF4J binding exclusion.
Give that a try.
Cheers,
John
[0] -
https://repository.apache.org/content/repositories/snapshots/org/apache/geode/gemfire-jgroups/1.0.0-incubating-SNAPSHOT/gemfire-jgroups-1.0.0-incubating-20150715.080727-26.pom
[1] -
https://repository.apache.org/content/repositories/snapshots/org/apache/geode/gemfire-core/1.0.0-incubating-SNAPSHOT/gemfire-core-1.0.0-incubating-20150715.080719-27.pom
On Tue, Jul 14, 2015 at 10:45 PM, João Peixoto <[email protected]>
wrote:
> When trying to run different components I'm getting the warning message:
>
> SLF4J: Class path contains multiple SLF4J bindings.
>
> Even if I try to exclude them, say:
>
> compile
> ("org.springframework.data:spring-data-gemfire:1.7.0.APACHE-GEODE-EA-SNAPSHOT")
> {
> exclude module : 'spring-boot-starter-logging'
> exclude module : "org.apache.logging.log4j:log4j-slf4j-impl:2.1"
> }
>
> It does nothing. Doing "gradle dependencies" tells me it is geode pulling
> those bindings.
>
> This causes ALL logging to be in debug level, which is way too noisy.
> Any idea how to circumvent this?
>
> Joao Peixoto
>
--
-John
503-504-8657
john.blum10101 (skype)
