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

[Hardy Ferentschik (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185201#comment-13185201 ] 

Hardy Ferentschik commented on JBIDE-22004:
-------------------------------------------

{quote}
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. 
{quote}
Sure, but what if the CDK Vagrantfile would define some variable/value in its config. The value would be irrelevant really for the actual Vagrant config, but you could parse/grep for this value and if it exist consider this Vagrant setup as a CDK.

The problem with the marker file is how to get it there. ATM, the CDK ships a zip bundle which contains a _Vagrantfile_ which you would need to copy into an empty directory. We could add the marker file to the zip bundle and document that the user should copy this file as well. However, that is error prone. Also in the hopefully not so long future, would would be able to create an initial Vagrant setup for the CDK by just typing {{vagrant init cdk}}. This would create an "empty" Vagrantfile just referencing the right box file. The actual default configuration would then be in the _Vagrantfile_ of the box file. How would we deal with the marker file then? I guess the "empty" config file might be problematic for my proposed solution for parsing for something in the _Vagrantfile_ as well.

Another idea would be to add something to the default Vagrantfile which creates the .cdk file. After all the _Vagrantfile_ is plain Ruby!?

Either way, just adding the marker file to the zip bundle of the CDK won't buy us much in the long run. We need different solution.

> 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)