Well, that's getting more exciting... java.io.IOException: No space left on device at java.io.FileOutputStream.write(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:290) at org.apache.tika.TestRereadableInputStream.createTestFile(TestRereadableInputStream.java:105) at org.apache.tika.TestRereadableInputStream.createTestInputStream(TestRereadableInputStream.java:97) at org.apache.tika.TestRereadableInputStream.test(TestRereadableInputStream.java:42)
-----Original Message----- From: Hudson (JIRA) [mailto:j...@apache.org] Sent: Friday, July 7, 2017 12:32 PM To: dev@tika.apache.org Subject: [jira] [Commented] (TIKA-2399) Version conflict with non-ASL jai-imageio-jpeg2000 and edu.ucar jj2000 [ https://issues.apache.org/jira/browse/TIKA-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078352#comment-16078352 ] Hudson commented on TIKA-2399: ------------------------------ ABORTED: Integrated in Jenkins build Tika-trunk #1320 (See [https://builds.apache.org/job/Tika-trunk/1320/]) TIKA-2399 exclude jj2000 because of potential license problems with ASL (tallison: [https://github.com/apache/tika/commit/f776c2479f8e7ab1134669fad1e25fd38bd82466]) * (edit) tika-parsers/pom.xml * (edit) CHANGES.txt > 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 > Assignee: Tim Allison > Fix For: 1.16 > > > 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)