[jbosstools-issues] [JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK
Hardy Ferentschik (JIRA)
issues at jboss.org
Thu Mar 31 08:40:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184594#comment-13184594 ]
Hardy Ferentschik commented on JBIDE-22004:
-------------------------------------------
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}
> Runtime detection unable to detect CDK
> --------------------------------------
>
> Key: JBIDE-22004
> URL: https://issues.jboss.org/browse/JBIDE-22004
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Radim Hopp
> Assignee: Hardy Ferentschik
> Fix For: 4.4.x
>
>
> Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it.
> Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jbosstools-issues
mailing list