[jbosstools-issues] [JBoss JIRA] (JBIDE-24877) CDK 2 detection results in CDK 3 adapter creation
[
https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-24877:
-------------------------------------
I really wanted to debug this bc it meant the detector is behaving badly. I added a few
more checks, specifically, the cdk3 detector shouldn't return true unless a folder has
a "cdk" file, a "config" folder, and a "config/config.json"
file.
To be clear, my checks aren't specific to file or folders, so it can be tricked. So
please don't open a bug by intentionally tricking it ;) We're doing light
validation here.
Anyway, I've created https://github.com/jbosstools/jbosstools-openshift/pull/1553
with a fix.
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)