[
https://issues.apache.org/jira/browse/TIKA-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208296#comment-15208296
]
Tim Allison commented on TIKA-1285:
-----------------------------------
Y, I've been thinking about this, too. I wonder if we could shade/relocate
PDFBox 1.8 ourselves, or perhaps ask our PDFBox colleagues to distribute a
shaded+relocated 1.8 (o.a.pdfbox18...) that we could call with PDFParser18 or
something.
If we can get the shading to work, this would be a perfect use case for the
back-off composite parser (still in planning stages)-- if there's an exception
with PDFBox 2.0.0, retry with PDFBox 1.8.x.
> Upgrade to PDFBox 2.0.0 when available
> --------------------------------------
>
> Key: TIKA-1285
> URL: https://issues.apache.org/jira/browse/TIKA-1285
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Affects Versions: 1.6
> Reporter: Jeremy Anderson
> Fix For: 1.13
>
> Attachments: TIKA-1285.patch, TIKA-1285_rev1641423.patch,
> TIKA-1285v3.patch, pdfbox_reports_2_0_0_20150709.zip,
> testPDF_childAttachments.pdf
>
>
> This issue is to track fixes required when upgrading the PDFbox dependency to
> 2.0.0 Final once it's available, and using PDFBox's daily build before then.
> See TIKA-1268 comment.
> Relates to PDFBOX-1893
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
