Uploaded image for project: '[Read Only] - Hippo Repository'
  1. [Read Only] - Hippo Repository
  2. REPO-2153

activation jar appearing in CMS due to Tika upgrade

    XMLWordPrintable

Details

    • Platform 195 - Hardening 1

    Description

      In REPO-2146 Tika dependency was upgraded to 1.9.1

      https://issues.apache.org/jira/browse/TIKA-2660 brings in a compile dependency to javax activation 1.1.1 jar, so then it ends up in the CMS war through hippo-repository-tika dependency.

      Having activation.jar in CMS.war is unwanted; can lead to class loader problems since it is normally is present in container installation, say Tomcat /lib.

      This happens in archetype projects on 12.6.0, 12.5.1, 11.2.10 and 10.2.14. Probably also in 13.

      Attachments

        Issue Links

          is a result of

          Task - A task that needs to be done. REPO-2146 Update Tika and PDFBox to latest supported version

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed
          relates to

          Task - A task that needs to be done. CMS-11262 Add javax activation dependency to project pom

          • Normal - Normal priority, tasks to be done before next intermediate release
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. CMS-11834 javax.activation jar appearing in CMS due to Tika upgrade

          • Blocker - Blocks further development for most developers or blocks intermediate release
          • Closed

          Activity

            People

              Unassigned Unassigned
              jhoffman Jeroen Hoffman
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: