[jbosstools-issues] [JBoss JIRA] (JBIDE-21603) Runtime environments and cdk are broken

[Rob Stryker (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154990#comment-13154990 ] 

Rob Stryker commented on JBIDE-21603:
-------------------------------------

We don't store any data in a runtime. We provide no UI for a runtime. What is present is basically a stub runtime with no saved values, which is never used. Removing the runtime entirely could prevent something like publishing to work, so it was left in for now in its stub form.  I wouldn't go so far as to say it's 'broken' so much as 'useless' ;) 

Since it doesn't look like the CDK server will have publish support, and instead publish support will be implemented by the openshift server, it's probably safe to completely remove the notion of a "runtime" for CDK. 

> Runtime environments and cdk are broken
> ---------------------------------------
>
>                 Key: JBIDE-21603
>                 URL: https://issues.jboss.org/browse/JBIDE-21603
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.3.1.Beta2
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>
> When you open the New Server dialog and want to create a new CDK server while there is already one existing, it will preselect the existing runtime. There is an "Add" button to add a new runtime, but it doesn't work - when you click it, nothing happens.
> 1. Create a cdk server
> 2. Open the new server dialog again
> 3. For server type, select CDK
> 4. The server runtime env field will show the existing runtime. Click Add next to the field to create a new runtime - nothing happens
> At first, I thought it was just this. But now I'm confused what the design really is. At first it seemed you just added the notion of runtimes just like we use them for JBoss AS / WildFly / EAP. Then it seemed you dropped runtimes and just used servers. But now it seems there is still a runtime displayed in the server editor.
> When I first created a cdk server manually (this was cdk beta4), it has its own runtime. Then I used runtime detection to add another cdk server (this was openshift-vagrant git repo), but in server editor, it shows the Beta4 runtime is used and there is no way to change it. Then in preferences -> Server -> Runtime Environments, you can see the one runtime, but you can't edit it. And when you want to add a new one, there is no CDK type in the new runtime dialog.
> So it seems we're somewhere halfway between not using runtimes at all and using them to some degree.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)