[
https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi...
]
Ondrej Dockal commented on JBIDE-24447:
---------------------------------------
So, I would like to make it clear.
CDK 2 is automatically detected by checking the running eclipse's
configuration location and going to the relative path
Platform.getOS().equals(Platform.OS_MACOSX) ? "../../../" : "") +
"../../../cdk/"; This is typically where the installer would install the older
runtimes. It then scans that folder for stuff.
Alright, then it is explained why cdk 2.x is detected ([~mmalina] I have CDK 2.x set on
that path, so it is alright). I have no problem with that. The thing is that
runtime-detection finds path of CDK 2.x and use it in *CDK 3* server adapter which is bug
in my opinion. CDK 2.x server adapter should be created, not CDK 3, right? Notice that
CDK3 server adapter is created only on fresh start (new workspace) and if MINISHIFT_HOME
env. var is set. If not set, then CDK 2.x is created (which seems corret).
Look for minishift configuration in MINISHIFT_HOME
--------------------------------------------------
Key: JBIDE-24447
URL:
https://issues.jboss.org/browse/JBIDE-24447
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: runtime-detection
Affects Versions: 4.4.4.Final
Reporter: Jan Richter
Assignee: Rob Stryker
Fix For: 4.5.x
Attachments: cdk2_x_RD.png, cdk3_minishift_home.png
One can use the MINISHIFT_HOME variable to save minishift configuration somewhere else
than in ~/.minishift
It would be nice if runtime detection looked there if the variable is configured.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)