[
https://issues.apache.org/jira/browse/SOLR-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084967#comment-13084967
]
Greg Pendlebury commented on SOLR-2487:
---------------------------------------
"At the moment there is no way in Maven to have it exclude the jdk14 JAR"...
Hmm, I shouldn't have stated an absolute like that. I eventually got a script
building today that dropped the WAR as a dependency, unpacked it to a '/solr'
context folder, then nuked the jdk14 JAR only, leaving the rest in place.
I'd still prefer a skinny WAR, since it would be a much cleaner build script,
and allow me to eliminate duplicate JARs on the classpath with greater ease. It
would also be more in line with the spirit of how Maven is intended to work...
but I have a workaround, and don't expect to world to conform to my wishes :)
> 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]
