[
https://issues.jboss.org/browse/JBIDE-25901?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-25901:
---------------------------------------
[~adietish] we're discussing this issue with Rob ATM and we ended up agreeing that
probably not that much needs to change. Once we're done we will sum up the current
functionality and add it to
https://issues.jboss.org/browse/RHDEVDOCS-724 to be
documented.
As to what $MINISHIFT_HOME is for: In CLI, by default, ~/.minishift is used for storing of
all the data, but you can change this by defining your MINISHIFT_HOME env var and pointing
it to another directory. That way minishift/cdk will use that directory instead.
There was a feature request a while back to support this variable in devstudio, i.e. use
the custom directory instead of the default (if $MINISHIFT_HOME is set for the Eclipse
process). But it turns out that this is quite a pain to do right - you don't always
want to use this, especially if you download a new CDK binary directly in Eclipse.
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)