|
David, is this ready to merge for 2.6?
This has been overtaken by the move to K1, as user is now in K1. So it seems the profile code will have to stay where it is for now.
Does this branch need to be refactored to make it a /kernel change, or should this issue be closed as Won't Fix?
It's trivial to move the SakaiPerson code out of the profile into its own module and update/create the poms. Since all components in SakaiPerson are something like common-xxx, it could be placed in a 'common' project for now. How long would it take to get into the kernel?
For those watching, I am progressing on this task shortly.
SakaiPerson will be moved into its own SVN space, removed from Profile, the POM's updated and the main .externals updated to reflect the changes. This was voted on in sakai-dev in February/March 2009 (http://www.nabble.com/Vote%3A-separate-SakaiPerson-API-from-Profile-tt21993631.html) 'common' project in main SVN contains SakaiPerson and related API's as of r59094
common added to main trunk build, tracked at
sakaiperson/common components removed from profile as of r59777
In common-1.0.x prior to release of common-1.0.0.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Task
Closed
Major
Move SakaiPerson service out of Profile
http://thread.gmane.org/gmane.comp.cms.sakai.devel/15406/focus=15628