up3 package name

[Andrew Petro]

I'm starting to think it would be helpful to rename the uPortal 3 package
structure so as to not collide with the uPortal 2 package structure. This
allows an upgrade path of pasting in pieces of uPortal 2 alongside the
uPortal 3 source and hacking away (e.g. to support a favorite channel) while
keeping a clear delineation of what came from uportal 2 versus what is part
of uPortal 3.

org.jasig.up3.... for the uPortal 3 code,

org.jasig.portal... for the code pasted from uPortal 2 in any given
deployer's local upgrading environment.

For instance, if you drag in an IChannel that depends on the IPermissible
API from uPortal 2, the naïve way to do this involves pasting files into
uPortal 3's org.jasig.portal.security package.

Thoughts? Too unimportant too late? An easy and quick way to make the
porting forward task more sane?

Andrew

------------------------------------
Unicon, Inc.
Andrew William Petro
Software Developer
ape...@unicon.net
3140 N. Arizona Ave
Suite 113
Chandler, AZ 85225
mobile: 203.915.7333
------------------------------------