[
https://issues.apache.org/jira/browse/TIKA-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379999#comment-17379999
]
Hudson commented on TIKA-3474:
------------------------------
UNSTABLE: Integrated in Jenkins build Tika ยป tika-main-jdk8 #277 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/277/])
TIKA-3474 -- handle 1.x container exception key (tallison:
[https://github.com/apache/tika/commit/020430f80665aba8ea2d4c7f7efcda8bd4dca34a])
* (edit)
tika-eval/tika-eval-app/src/main/java/org/apache/tika/eval/app/AbstractProfiler.java
TIKA-3474 -- handle 1.x container exception key (tallison:
[https://github.com/apache/tika/commit/c26e9c1572bdbcdb76d2ec87939882251a714125])
* (edit) tika-integration-tests/tika-pipes-solr-integration-tests/pom.xml
* (edit) tika-parent/pom.xml
* (edit) tika-integration-tests/tika-pipes-opensearch-integration-tests/pom.xml
> tika-eval in 2.x should handle the exception key from 1.x
> ---------------------------------------------------------
>
> Key: TIKA-3474
> URL: https://issues.apache.org/jira/browse/TIKA-3474
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Trivial
> Fix For: 2.0.0
>
>
> In Tika 2.x, we slightly changed the key to store stacktraces in the
> metadata. The tika-eval module is currently only looking for the 2.x version,
> which means that you can't run an evaluation between the 1.x and 2.x branches.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
