[
https://issues.apache.org/jira/browse/TIKA-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264705#comment-17264705
]
Nick Burch commented on TIKA-3274:
----------------------------------
Two possible issues with the move spring to mind:
* It becomes harder for users to tell what possible metadata they might get
from Tika
* Code that references the parser-specific metadata properties, in the case of
the module being missing, go from "uses empty parser + gets no text" to
"runtime class not found exception"
> Tika 2.0.0 -- Move parser specific metadata out of tika-core to parser modules
> ------------------------------------------------------------------------------
>
> Key: TIKA-3274
> URL: https://issues.apache.org/jira/browse/TIKA-3274
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Major
>
> We should move parser specific metadata properties out of tika-core into the
> respective parser modules. This can wait until the 2.0.0-BETA release, IMHO.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
