the benefit might be small now, but with a serialized startup process this will only get worse in the future. think of what the server startup times would be if a user has 50 deployed plugins. this will significantly reduce the time needed to start all plugins, because the plugin deployer will be able to deploy concurrently those that are not part of the same lineage. furthermore, once a common ancestor is successfully deploy, all descendant lineages will proceed with their deploys concurrently.
rev884 - subclassed LatchService to capture the required pieces of information needed during a plugin deployment; rewrote main part of plugin deployer to leverage the latched concurrent controller framework to concurrently deploy plugins;
rev885 - fixed typo for logger initialization rev887 - typo, the completion latch should have also been final
closing this code-level item, no qa necessary.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-526