[
https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-24877:
---------------------------------------
So I finally tried this myself. And I cannot reproduce.
I removed my ~/.minishift and then ran minishift cdk-setup with
MINISHIFT_HOME=/Users/rasp/minishift_home.
Then I installed devstudio in the same directory where I had the cdk folder of cdk 2 - so
that cdk 2 is detected.
I ran the installer with the MINISHIFT_HOME variable, so that at the end of the
installation when I click Open devstudio, it would get this var.
When devstudio started, it opened the runtime detection dialog to complain that the cdk 3
runtime it found is missing minishift binary location - that was a surprise - I never get
this normally when ~/.minishift is used and the binary is then empty (because I never have
it on PATH). Anyway, I fixed that using the quickfix.
The result was that I had two server adapters - exactly as Rob says, one for cdk 2 and one
for cdk 3. No odd mixtures or anything. Everything seemed correct.
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)