Uploaded image for project: 'Alfresco'
  1. Alfresco
  2. ALF-21062

Contribute PDFBox changes to Apache PDFBox, to avoid having a custom Alfresco version

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Unprioritized
    • Resolution: Fixed
    • Affects Version/s: 4.2 Enterprise, 5.0
    • Fix Version/s: None
    • Security Level: external (External user)
    • Labels:
      None
    • Security Severity:
      None

      Description

      For some time now, Alfresco has been shipping patched versions of Apache PDFBox, with a handful of fixes in it. This list of fixes looks fairly stable - they're almost identical on 4.1.4 for PDFBox 1.7.0 to 4.2.2 for PDFBox 1.8.2 to community head for PDFBox 1.8.4

      Because PDFBox in Alfresco is a custom patched version, it makes upgrading harder, both for customers and Alfresco. With Apache Tika 1.6 due out in a few days, which needs a newer PDFBox, that'll be an issue once again. (It's an issue for anyone trying to upgrade to the release candidate to check today)

      It would seem best for everyone if patches to things like Apache POI, Tika and PDFBox could be contributed upstream, to avoid the need for Alfresco patched versions in the long term. (Short term for bug fixes is one thing, a year seems another!).

      (The current set of PDFBox patches are the main ones needed for this - the POI patches have already been applied upstream, but confusingly community head has 3.10 final but a patch file for the previous 3.9 changes...)

        Attachments

          Issue Links

            Activity

            Hide
            resplin Richard Esplin added a comment -

            This issue sat open for so long that I suspect it doesn't apply anymore. I think we upgraded PDFBox in 5.0, we contributed many of our patches upstream, and we have been separating our patches from the application code so it is easier to upgrade these libraries in the future.

            I'll close this as fixed.

            We are looking at upgrading PDFBox in REPO-1315, so we linked the issues so that we can be aware of the suggestion.

            Thanks again Nick.

            Show
            resplin Richard Esplin added a comment - This issue sat open for so long that I suspect it doesn't apply anymore. I think we upgraded PDFBox in 5.0, we contributed many of our patches upstream, and we have been separating our patches from the application code so it is easier to upgrade these libraries in the future. I'll close this as fixed. We are looking at upgrading PDFBox in REPO-1315 , so we linked the issues so that we can be aware of the suggestion. Thanks again Nick.

              People

              • Assignee:
                closedissues Closed Issues
                Reporter:
                nburch Nick Burch
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: