[
https://issues.jboss.org/browse/JBIDE-24447?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-24447:
---------------------------------------
{quote}
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.
This sounds like it's working as expected?
{quote}
My understanding was that Ondrej didn't have cdk 2 set up at all so how come Eclipse
used that location? But that would really be strange. It looks more likely that in fact
cdk 2 path was set up somewhere. Ondrej will need to check again.
{quote}
This sounds like a legitimate bug.
{quote}
I created a JIRA for the inconsistent cdk 3 server adapter name: JBIDE-24875
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)