AdminSvc now starts up in privileged mode and joins the workgroup.
Classloader spec in deployer config now has an option to set "parent priority" or "application priority", in which setting "application priority" causes classes to be loaded from the application in preference to the parent loader.
ContextualWorkManager has been changed over to present a ScheduledExecutorService for applications to use, rather than a WorkManager.

Starting up the Admin service now works.  AdminService is not yet fully implemented.
Admin Service is able to query all the ApplicationManager objects in the container context for application statuses.

StarterServiceDeployer now creates a working directory for each service and places the File for that directory into the service's configuration as $workingDirectory.

The StartupDeployer has been renamed to FolderBasedAppRunner which is more descriptive of its function.  It scans a folder at startup and runs any application archives that it finds.  Similarly, the ClientAppDeployer has been renamed to CommandLineAppRunner, since it runs the application specified on the command line.

The Context class now supports getting all components that implement a given interface.  This functionality is used to find all the ApplicationManager implementations that can be polled for applications.