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

[Backport 11.2] CMS does not manage commons-beanutils dependency

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Top
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.5
    • Component/s: None
    • Labels:
      None
    • Similar issues:
    • Sprint:
      Turing Sprint 160, Turing Sprint 161 (7/18-8/1), Turing Sprint 162
    • Processed by team:
      Turing

      Description

      commons-beanutilities are used In the CMS.

      The root/parent pom defines the version properties but does not have beanutils in the dependencyManagement section. Engine directly uses this version to depend on the beanutils. For 12.0 the version was bumped from 1.7.0 to 1.9.3

      The API also uses the beanutils but does not directly specify this dependency, it pulls it in via the Tika dependency. When using 1.9.3 the API build fails due to a incomatible map.

      -CMS-10800-

      When building the CMS API with beanutils 1.9.3 the following error is given:

      api/src/main/java/org/hippoecm/frontend/util/PluginConfigMapper.java:[36,60] error: incompatible types: Map<String,String> cannot be converted to Map<String,Object>

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                aschrijvers Ard Schrijvers
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: