...
See the JIRA issue tracker for Groups and Permissions for a description of the tasks for each component.
Collaboration with related APIs
Notes
The plan is to start by creating a common service layer, wired together using Spring, with the individual services available as Spring-managed beans. Next publish the public Groups and Permissions api's, so uPortal 3 developers have something to write to. Then we can move on to migrating the services themselves. Finally, we could back-port the GAP code to uPortal 2.6, where it could be available as an optional configuration. The advantage would be that you could use Spring to do service configuration and have be able to plug in external implementations of common services.
...