put a log4j.properties as a resource or beside the test in svn. On Fri, May 17, 2013 at 7:18 AM, Shai Erera <[email protected]> wrote: > Hi > > I noticed lucene/replicator tests output this warning: > > [junit4:junit4] 2> SLF4J: Failed to load class > "org.slf4j.impl.StaticLoggerBinder". > [junit4:junit4] 2> SLF4J: Defaulting to no-operation (NOP) logger > implementation > [junit4:junit4] 2> SLF4J: See > http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > > In the webpage mentioned in the warning it's said that's because the > classpath doesn't have one of slf4j bindings, e.g. slf4j-jdk. Replicator > itself doesn't use logger at all, but InfoStream, so this must be something > that comes from the Jetty libs. > > Is it a new thing? Do Solr tests output same warnings? Should we care about > it? > > What's weird is that this is printed only when I run w/ > -Dtestscase=HttpReplicatorTest, but not if I run 'ant test'. Maybe that's > related to the debug info test-framework outputs if a single test is run vs > all? > > Shai
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
