Rationale
- remove extraneous stuff from the uPortal codebase.
- let other applications e.g., HyperContent use the groups and permissions APIs.
Notes
As a first cut, the project plan is to start in the current uPortal MAIN branch and make the GAP external dependencies injectible, that is, make it possible to use Spring to configure GAP. This includes making supporting services like locking and caching injectible. Once this is accomplished, the code would branch. That is, it would continue in uPortal MAIN for the time being and be spun off into its own cvs project, independent of uPortal.
Keith Stacks is currently working on some enhancements to PAGS and the permissions framework. These will probably have to be applied to both the MAIN and the independent GAP code.
When the spun-off GAP becomes available, we can decide if we want to rip out the code that remains in the uPortal packages or continue with an integrated GAP in uPortal 2.x.
The code seems to divide into the following areas, ultimately corresponding to individual jars:
- gap-common
- gap-groups-core
- gap-groups-services
- gap-permissions