[
https://issues.apache.org/jira/browse/SOLR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084928#comment-13084928
]
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:
http://www.jarvana.com/jarvana/browse/org/dspace/dependencies/solr/dspace-solr-webapp/1.4.1.0/
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:
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-jdk</artifactId>
<version>1.6.1</version>
<scope>provided</scope>
</dependency>
> 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
>
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
