[
https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi...
]
Hardy Ferentschik commented on JBIDE-21290:
-------------------------------------------
So there is now {{vagrant service-manager box version --script-readable}} which can be
called to determine the version of CDK/ADB. The VM has to be running for this to work, but
I think this is the only way to properly report a version. Adding the marker file has
several issues:
# The cdk.zip which maybe could be used to add it, might go away in the near future. At
least that is the plan. It would be really up to the platform installers to create the
marker files and add the version.
# The user could install a CDK and then upgrade it later (just the VM, not the whole
install). The reported version would still be the one in the marker file.
IMO, the best solution is to get the version from the VM. Could the UI not display
"unkown" until the VM is started and then update the version based on
service-manager call?
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: cdk, runtime-detection, upstream
Affects Versions: 4.3.1.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Minor
Fix For: 4.4.x
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)