[
https://issues.apache.org/jira/browse/BLUR-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789976#comment-13789976
]
Vikrant Navalgund commented on BLUR-228:
----------------------------------------
Hello Rahul,
I tried to simulate this:
(1) I created some dummy maven projects with different versions of slf4j-api
and slf4j-log4j12.
(2) As long as I(client) had a matching slf4j-api-<ver-xxx> and
slf4j-log4j12-<ver-xxx>, I had no issues.
Within Eclipse IDE:
(1) With the same above setting, if I(client) make sure that I have a matching
slf4j-api-<ver-xxx> and slf4j-log4j12-<ver-xxx>, I had no problem. It did not
matter even if I pulled Zookeeper which in turn pulls in its dependency some
other version of slf4j.
Also, the SLF4J site states that it should not be a problem:
http://www.slf4j.org/codes.html#version_mismatch
Please let me know what issues you are envisioning and any problems that you
came across, so that we can close it.
Regards,
Vikrant
> Multiple SLF4J bindings
> -----------------------
>
> Key: BLUR-228
> URL: https://issues.apache.org/jira/browse/BLUR-228
> Project: Apache Blur
> Issue Type: Improvement
> Components: Blur, Blur Console
> Affects Versions: 0.2.0, 0.3.0
> Reporter: Rahul Challapalli
> Priority: Trivial
> Fix For: 0.3.0
>
>
> Copying Aaron's comments from email :
> I'm not sure how we should go about resolving this issue. In blur-util
> slf4j is on 1.6.1 (because ZooKeeper has it as a dependency) and it's
> appears that Hadoop 1.2.1 is still on 1.4.3 of slf4j. I know that the
> normal java way to resolve such issues is will different class loaders or
> with OSGI but that seems like over kill. Thoughts?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
