Uploaded image for project: 'Hippo CMS'
  1. Hippo CMS
  2. CMS-11834

javax.activation jar appearing in CMS due to Tika upgrade

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 13.1.0, 11.2.12, 12.6.2
    • 13.1.1, 13.0.2, 11.2.13, 12.6.3, 13.2.0
    • None
    • None
    • Pulsar
    • Platform 205 - Content Beans 2

    Description

      In CMS-11726 Tika was upgraded to version 1.20

      This brings in a compile scope dependency to com.sun.activation:javax.activation:jar:1.2.0, so that ends up in the CMS war through hippo-repository-tika dependency.

      The jar contains the same classes as javax.activation:activation:jar:1.1.1 which used to be a compile scope dependency, see REPO-2153.

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

      This happens in archetype projects on 13.1.0, 12.6.2 and 11.2.12.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: