[
https://issues.apache.org/jira/browse/SOLR-16078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17817448#comment-17817448
]
James Dyer commented on SOLR-16078:
-----------------------------------
bq. Can we even get rid of jackson, or is it needed for JSON
I was thinking about this and was wondering if it would be possible, even if we
need a JSON parser, to have one solrj maven coordinate that only depended on
slf4j and nothing else. This would be for those applications running in a
JakartaEE-compliant environment. Then a separate artifact would pull in
Jackson for those users who do not have JSONB provided by the environment. I
do not know what it would take to accomplish this or if it is worth it.
> New solrj-core module
> ---------------------
>
> Key: SOLR-16078
> URL: https://issues.apache.org/jira/browse/SOLR-16078
> Project: Solr
> Issue Type: Sub-task
> Components: SolrJ
> Reporter: Jan Høydahl
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We should introduce a solrj-core module that is as slim as possible wrt
> dependencies.
> A user will then add solrj-core as well as any other solj-xx modules needed
> for their use.
> By marking it {{\@lucene.experimental}} we can change the API of this
> solrj-core during 9.x as we move stuff into other modules.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
