lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (SOLR-2487) Do not include slf4j-jdk14 jar in WAR
Date Tue, 21 Jun 2011 16:19:47 GMT


Hoss Man commented on SOLR-2487:

"supported" is always a vague term, but like with every other ant property in our build file,
the default is the "supported" one that we test, and if you override a property when building
from source that's a customization and we won't promise that it will always work.

it's no different then if they override the "javac.source" property, or "build.encoding",

> Do not include slf4j-jdk14 jar in WAR
> -------------------------------------
>                 Key: SOLR-2487
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: Build
>    Affects Versions: 3.2, 4.0
>            Reporter: Jan H√łydahl
>              Labels: logging, slf4j
> I know we've intentionally bundled slf4j-jdk14-1.5.5.jar in the war to help newbies get
up and running. But I find myself re-packaging the war for every customer when adapting to
their choice of logger framework, which is counter-productive.
> It would be sufficient to have the jdk-logging binding in example/lib to let the example
and tutorial still work OOTB but as soon as you deploy solr.war to production you're forced
to explicitly decide what logging to use.

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message