lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Pendlebury (JIRA)" <>
Subject [jira] [Commented] (SOLR-2487) Do not include slf4j-jdk14 jar in WAR
Date Mon, 15 Aug 2011 00:57:27 GMT


Greg Pendlebury commented on SOLR-2487:

It would be great to have a skinny WAR available as a Maven artifact. At the moment there
is no way in Maven to have it exclude the jdk14 JAR short of rebuilding and rehosting the
WAR elsewhere. eg:

And to my knowledge at the moment, there is nothing like this available for v3.3.0

With a skinny WAR in Maven listing all the currently bundled dependencies the end result for
most users would be identical, since Maven will go get them all for you anyway. Then people
that don't want jdk14 can add this to their own project and they will get everything but that
single dependency:

> 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