[JBoss JIRA] (JBIDE-22548) Fix remaining CDK names inconsistencies
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22548?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22548:
---------------------------------------
Verified in devstudio 10.0.0.GA B18.
The server adapter name is now correct - Red Hat Container Development Kit.
The default name is Container Development Environment.
Runtime Detection is currently not supported for manual cdk installs - I created a JIRA to track that: JBIDE-22598
So to verify that, I will ask somebody who uses the devsuite installer frequently - [~jrichter1], can you check that the name in Servers view is Container Development Environment for CDK?
> Fix remaining CDK names inconsistencies
> ---------------------------------------
>
> Key: JBIDE-22548
> URL: https://issues.jboss.org/browse/JBIDE-22548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> This is a follow up of JBIDE-22431 . There are some remaining things to be fixed.
> 1. Alexey asked for the server adapter to be renamed to "Red Hat Container Development Kit" but it's now "Red Hat Container Development Kit Support". While it makes sense to have "Support" in the feature/plugin name, I don't think it makes sense for the server adapter type or the server name once it's created. So please drop the Support.
> 2. Runtime detection now uses the name of "Container Development Environment". This is inconsistent with creating the server adapter manually. Some time ago we tried to unify this - EAP now has the same names both when created via runtime detection or manually (default name). So if we really want to use the CDE thing (which I'm not a fan of, but whatever), I suggest we use this as the default name when creating a CDK adapter manually. But the adapter type should probably still be "Red Hat Container Development Kit" (no Support)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22598) Support runtime detection for manual CDK install
by Martin Malina (JIRA)
Martin Malina created JBIDE-22598:
-------------------------------------
Summary: Support runtime detection for manual CDK install
Key: JBIDE-22598
URL: https://issues.jboss.org/browse/JBIDE-22598
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdk, runtime-detection
Affects Versions: 4.4.0.Final
Reporter: Martin Malina
Assignee: Rob Stryker
Right now with CDK 2.1 when you have a manual cdk install (i.e. using cdk.zip and then adding the vagrant box yourself), there will be no .cdk marker, so Runtime Detection will not work.
The only case where Runtime Detection will work is when you use the (as of now Windows-only) suite installer. At that point Runtime Detection will do its thing silently without you noticing.
The way I see it there are two options:
a) Create and upstream issue with CDK and ask them to include a basic .cdk in their zip
b) Make the runtime detection work without .cdk
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months