SOLR-17048: Update solrj dep on 'api' module #2029
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://issues.apache.org/jira/browse/SOLR-17048
Description
Solr 9.4 introduced a new 'api' module consumed by various other parts of Solr. The solrj module declared an 'implementation' dependency on this new module which worked for Solr's own build, but isn't actually sufficient to have the dependency picked up transitively in client apps, leading to a variety of ClassDefNotFound's.
Solution
This commit updates SolrJ's declaration of its 'api' dependency to list it as an "api" type dependency. This should prevent any client-side ClassDefNotFound problems related to these jar contents.
(Users of 9.4 can workaround this problem by adding an explicit dependency on solr-api in their apps, as in:
)
Tests
Existing tests continue to pass.
Checklist
Please review the following and check all that apply:
main
branch../gradlew check
.