[jbosstools-issues] [JBoss JIRA] (JBIDE-24877) CDK 2 detection results in CDK 3 adapter creation

[ https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24877: ------------------------------------- I'm not able to replicate this at all. :| When I replicate teh above instructions, I end up with 2 different server adapters created: 1 is a CDK 2.x but just has simple name "Container Development Environment". Opening in the editor reveals it is a proper cdk2 server, with vagrantfile location set properly to (base)/cdk/components/rhel/rhel-ose The second is a cdk3 server adapter with name "Container Development Environment 3". Opening it in the server editor reveals the proper cdk3 UI with ~/.minishift as the folder (thus ignoring the MINISHIFT_HOME flag). However, a look at the code reveals this is intentional, and that if ~/.minishift exists, it will initialize THAT folder, but not initialize the MINISHIFT_HOME folder. It will add both as runtime paths, though, which can be verified by opening the runtime detection preference page. But I am 100% unable to replicate ANY cdk3 server adapter with a CDK2 path or a cdk2 server with a minishift path. [~mmalina] are you able to replicate? -- This message was sent by Atlassian JIRA (v7.2.3#72005)