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

Tim Allison edited comment on TIKA-2399 at 7/5/17 2:30 PM:
-----------------------------------------------------------

[~mcaruanagalizia], would you be able to ask Unidata if they'd mind if I 
published jj2000 5.3 to maven central with my key?

My guess is that it would have to have the group id org.tallison like jmatio... 
  Or, if we do get their approval, would I be able to push under edu.ucar?


was (Author: talli...@mitre.org):
[~mcaruanagalizia], would you be able to ask Unidata if they'd mind if I 
published jj2000 5.3 to maven central with my key?

My guess is that it would have to have the group id org.tallison like jmatio...

> 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