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 > > >
