[ 
https://issues.apache.org/jira/browse/TIKA-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074825#comment-16074825
 ] 

Nick Burch commented on TIKA-2399:
----------------------------------

We can properly fix this in 2.x when we sort out how to have multiple parsers 
for a single format. Until we sort that on 2.x....

My suggestion would be for one of us to get the OK from Unidata to push the new 
build to central on their behalf, and GPG sign it with our Apache key. That'll 
fix it for the latest release, and subsequent ones we can either help again or 
they might've fixed their key storage to do it themselves

For 1.16 I think whatever warning makes most sense, unless someone can be very 
quick at getting the OK + Maven Central third party upload done!

> Version conflict with non-ASL jai-imageio-jpeg2000 and edu.ucar jj2000
> ----------------------------------------------------------------------
>
>                 Key: TIKA-2399
>                 URL: https://issues.apache.org/jira/browse/TIKA-2399
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.15
>            Reporter: Tim Allison
>
> For users who want to extract jp2000 from PDFs for inline-image OCR, they 
> have to add non- ASL 2.0 compatible:
> {noformat}
> <dependency>
>     <groupId>com.github.jai-imageio</groupId>
>     <artifactId>jai-imageio-jpeg2000</artifactId>
>     <version>1.3.0</version>
>   </dependency>
> {noformat}
> However, this creates a conflict with GRIB's jj2000:
> {noformat}
>    <dependency>
>       <groupId>edu.ucar</groupId>
>       <artifactId>jj2000</artifactId>
>       <version>5.2</version>
>     </dependency> 
> {noformat}
> [~mcaruanagalizia] (I'm guessing?) identified this conflict 
> [here|https://github.com/ICIJ/extract/blob/master/pom.xml] and fixes it by 
> upgrading jj2000 to 5.3.  However, that doesn't exist in maven central, but 
> only in [Boundless|http://example.com].
> What do we do?
> # We could exclude the jj2000 dependency from GRIB, and that functionality 
> won't work for GRIB folks
> # We could add a warning if we see {{jai-imageio-jpeg2000}} is on the 
> classpath to instruct users to exclude jj2000.
> # Other options?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to