lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-2487) Do not include slf4j-jdk14 jar in WAR
Date Thu, 13 Oct 2011 20:05:12 GMT

    [ https://issues.apache.org/jira/browse/SOLR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126870#comment-13126870
] 

David Smiley commented on SOLR-2487:
------------------------------------

Hoss: right; the user could simply expand the .war themselves and then customize. I think
most webapp deployments would want some sort of customization, the most common of which is
logging but there are others. Perhaps a different build.xml option might deploy an expanded
WAR to the example jetty webapps dir--just an idea.  I admit my first comment on this issue
was "I like it Jan!" but there are so many things a user might do to customize the app that
I'm not sure if it's worthwhile to add build.xml targets for these things when there is no
telling what the user will need to customize. We can just make it easy for them to get going
on that customization and the first step is having an exploded deployment so they need not
expand a war file.  But that's not a big deal.
                
> Do not include slf4j-jdk14 jar in WAR
> -------------------------------------
>
>                 Key: SOLR-2487
>                 URL: https://issues.apache.org/jira/browse/SOLR-2487
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message