[
https://issues.apache.org/jira/browse/TIKA-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056159#comment-16056159
]
Matthew Caruana Galizia commented on TIKA-2399:
-----------------------------------------------
Their response:
bq. Thanks for looking into this. Generating a POM that's compatible with Maven
Central isn't the problem; it's managing the PGP key that we'd need to sign our
artifacts. Our organization doesn't have a good way to store those secrets in a
secure way and then access them from a CI server. For more info, see:
https://github.com/Unidata/thredds/issues/819
bq. It's certainly not an insurmountable obstacle, but I'd have to get our
sysadmin (and possibly other interested developers) involved. As it's a problem
that I can't fix by myself, it's naturally tumbled down my priority list. I
definitely do want to solve it though.
> 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)
