[KULRICE-4881] Clean up utility classes Created: 07/Jan/11  Updated: 23/Feb/12  Resolved: 10/May/11

Status: Closed
Project: Kuali Rice Development
Component/s: Modularity
Affects Version/s: None
Fix Version/s: 2.0
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Major
Reporter: Travis Schneeberger Assignee: Travis Schneeberger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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



 Comments   
Comment by Travis Schneeberger [ 10/May/11 ]

resolving for now.... will create new jiras for additional work.

Comment by Jessica Coltrin (Inactive) [ 23/Feb/12 ]

Closing since these items are now in the release notes.

Generated at Sat Oct 24 13:11:36 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.