[ https://issues.jboss.org/browse/JBIDE-18568?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18568: ------------------------------------- Unfortunately, the code that sets up the DS stuff is in the plugin org.jboss.tools.as.runtimes.integration and so can't really be called from as.core/as.ui since it sits above those two. We could make a different change though. We could have as.runtime.integration add a server creation listener to run the following code, rather than run it directly in the JBossASHandler (runtime detection code that creates the server) {code} if( isDtpPresent()) new DriverUtility().createDriver(asLocation.getAbsolutePath(), serverType); {code} Since DriverUtility is in as.runtime.integration, it can't be called directly from as.core/as.ui. Currently JBossASHandler calls these two lines directly when adding a server adapter. If we switched it to a listener, it could work in all cases, except if as.runtime.integration hasn't been started yet as a bundle, in which case the listener wouldn't be added. It'd still help, but, unless we could somehow force as.runtime.integration to start early, it'd still have the potential to not create the driver. -- This message was sent by Atlassian JIRA (v6.3.8#6338)