Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: Modularity
    • Security Level: Public (Public: Anyone can view)
    • Labels:
      None
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      There are many changes that need to happen to our utility classes for modularity:

      1) our utility classes need to be actual utility classes (static methods, private ctors, final classes, usually deterministic method calls, does not use spring services)
      2) we need to get rid of the duplicate methods that exist in multiple library classes or rice utility classes (isEqual(), jotNode)
      3) we need to delete junk that isn't used
      4) we need to create meaningful apis which might mean breaking up utility classes
      5) we meed to differentiate between utilities that are internal to rice versus ones we want client apps to use
      6) everything that isn't a utility method in a utility class should be moved

        Attachments

          Activity

          Error rendering 'com.atlassian.jira.jira-view-issue-plugin:activitymodule'. Please contact your JIRA administrators.

            People

            • Assignee:
              tschneeb Travis Schneeberger
              Reporter:
              tschneeb Travis Schneeberger
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: