[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Hardy Ferentschik commented on JBIDE-21290: ------------------------------------------- {quote} Even if cdk.zip goes away, there will always be some folder somewhere that contains the Vagrantfile. And we just need to make sure that folder contains the marker - that should always be doable. {quote} Not necessarily. In a perfect work you should get away with {{vagrant init}}. Either way, if you want to have the marker file with the version, then I expect this to be added/generated by the installer. {quote} OK, that is a valid concern. Currently we don't support any upgrade of cdk at all, so I'm not sure exactly how that would work. {quote} Support in which sense? Then we don't document how to do it? That will not stop users with some understanding on how Vagrant works to do it. Personally I do it a lot. Also, atm we only report a major version, but to make this version string really valuable it needs to be able to identify a specific built as well. This ties into https://github.com/projectatomic/adb-atomic-developer-bundle/issues/436. Having this type of information presented to me by the GUI would be useful, however there is only one 100% accurate place where to get this information from. I think it is completely reasonable to defer displaying the version until it can be properly determined. -- This message was sent by Atlassian JIRA (v6.4.11#64026)