Move SakaiLocaleResolver to kernel-util

Description

For the eventual, complete fix of SAK-19184, a spring LocaleResolver was added to metaobj. The location was chosen arbitrarily and a better choice would be kernel-util. There was some discussion on the kernel team list with positive feedback to this suggestion. This issue captures that initiative.

List thread: http://collab.sakaiproject.org/pipermail/cle-kernel-team/2011-September/000048.html

Environment

None

Test Plan

None

Activity

Show:

Matthew Jones April 24, 2018 at 10:33 AM

Bulk closing issues that have not been updated since 2015 and earlier. Please reopen if this is still an issue and you have new information or if this is a feature you'd like to still have consideration for.

Noah Botimer March 26, 2012 at 7:25 AM

There aren't many Spring dependencies at present, but there are some. Namely, some EhCache support and some resource loading. For now, I think this Resolver should land there and, if we decide to unspringify kernel-util later, move it with the others.

Aaron Zeckoski March 26, 2012 at 7:11 AM

Isn't kernel-util currently spring dependency free? If not, just go for it. If so, maybe we should make a util which is specific to spring dependencies (or write the code in a way that it will not blow up if the spring classes are missing - if that is even possible)

Sam Ottenhoff January 19, 2012 at 8:23 AM

CLE Team call: demoting from Critical for 2.9

Noah Botimer November 10, 2011 at 8:41 PM

I am happy to update the metaobj/OSP references to the resolver and test if the Java package changes. It seems that the best way to manage the migration would be to copy the class to kernel-util, then I can update metaobj/OSP so they aren't broken during transition.

Won't Fix

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created November 10, 2011 at 8:38 PM
Updated April 25, 2018 at 3:34 PM
Resolved April 24, 2018 at 10:33 AM