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?
Aaron On Mon, Sep 16, 2013 at 6:12 AM, Aaron McCurry <[email protected]> wrote: > I don't think it's something that should stop the release. We should > definitely add an issue in jira and resolve for 0.3.0. > > Thanks > Aaron > > > > Sent from my iPhone > > On Sep 16, 2013, at 1:15 AM, rahul challapalli <[email protected]> > wrote: > > > How else can we do it, other than selectively excluding this jar while > > loading jars from hadoop lib. > > Should we not fix it as part of the Release Candidate? > > > > > > On Sun, Sep 15, 2013 at 7:26 PM, Aaron McCurry <[email protected]> > wrote: > > > >> Yeah I've seen it before. Perhaps we should not include slf4j in the > Blur > >> lib directory and just rely on Hadoop to bring in slf4j. Thoughts? > >> > >> Aaron > >> > >> > >> On Sun, Sep 15, 2013 at 10:15 PM, rahul challapalli < > >> [email protected]> wrote: > >> > >>> Does anyone else get the below warning when starting the shell? My > local > >>> hadoop installation already has one. > >>> > >>> SLF4J: Class path contains multiple SLF4J bindings. > >>> SLF4J: Found binding in > >> > [jar:file:/Users/rchallapalli/Blur-Testing/apache-blur-0.2.0-incubating-bin/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] > >>> SLF4J: Found binding in > >> > [jar:file:/usr/local/Cellar/hadoop/1.1.2/libexec/lib/slf4j-log4j12-1.4.3.jar!/org/slf4j/impl/StaticLoggerBinder.class] > >>> > >>> - Rahul > >> >
