I've implemented the incomplete deployment exception,
example output:
2006-09-21 05:53:55,398 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
file:/home/ejort/mc-vdf-work/build/output/jboss-5.0.0.Beta/server/default/deploy/bsh-deployer.xml
file:/home/ejort/mc-vdf-work/build/output/jboss-5.0.0.Beta/server/default/deploy/ear-deployer.xml
file:/home/ejort/mc-vdf-work/build/output/jboss-5.0.0.Beta/server/default/deploy/ejb-deployer.xml
file:/home/ejort/mc-vdf-work/build/output/jboss-5.0.0.Beta/server/default/deploy/ejb3-interceptors-aop.xml
file:/home/ejort/mc-vdf-work/build/output/jboss-5.0.0.Beta/server/default/deploy/http-invoker.sar/invoker.war/
file:/home/ejort/mc-vdf-work/build/output/jboss-5.0.0.Beta/server/default/deploy/jbossweb-tomcat6.sar/ROOT.war/
file:/home/ejort/mc-vdf-work/build/output/jboss-5.0.0.Beta/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
file:/home/ejort/mc-vdf-work/build/output/jboss-5.0.0.Beta/server/default/deploy/jmx-console.war/
file:/home/ejort/mc-vdf-work/build/output/jboss-5.0.0.Beta/server/default/deploy/management/console-mgr.sar/web-console.war/
*** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
jboss.ejb3:service=EJB3Deployer
-> jboss.ejb:service=EJBDeployer{Start:** NOT FOUND **}
-> jboss.ejb:service=EJBDeployer{Create:** NOT FOUND **}
*** CONTEXTS IN ERROR: Name -> Error
jboss.ejb:service=EJBDeployer -> ** NOT FOUND **
This brought up the issue that we need a way
to identify what deployments we expect only to provide classloading.
For now, I'm excluding .jar files with a HACK.
