Details
-
Type:
Rice Enhancement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: Unspecified Future Release
-
Component/s: Unknown
-
Labels:None
-
Rice Theme:Modularity
-
Priority Score:0
-
Impact if not Implemented:Development and Implementation of Rice will continue to be an all or none affair with pieces not needed/desired by an application having to be used. The work well underway on this, from the rice 2.0 release, will be incomplete.
-
Priority - KFS:No Priority
-
Priority - KC:No Priority
-
Priority - KS:No Priority
-
Priority - Rice:No Priority
Description
Finish modularity work on Rice impl
- KCB and KEN stuff should be easy to work with by moved into a KEN IMPL Module
- KNS package should be move up to KNS module
- Module service base should be move up from KRAD to the KRAD APP or Framework allows for core service and location out of rice impl
- Analyze KEW to see how it needs to be refactored to it's own module
- Analyze KIM as well
- Analyze the KRAD pieces and decide which needs to go where by package and classes
Attachments
Issue Links
- Trackbacks
-
![[Confluence: Kuali Rice]](/images/icons/generic_link_16.png "[Confluence: Kuali Rice]")
Kuali Rice Roadmap 2012
Draft !roadmap2012.png border=1! Timelines View a more detailed timeline and breakdown of Rice 2.2 features at KULRICE:Rice 2.2 Project Plan with Milestones and information on 2.3 Planning at KULRICE:Rice 2.3 Project Plan....
-
Remaining Modularity Work for Rice
Original Rice 2.0 Modularity Design and Analysis https://wiki.kuali.org/display/KULRICE/Rice2.0ModularityDesign To Dos # Finish work on Rice IMPL https://jira.kuali....