You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gregory Chanan (JIRA)" <ji...@apache.org> on 2015/06/11 01:33:00 UTC

[jira] [Resolved] (SOLR-7628) Investigate not using apacheds-all jar

     [ https://issues.apache.org/jira/browse/SOLR-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gregory Chanan resolved SOLR-7628.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Trunk
                   5.3

Thanks for taking a look mark and Steve.

Committed to 5.3 and trunk.

> Investigate not using apacheds-all jar
> --------------------------------------
>
>                 Key: SOLR-7628
>                 URL: https://issues.apache.org/jira/browse/SOLR-7628
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud, Tests
>    Affects Versions: 5.1, Trunk
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>             Fix For: 5.3, Trunk
>
>         Attachments: SOLR-7628.patch, SOLR-7628.patch, SOLR-7628v2.patch
>
>
> Over in SOLR-6915 it was reported that using the apacheds-all jar can be an issue because it has some conflicting classes:
> bq.  This apacheds-all jar seems troublesome - currently it has conflicting slf4j classes in it...
> See: https://issues.apache.org/jira/browse/SOLR-6915?focusedCommentId=14569870&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14569870



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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