-
Bug
-
Resolution: Done
-
Critical
-
3.1.0.GA, 3.1.1
-
None
When attempting to add SOA-P 5 as an ESB runtime to JBDS 3.0.0, this is only possible if a 'default' server configuration exists. If the 'default' server configuration is renamed to something else (like 'development' for example) then the runtime is not valid.
org.jboss.tools.esb.core.runtime.ESBRuntimeResolver_47#getJarDirectories(..) has a hard-coded reference to the "default" directory.
- blocks
-
JBDS-1271 ESB 4.7 runtime detection depends on default server configuration
- Resolved