Classes from the original utility jar have now been transfered into
plug-ins.  (from last comment) The different plug-ins are primarily so
that it is easier to take care of dependancies.  I wanted to make sure
that utils.core.domino and utils.errorHandling were correctly built on
one another in particular due to issues I used to have with
stackoverflow exceptions.  These classes were at one time calling each
other in strange loops through the SessionHelper class.  Because I had
started to build different plug-ins for different modules, I continued
this scheme for the locking, cookies classes.

Important steps to come are the following,
1. Go through and find a way to get key values from the notes.ini or xsp
configurations.  This is necesary for most importantly the primary
configuration of the core.domino classes as well as the
utils.errorhandling classes.

2. Decide how to best go about getting objects from the scopedMaps.  Is
it best to go through a variable resolver, or to ask the map whether the
object in question is there already and to add it if it is not there?

3. Build the utils.ui classes.  These classes will include getting HTML
tables for the scopedMaps, for the cookie property maps, and for the
debug tables.  The Admin Panel will no longer exist in the platform as
its own custom control out-of-the-box, but rather the tables will be
controls that can be placed where the user sees fit.  A custom control
can still be made and then copied around.

4. Besided the constant testing that will need to be done, Test all
aspects of the ui and api.

5. Fix and missing or now-invalid JavaDoc entries.

6. Add any needed licensing information.