On Thu, May 23, 2013 at 12:29 PM, Shawn Heisey <s...@elyograg.org> wrote:
> > For logs that are in test code itself, using sysout or syserr is probably > a good option. The Solr code that is being tested will (in most cases) > pull in a dependency on slf4j because Logger is ubiquitous. That's what I > was referring to. > > I'm not sure it has to forever. For example, in trunk we could decide to use jetty's logging class instead, so solr has no hard dependency on slf4j at all. If its in the classpath it would get used, but otherwise stuff just goes to System.err.println. Or solr could just use System.err.println, and if someone wants logging they can redirect it (e.g. http://projects.lidalia.org.uk/sysout-over-slf4j/ ). Lots of possibilities to remove logging jars!
