+1
Great progress indeed!!
On Tuesday, April 12, 2016, Anthony Baker wrote:
> See [1]. Only trouble I had was excluding log4j-slf4j-impl. Without that
> I hit a startup error complaining about logging conflicts.
>
> compile ('org.apache.geode:geode-core:1.0.0-incubating.M2') {
> exclude m
See [1]. Only trouble I had was excluding log4j-slf4j-impl. Without that I
hit a startup error complaining about logging conflicts.
compile ('org.apache.geode:geode-core:1.0.0-incubating.M2') {
exclude module: 'log4j-slf4j-impl'
}
It would be nice to remove both slf4j-api and log4j-slf4j
++1 - Congrats!!
We should also try with other frameworks, such as Spring(boot) to see if
it's now easier to integrate without going into conflicts.
On Tue, Apr 12, 2016 at 3:58 PM John Blum wrote:
> +1 This is a huge improvement; nice work! Not sure about all them, but I
> seem to remember t
+1 This is a huge improvement; nice work! Not sure about all them, but I
seem to remember the log4j extension JARs (e.g. log4j-jcl, log4j-jul and
log4j-slf4j-impl) definitely being feature specific. I think it was *Gfsh*
that used JUL and embedded Tomcat (at the time) that used SLF4J.
findbugs-a
The changes for GEODE-27 [1] improved our pom dependencies immensely. I wrote
up a quick sample app [2] to test out the maven dependencies. Here’s what the
sample app pulls in just based on geode-core:
Anthony-Baker-MacBook-Pro:geode-hello-world abaker$ ls -1
build/install/geode-hello-world/l
