[JBoss JIRA] (JBIDE-21622) Timeout to stop starting of CDK should be longer
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21622:
----------------------------------
Summary: Timeout to stop starting of CDK should be longer (was: CDK server adapter is halted after 450 seconds)
> Timeout to stop starting of CDK should be longer
> ------------------------------------------------
>
> Key: JBIDE-21622
> URL: https://issues.jboss.org/browse/JBIDE-21622
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Attachments: cdk_vagrant_halt.png
>
>
> When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. I think it is not proper to kill it (vagrant halt) after 450 seconds just like that. Timeout could be higher by default.
> !cdk_vagrant_halt.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21614) OpenShift connection is not created when CDK server starts on Windows
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21614?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-21614:
-------------------------------------------
It is also related to [vagrant-adbinfo #20|https://github.com/projectatomic/vagrant-adbinfo/issues/20]. I think the issues does not occur when one uses ssh/scp instead of Putty.
> OpenShift connection is not created when CDK server starts on Windows
> ---------------------------------------------------------------------
>
> Key: JBIDE-21614
> URL: https://issues.jboss.org/browse/JBIDE-21614
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> I'm testing the latest JBDS 9.1.0.CR1 nightly build + CDK from the PDK installer.
> When I create and start CDK server on my Ubuntu it creates OpenShift connection.
> When I do the same (same CDK, same JBDS build) on Windows, vargrant starts successfully (I can access OS web console etc.) but the OpenShift connection is not created in JBDS.
> It worked before (sometime ago on a different installation).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21616:
---------------------------------------
[~adietish] I could, but... CDK adapter is our creation. Do you know whether this his happens in some other place too? Bcs. reporting issue to Eclipse bugzilla that something is happening in JBT in Launch Configuration shell is not quite proper I think. [~rob.stryker] Or do you have any hint which server adapter could have similar Launch Configuration to verify it?
> Main tab for CDK launch configuration is not whole by default
> -------------------------------------------------------------
>
> Key: JBIDE-21616
> URL: https://issues.jboss.org/browse/JBIDE-21616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Environment: Fedora 22, GTK3
> Reporter: Marián Labuda
> Attachments: after.png, before.png
>
>
> In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available.
> !before.png!
> After switching to Environment tab and back, Working directory and Arguments widgets become available.
> !after.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month