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

Determine how best to deprecate ObjectUtils so that it's not referenced from non-legacy KRAD code

    Details

    • Type: Task
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4
    • Component/s: Analysis, JPA, Roadmap
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • Rice Module:
      KRAD
    • KRAD Feature Area:
      Utility
    • Sprint:
      Sprint 2, JPA Sprint 3
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Right now I have this class deprecated, but i haven't look at everywhere that it's called to determine what the replacements are. These should ultimately be documented properly. I suppose it's also possible that we don't want to deprecate all of ObjectUtils but just certain methods on it. But I really hate having a class called just "ObjectUtils". Certainly we can come up with a better name for such a thing.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              lfox Allen Fox (Inactive)
              Reporter:
              ewestfal Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified