[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ] 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)