[
https://issues.apache.org/jira/browse/SOLR-7628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580605#comment-14580605
]
Mark Miller commented on SOLR-7628:
-----------------------------------
bq. There are quite a number of dependencies I had to add, but it seems worth
it to not have conflicting jars on the classpath
It also keeps us honest about having all the licenses and NOTICES for all the
code we ship - including the test-framework modules.
bq. Given that we only use the MiniKDC for tests, we should find any places
where this could be in an issue automatically in the future. This seems like a
reasonable approach over maintaining more dependencies.
I took the same approach with the Hadoop test dependencies. Sometimes on an
update you have to add a dependency that was not tickled before, but again, it
keeps us honest about tracking and attributing that.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
