[
https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-24877:
---------------------------------------
[~odockal] bugged me long enough so I tried again. He said I needed to have cdk/cdk in the
structure to reproduce. I couldn't believe. But it's true. So you need these:
1. You have a structure like this:
./devstudio-whatever - your devstudio install
./cdk/cdk/components/rhel/rhel-ose/Vagrantfile - your vagrant file; i.e. unzip your
cdk.zip inside cdk/
2. Start devstudio with MINISHIFT_HOME=dir where dir is where you set up cdk 3 using the
same variable (in my case MINISHIFT_HOME=/Users/rasp/minishift_home)
Once I started devstudio, I only had one server - cdk 3. And the minishift home field was
set to /Users/rasp/git/cdk-install/cdk - which is the cdk 2 path.
Notice how I needed to have one more cdk directory to reproduce it - if there was just
./cdk/components/rhel/rhel-ose/Vagrantfile it worked fine.
CDK 2 detection results in CDK 3 adapter creation
-------------------------------------------------
Key: JBIDE-24877
URL:
https://issues.jboss.org/browse/JBIDE-24877
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.5.1.AM1
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Minor
Fix For: 4.5.1.AM2
As described by [~odockal] in JBIDE-24447:
When you start devstudio and it finds cdk 2 installed inside ../../../cdk/ relative to
eclipse's config, it will create a cdk 3 server instead of cdk 2.
This relative path normally translate to a structure like this:
$SOME_DIR/devstudio
$SOME_DIR/cdk/YOUR/CDK/2/SOMEWHERE/INSIDE/HERE
BUT... this will only happen in a special situation where you have CDK 2 installed where
devstudio looks for it (see above) AND you set up the MINISHIFT_HOME env var to point to
your CDK 3 home when you start devstudio.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)