[
https://issues.apache.org/jira/browse/TIKA-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14011287#comment-14011287
]
Nick Burch commented on TIKA-1311:
----------------------------------
If we put it into core, we'd need to add another dependency (to GSON) which
isn't ideal, so we might want to run the plan past the dev list first to see
what people think (core tends to try to have a very minimal set of deps, unlike
the other modules)
Package wise, org.apache.tika.metadata.json is what I'd lean towards, otherwise
utils.json
> Centralize JSON handling of Metadata
> ------------------------------------
>
> Key: TIKA-1311
> URL: https://issues.apache.org/jira/browse/TIKA-1311
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> When json was initially added to TIKA CLI (TIKA-213), there was a
> recommendation to centralize JSON handling of Metadata, potentially putting
> it in core. On a recent bug fix (TIKA-1291), the same recommendation was
> repeated especially noting that we now handle JSON/Metadata differently in
> CLI and server.
> Let's centralize JSON handling in core and use GSON. We should add a
> serializer and a deserializer so that users don't have to reinvent that wheel.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
