There existed an issue in JBoss EAP 6 where dependency graph resolution was not taking into account situations where the `Class-Path` specified in deployment manifests may be transitive.
This would result in a module attempting to start before all its dependencies were started, and would cause the application to fail to deploy, resulting in the following exception:
Caused by: org.jboss.modules.ModuleLoadException: JBAS018760: Timeout waiting for module service: deployment.example.ear.example-ejb.jar:main
To fix this issue, a multi-stage resolution process was added to make sure that all dependent module specification services have started before starting a module service.
As a result, a deployment should no longer fail where transitive dependencies are specified in its `Class-Path`.