[ ] I always use the JDK logging as bundled in solr.war, that's perfect [ ] I sometimes use log4j or another framework and am happy with re-packaging solr.war [X] Give me solr.war WITHOUT an slf4j logger binding, so I can choose at deploy time [ ] Let me choose whether to bundle a binding or not at build time, using an ANT option [ ] What's wrong with the "solr/example" Jetty? I never run Solr elsewhere! [ ] What? Solr can do logging? How cool!
Actually, more specifically, the build distribution could build a war done either way, but I'd most like to see the war file WITHOUT a binding be deployed to Maven. As it stands, I've done both 1) deploy solr without logging to Maven and use it, and 2) deploy solr with jdk logging to Maven, then have a Maven build repackage to remove jdk and use my preferred implementation (logback). I've only done 2) at the preference of others who don't want me to deploy a "modified" war to our Maven repo. Stephen Duncan Jr www.stephenduncanjr.com
