lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Updated) (JIRA) <>
Subject [jira] [Updated] (SOLR-2487) Do not include slf4j-jdk14 jar in WAR
Date Mon, 10 Oct 2011 20:40:29 GMT


Jan Høydahl updated SOLR-2487:

    Attachment: SOLR-2487.patch

This patch attempts a solution which hopefully solves all needs. It adds a new ant target
"dist-war-minimal" which creates a minimal Solr WAR Distribution file, without slf4j jars,
except for the slf4j-api itself.

The target is not included in the "dist" task, so the minimal war will not be packaged redundantly.
However, being an explicit target it is more easily understood and discoverable than a build
parameter. Users packaging the war using this target must supply the relevant slf4j jars elsewhere
on their classpath.

This minimal war could be a candidate for uploading to maven.
> 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
>         Attachments: SOLR-2487.patch
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


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

View raw message