[
https://issues.apache.org/jira/browse/TIKA-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209034#comment-15209034
]
Tim Allison commented on TIKA-1855:
-----------------------------------
Alright, the build is back.
I moved everything out of tika-parsers that I could, but I couldn't get rid of
it entirely. At this point, it is a convenient way to gather all the
parser-modules so that tika-app and tika-server can rely on it without having
to specify all the same individual tika-parser-x-modules. I'm sure there is a
way to do this with tika-parser-modules instead, but I couldn't figure out how
to do it.
[~bobpaulin], any recommendations? Can we actually get rid of tika-parsers? I
give you the honor. :)
I started to cleanup some of the tests to rely more on TikaTest's getXML and
was able to get rid of quite a bit of code. More work remains across all the
tests...
I put nearly all test documents (from tika-parsers and tika-server) into
tika-test-resources.
We could probably move files from tika-app there as well...
> TIka 2.0 - Move shared test-code back to tika-core and distribute test files
> to parser modules
> ----------------------------------------------------------------------------------------------
>
> Key: TIKA-1855
> URL: https://issues.apache.org/jira/browse/TIKA-1855
> Project: Tika
> Issue Type: Sub-task
> Reporter: Tim Allison
> Assignee: Tim Allison
>
> Undo TIKA-1851, and divide test docs to appropriate parser modules.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
