[
https://issues.jboss.org/browse/JBIDE-25901?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-25901:
-------------------------------------
It seemed extremely common to me that users (or other testers) would complain of their cdk
/ minishift not functioning properly, and this was caused by an old minishift_home which
had data from an old version of cdk.
This happened so often that it became extremely annoying. Having 3 different versions of
CDK all using the same minishift_home, and testing each version, having one version
clobber or corrupt the home directory for the other two, etc etc.
It really seems to me that best practices should indicate that each server has its own
minishift_home. I really don't know if what I'm doing is best, but it seems to me
it's the cleanest.
I guess we can ask for an executive opinion here. But I really don't think encouraging
everyone to use the same minishift_home is smart.
MINISHIFT_HOME is not propagated to new detected cdk binary properly
--------------------------------------------------------------------
Key: JBIDE-25901
URL:
https://issues.jboss.org/browse/JBIDE-25901
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk, runtime-detection
Affects Versions: 4.5.3.Final
Reporter: Martin Malina
Assignee: Rob Stryker
Following some of the changes to how cdk and runtime detection works (most notably that
path to cdk binary can now be used for searching), I wanted to try and see if
$MINISHIFT_HOME is still respected and works properly. And it seems to fail.
I started devstudio with MINISHIFT_HOME=/Users/rasp/minishift_home, then ran runtime
detection against /Users/rasp/tmp where a cdk binary was found. But the newly created
adapter had this set up as minishift home: /Users/rasp/tmp/MINISHIFT_HOME
That seems totally wrong.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)