Hi Eric,
The initial work involved is:
1. doing a maven build process that creates .jars for the
various sub-projects that we want to divide GaP into;
2. making the jars available to uPortal3;
3. removing the GaP packages and service facades from
uPortal3.
4. building uPortal3 with the GaP libraries, including
the gap_uPortal2_api and working out configuration issues.
And then,
5. over time, removing references to the uPortal GaP
classes and replacing them with references to the standalone
GaP classes.
I'd like to put in time this week and next on I've put in
some time on the maven build on this, since it should be
pretty slow around here.
I don't think this is a great deal of work.
Dan
Eric Dalquist wrote:
Dan,
At the unconference we had talked about about moving to the stand-alone
GaP code for uPortal 3. I can't remember much beyond that, is this
something you have looked into at all and what are your views on the
amount of work involved?
-Eric
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
