[
https://issues.apache.org/jira/browse/TIKA-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135458#comment-15135458
]
Thamme Gowda N commented on TIKA-1851:
--------------------------------------
Shell script was the initial version we had for manual setup (we must have
deleted it from source control to avoid this ambiguity). The groovy script is
actually used in the build to automate the test setup.
We chose groovy over shell script because it makes the setup portable to
windows since it doesnt need tools like wget or curl.
I tried to include the groovy script in src/test/groovy first, that forced me
to setup groovy for the entire test goal of the project. But actually, the
script is part of build tools (i.e. maven plugins) and not part of tika's test
cases, so it was kept outside.
As always, open to any suggestions you will have.
> 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
>
>
> 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)
