[jbosstools-issues] [JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK

[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ] Hardy Ferentschik edited comment on JBIDE-22004 at 3/31/16 9:43 AM: -------------------------------------------------------------------- See also https://github.com/projectatomic/adb-atomic-developer-bundle/issues/310 Personally I am not sure whether adding the .cdk file to the CDK distro makes sense, since hopefully one will be able to bootstrap a CDK _Vagrantfile_ by a simple {{vagrant init}}. What is this file good for really? Can we find other ways to achieve the same goal? Right now we have this: {code} openshift.auth.scheme=Basic openshift.auth.username=openshift-dev openshift.auth.password=devel cdk.version=2.0 {code} It looks like it mixes several concerns. There seems to be some OpenShift information and I believe what the server-adapter is really after, _cdk.version_. What's really needed here and why? [~rob.stryker] !? was (Author: hardy.ferentschik): See also https://github.com/projectatomic/adb-atomic-developer-bundle/issues/310 Personally I am not sure whether adding the .cdk file to the CDK distro makes sense, since hopefully one will be able to bootstrap a CDK _Vagrantfile_ by a simple {{vagrant init}}. What is this file good for really? Can we find other ways to achieve the same goal? Right now we have this: {code} openshift.auth.scheme=Basic openshift.auth.username=openshift-dev openshift.auth.password=devel cdk.version=2.0 {code} It looks like it mixes several concerns. There seems to be some OpenShift information and I believe what the server-adapter is really after, _cdk.version_. What's really needed here and why? [~rob.stryker] !? {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)