[jbosstools-issues] [JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK
Rob Stryker (JIRA)
issues at jboss.org
Thu Mar 31 14:48:00 EDT 2016
[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184913#comment-13184913 ]
Rob Stryker commented on JBIDE-22004:
-------------------------------------
Hi Hardy:
The primary purpose of this file is to designate what is or is not a cdk. It has other secondary purposes which help us in creating our openshift and docker connections, but this is primary.
Without this marker file, all we'd have is Vagrantfile. When a user wants to 'scan' a folder recursively to locate any cdk instances, we'd probably end up claiming every folder with a VagrantFile in it is a cdk, because there's no real way to parse the VagrantFile to determine if it's actually referencing the CDK or not.
Instead, we ask the installer or other distributions to include a .cdk file so that we can separate it from other vagrant instances.
Does this need to be in a raw cdk distribution? Only if we want the tools to autodetect it when a user scans a folder.
> 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