[JBoss JIRA] (JBDS-3819) Showing that we detected 0 existing components is useless
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-3819?page=com.atlassian.jira.plugin.... ]
Joshua Wilson reassigned JBDS-3819:
-----------------------------------
Assignee: Denis Golovin (was: Joshua Wilson)
> Showing that we detected 0 existing components is useless
> ---------------------------------------------------------
>
> Key: JBDS-3819
> URL: https://issues.jboss.org/browse/JBDS-3819
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Priority: Minor
> Labels: havoc, ui
> Fix For: 10.0.1.AM2
>
>
> We found 0 installed component that meets the requirement. Apart from the fact that only 1 component should be singular, saying that we've found nothing does not provide any additional information.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3812) Target folder input looks weird
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-3812?page=com.atlassian.jira.plugin.... ]
Joshua Wilson reassigned JBDS-3812:
-----------------------------------
Assignee: Denis Golovin (was: Joshua Wilson)
> Target folder input looks weird
> -------------------------------
>
> Key: JBDS-3812
> URL: https://issues.jboss.org/browse/JBDS-3812
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc, ui
> Fix For: 10.0.1.AM2
>
> Attachments: selected.png, unselected.png
>
>
> There are a few visual issues with the target folder input group that make it look really weird:
> - When not focused, there is no real border around the input box, just a little line on the bottom
> - The Browse button is shoved right on top of the input field - when the field is focused, its border is hidden under the button on the right
> - The input field should probably be auto-focused
> - When the validation message shows an error, it has a red icon with black text
> - The path with spaces warning has black text - plus since this path is not allowed, it should show as error, not a warning
> - The message that folder will be created looks exactly like a warning, it should be styled as info (no orange text and icon)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22609) Provided wrong credentials, CDK server adapter says "started" even though it is not.
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22609?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22609.
---------------------------------
I agree that there is not much we can do here. Fixing adb/service-manager is the way to go. I verified the updated error message and created a new JIRA to track the upstream issue:
JBIDE-22725
Closing.
> Provided wrong credentials, CDK server adapter says "started" even though it is not.
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-22609
> URL: https://issues.jboss.org/browse/JBIDE-22609
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Environment: Devstudio 10.0.0.GA (B33), CDK 2.1.RC4, Windows 10
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.1.AM1
>
>
> When CDK startup fails when it is provided wrong credentials (it fails on vagrant-registration), CDK server adapter sets its state to "started" and OS3 connection is created (even though OS3 is not running in vagrant) with some weird IP (10.0.2.15). Also error pops up saying "The CDK VM is up and running, but OpenShift is unreachable at url https://10.0.2.15:8443/healthz/ready". I really don't know where this IP comes from. I was able to reproduce it on Fedora using libvirt box and the IP was something like (192.168.x.x)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-22195.
---------------------------------
Resolution: Done
On Windows 10 is it working without issues.
Verified in:
Red Hat JBoss Developer Studio
Version: 10.0.1.AM1
Build id: AM1-v20160711-2026-B5656
Build date: 20160711-2026
> Docker-machine look-up does not work
> ------------------------------------
>
> Key: JBIDE-22195
> URL: https://issues.jboss.org/browse/JBIDE-22195
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.4.x
>
>
> The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying :
> {quote}
> The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin
> {quote}
> even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}.
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=493328
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months