I usually build solr using 'ant test dist' to run tests and build the
.war and other jars, in particular the dataimporthandler. Having an
alternate ant option to build without the binding would work for me.
If/when I get around to changing logging mechanisms, I wouldn't be able
to use the binary distribution, but with 3.1 I am already including
selected patches from branch_3x and building it myself.
I can see that there is a lot of resistance to just removing the binding
entirely. I think that's a better option, but I know it's important to
take care of the complete novices and their initial experience with the
software.
[ ] 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
[X] 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!
On 5/18/2011 3:31 PM, Jan Høydahl wrote:
> Hi,
>
> If you've setup your Tomcat with log4j logging, and want to add Solr,
within the same logging config, you need to:
> #1. Remove slf4j-jdk14-1.6.1.jar from solr.war (unpack, remove, repack)
> #2. Download slf4j-log4j12-1.6.1.jar (from slf4j.org) and place it
in e.g. tomcat/shared/lib
>
> If solr.war shipped without a pre-packaged binding, you could skip
#1. The binding jar you deploy to appserver lib would also take effect
for any other webapp using slf4j deployed to the same app-server.
>
> An alternative to manually repackage solr.war as in #1, is Hoss'
suggestion in SOLR-2487 of a new ANT option to build Solr artifacts
without the JUL binding.
