[
https://issues.apache.org/jira/browse/TIKA-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245861#comment-15245861
]
Tim Allison commented on TIKA-1950:
-----------------------------------
[~chrismattmann] and [~jotomo], will we break anything with rometools or
elsewhere in Tika if we exclude JDOM from ROME? It looks like this was a bit
of a challenge on TIKA-1435.
{noformat}
<dependency>
<groupId>com.rometools</groupId>
<artifactId>rome</artifactId>
<version>1.5.1</version>
<exclusions>
<exclusion>
<groupId>org.jdom</groupId>
<artifactId>jdom</artifactId>
</exclusion>
</exclusions>
</dependency>
{noformat}
> Clean up jdom version conflict
> ------------------------------
>
> Key: TIKA-1950
> URL: https://issues.apache.org/jira/browse/TIKA-1950
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Blocker
>
> Not sure best way to fix this. grib 4.5.5 uses jdom 2.0.4 and rometools uses
> 2.0.2. Both are now getting packed into tika-app. Should we exclude the
> earlier (jdom from rometools) and hope for the best?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
