[
https://issues.apache.org/jira/browse/TIKA-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141793#comment-15141793
]
Bob Paulin commented on TIKA-1851:
----------------------------------
[[email protected]] You are correct. If they are in the test directory they
would not be packaged with the main jars. They would only be a part of the
test jars if we were creating them for the individual modules, which we are
not. I think the bigger issue is all the documents that are shared in the
individual tests. So there's the choice of duplicating them in each module,
keeping them in tika-test-resources, or refactoring tests to not require the
shared documents. In the case of the later perhaps integration tests requiring
different combinations of documents would be better served in tika-app. There
are risks to moving these things around. I am curious what [~lewismc] is
seeing in Lucene. I think the purest in me says unit tests should only involve
code/documents specific to the module, but the pragmatist says it's risky to
change these things. To manage the pain it would be good hear what's up with
Lucene.
> Tika 2.0 - Move test resources from core to test-resources
> ----------------------------------------------------------
>
> Key: TIKA-1851
> URL: https://issues.apache.org/jira/browse/TIKA-1851
> Project: Tika
> Issue Type: Sub-task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Trivial
> Fix For: 2.0
>
> Attachments: tika_2x_test_files_and_modules.xlsx
>
>
> Let's try to move resources that are used for testing to the test-resources
> module if possible: MockParser, DummyParser, TikaTest and the unit tests for
> MockParser. That should also allow us to drop the test-jar goal in
> tika-core. Anything else?
> Haven't actually tried this yet; there may be surprises.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
