[
https://issues.jboss.org/browse/JBIDE-22598?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-22598:
---------------------------------------
Radim just told me this works for him which was odd. And then he found out that this works
when he searches deep enough, but not when he's too high up.
Let me give you an example. Say you have this dir structure:
/Users/rasp/git/cdk-install/07-Oct-2016/cdk/components/rhel/rhel-ose/
If you search this path (or anything even deeper), it will work:
/Users/rasp/git/cdk-install/07-Oct-2016/cdk
But if you search this path (or anything even higher up), it won't work:
/Users/rasp/git/cdk-install/07-Oct-2016
Support runtime detection for manual CDK install
------------------------------------------------
Key: JBIDE-22598
URL:
https://issues.jboss.org/browse/JBIDE-22598
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdk, runtime-detection
Affects Versions: 4.4.0.Final
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.4.2.AM2
Right now with CDK 2.1 when you have a manual cdk install (i.e. using cdk.zip and then
adding the vagrant box yourself), there will be no .cdk marker, so Runtime Detection will
not work.
The only case where Runtime Detection will work is when you use the (as of now
Windows-only) suite installer. At that point Runtime Detection will do its thing silently
without you noticing.
The way I see it there are two options:
a) Create and upstream issue with CDK and ask them to include a basic .cdk in their zip
b) Make the runtime detection work without .cdk
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)