[
https://issues.apache.org/jira/browse/SOLR-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494107#comment-13494107
]
Shawn Heisey commented on SOLR-3918:
------------------------------------
I've changed the issue title, because the latest version of the patch changes
how dist-war-excl-slf4j works, in addition to creating a new dist-excl-slf4j
target. The current build.xml leaves slf4j-api in the war, forcing you to
stick with that specific slf4j version. The patch removes all slf4j jars from
the war.
With my patch, someone who wants to change the slf4j binding can go to
slf4j.org and download the newest version. By putting the appropriate jars
into the proper location (lib/ext for the included jetty8), they can use the
-excl-slf4j war and have everything work. The required jars are slf4j-api,
jcl-over-slf4j, log4j-over-slf4j, the required binding jar. In the case of
log4j, you have to include the log4j jar itself as well.
> Change the way -excl-slf4j targets work
> ---------------------------------------
>
> Key: SOLR-3918
> URL: https://issues.apache.org/jira/browse/SOLR-3918
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 3.6.1, 4.0-BETA
> Reporter: Shawn Heisey
> Priority: Trivial
> Fix For: 3.6.2, 4.1, 5.0
>
> Attachments: SOLR-3918.patch, SOLR-3918.patch
>
>
> If you want to create an entire dist target but leave out slf4j bindings, you
> must currently use this:
> ant dist-solrj, dist-core, dist-test-framework, dist-contrib
> dist-war-excl-slf4j
> It would be better to have a single target. Attaching a patch against
> branch_4x for this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
