[GEODE-1511] geode-core Maven POM File incorrectly includes the log4j-slf4j-impl bridge JAR

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.0.0-incubating
• Component/s: build
• Sprint: 1.0.0-incubating.M3
• Assignee: Unassigned
• Reporter: John Blum
• Created: 06/Jun/16 22:03
• Updated: 25/Oct/16 07:17
• Resolved: 21/Sep/16 16:09

Description

The log4j-slf4j-impl SLF4J bridge JAR has been erroneously declared in the Apache Geode geode-core Maven POM file.

The inclusion of this declaration can have unintended consequences in a user's Geode-based application that might potentially rely on different and/or several logging frameworks (e.g. SLF4J, logback, etc), depending on the transitive dependencies of the application.

Geode should not be including SLF4J bridge JARs in the applications CLASSPATH at runtime or otherwise.

Additionally, the Geode POM file includes references to test dependencies that should be removed, specifically...

junit
asm
system-rules
mockito-core
geode-junit
hadoop-auth
awaitility
catch-exception
cglib
powermock-module-junit4
jmock-junit4
catch-throwable
tempus-fugit
commons-collections
JUnitParams
bcel
assertj-core
powermock-core
jedis
jmock-legacy
powermock-api-mockito
hamcrest-all
commons-configuration
spymemcached
multithreadedtc
derby

The more dependencies you include, the greater chance for conflict an application developer may have when integrating with Apache Geode. The distributed/deployed (to Maven Central) is less about "building" the Apache Geode project and more about running an application built with Apache Geode.

Issue Links

• is related to: GEODE-1811 Runtime dependencies listed as optional in build.gradle are not optional in the pom