Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-8615

Wrong commons-collections version when depending on rice-kim-api

    Details

    • Type: Bug Fix
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0-m4, 2.2
    • Fix Version/s: 2.1.3
    • Component/s: Development
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KIM
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      If a project depends on rice-kim-api, an institutional kim impl for example, an older dependency of commons-collections (3.1) will be resolved by maven. This causes compilation errors. The kim api code uses commons-collections classes, but it doesn't declare a dependency (it gets the older version from db-ojb). While the proper version is declared in the dependencyManagement of the Rice parent, this doesn't seem to affect external projects. Adding commons-collections as an explicit dependency seems warranted and will resolve the problem for external projects.

        Attachments

          Activity

          Hide
          gilesp Peter Giles (Inactive) added a comment -

          Corey, can you check if this issue affects 2.1.3 as well? If so we'll fix it and merge it over to trunk.

          Show
          gilesp Peter Giles (Inactive) added a comment - Corey, can you check if this issue affects 2.1.3 as well? If so we'll fix it and merge it over to trunk.
          Hide
          cpedersen Corey Pedersen (Inactive) added a comment -

          Currently if your project just has a dependency on the rice-kim-api module, maven will load commons-collections:3.1. If you include another module with commons-collections dependency defined (such as rice-ksb-api) maven will load common-collections:3.2.1. To utilize a consistant and common current version in rice-kim-api, a dependency should be added which will inherit it's version number from the rice parent.

          Show
          cpedersen Corey Pedersen (Inactive) added a comment - Currently if your project just has a dependency on the rice-kim-api module, maven will load commons-collections:3.1. If you include another module with commons-collections dependency defined (such as rice-ksb-api) maven will load common-collections:3.2.1. To utilize a consistant and common current version in rice-kim-api, a dependency should be added which will inherit it's version number from the rice parent.
          Hide
          cpedersen Corey Pedersen (Inactive) added a comment -

          Peter: This IS true in 2.1.3 and the change will be committed there.

          Show
          cpedersen Corey Pedersen (Inactive) added a comment - Peter: This IS true in 2.1.3 and the change will be committed there.
          Hide
          cpedersen Corey Pedersen (Inactive) added a comment -

          Committed revision 36174.

          Show
          cpedersen Corey Pedersen (Inactive) added a comment - Committed revision 36174.

            People

            • Assignee:
              cpedersen Corey Pedersen (Inactive)
              Reporter:
              sgibson Scott Gibson (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: