geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Blum (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEODE-1511) geode-core Maven POM File incorrectly includes the log4j-slf4j-impl bridge JAR
Date Mon, 06 Jun 2016 22:04:20 GMT
John Blum created GEODE-1511:
--------------------------------

             Summary: geode-core Maven POM File incorrectly includes the log4j-slf4j-impl
bridge JAR
                 Key: GEODE-1511
                 URL: https://issues.apache.org/jira/browse/GEODE-1511
             Project: Geode
          Issue Type: Bug
          Components: build
            Reporter: John Blum


The {{log4j-slf4j-impl} SLF4J bridge JAR is erroneously declared in the _Apache Geode_ {{geode-core}}
Maven POM file.  This can have unintended consequences in user Geode-based applications that
rely on different and/or several logging frameworks (e.g. SLF4J, logback, etc).

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.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message