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

Matthew Caruana Galizia commented on TIKA-2399:
-----------------------------------------------

Their response:

bq. I wouldn't mind if you forked the repo and published your own artifact, but 
please use a different group ID. 
bq. However, I am not a lawyer, and I don't know what, if any, legal 
ramifications there are for doing so. We (Unidata) do not own JJ2000. 
Furthermore, its license is uncertain. The Google Code page (1) claims "GNU 
Lesser GPL", but see also this issue (2).
bq. (1) https://code.google.com/archive/p/jj2000/
bq. (2) https://code.google.com/archive/p/jj2000/issues/3

> 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