[ https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10784: ----------------------------------------- [~manovotn] Ignore the deprecation. MSC has new API that it wanted people to use, so it deprecated the old one. But almost nothing in WildFly uses that new API, and it's not a no-thought activity to switch chunk of functionality to it; things can break when partial conversions are done. IMHO that deprecation was premature as it just scares people. That said, I'm not sure you need to do DeploymentPhaseContext.getServiceRegistry().getService(WeldBootstrapService.SERVICE_NAME). Perhaps you could just retain WeldStartCompletionService and have it depend on / inject WeldBootstrapService. But the stuff from L296-299 at https://github.com/wildfly/wildfly/pull/10795/files#diff-5437e2864026abc7... isn't necessary. In my last comment I didn't mean to imply WeldStartCompletionService shouldn't depend on anything; just that it didn't need to depend on the services that are causing this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)