[
https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi...
]
Hardy Ferentschik commented on JBIDE-21290:
-------------------------------------------
{quote}
Runtime detection is typically used for JBoss EAP runtimes where you want to show the
version
{quote}
I see, thanks. That was the part I was missing
{quote}
It may seem redundant to show version of CDK now, but like any other product, it will have
multiple versions in time, so I think it makes sense to show the version there.
{quote}
Sure, the problem is that there is no discover-able version in the CDK as of now. There is
this issue to track this
https://github.com/projectatomic/vagrant-adbinfo/issues/64. Once
the version is added and the vagrant plugin can report it, we can retrieve the version
that way. Until then we might as well hard code the version.
CDK 2 is detected as version 1.0
--------------------------------
Key: JBIDE-21290
URL:
https://issues.jboss.org/browse/JBIDE-21290
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift, runtime-detection
Affects Versions: 4.3.1.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Minor
Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png
When you detect CDK using runtime detection, it will show you the name cdk-v2 which
clearly shows it's version 2 (this is actually just based on the folder it seems). But
the Version column says Version 1.0.
!cdk-runtime-detection.png!
Could we change it to version 2?
I know that this probably doesn't have any meaning right now - I noticed there is no
runtime anymore, so the version is nowhere to be seen once you create the cdk server
adapter. But it would still be nicer to show the correct version if possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)