[
https://issues.apache.org/jira/browse/SOLR-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861725#comment-16861725
]
Mark Miller commented on SOLR-13437:
------------------------------------
I think it's not anymore? It might be that whatever we use in spatial4j doesn't
touch the code that uses noggit (obviously nothing in tests appear to touch
it). Unless someone reports a problem, I'm not too concerned, just thought I'd
mentioned it because I noticed while working on the gradle build. I'll have to
probe a little more and maybe get some input from [~dsmiley] to decide what to
do there - include it for the spatial module or make an exception for it.
> fork noggit code to Solr
> ------------------------
>
> Key: SOLR-13437
> URL: https://issues.apache.org/jira/browse/SOLR-13437
> Project: Solr
> Issue Type: Task
> Components: SolrJ
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> We rely on noggit for all our JSON encoding/decoding needs.The main project
> is not actively maintained . We cannot easily switch to another parser
> because it may cause backward incompatibility and we have advertised the
> ability to use flexible JSON and we also use noggit internally in many classes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
