[JBoss JIRA] (JBIDE-22187) Connection wizard: Should not be able to create duplicate Openshift connections
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich reassigned JBIDE-22187:
---------------------------------------------
Assignee: Viacheslav Kabanovich (was: Andre Dietisheim)
> Connection wizard: Should not be able to create duplicate Openshift connections
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22187
> URL: https://issues.jboss.org/browse/JBIDE-22187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21885) Properties: Remove "()" from context-menu name of Start Build
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21885?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich reassigned JBIDE-21885:
---------------------------------------------
Assignee: Viacheslav Kabanovich
> Properties: Remove "()" from context-menu name of Start Build
> --------------------------------------------------------------
>
> Key: JBIDE-21885
> URL: https://issues.jboss.org/browse/JBIDE-21885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202
> OS: Fedora 22 & Windows 10
> Reporter: Xia Zhao
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha2
>
> Attachments: build-config-properties-menu.png, start-build.png
>
>
> The "()" from context-menu name of Start Build should be removed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21885) Properties: Remove "()" from context-menu name of Start Build
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21885?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21885 at 5/17/16 6:03 PM:
------------------------------------------------------------------------
This is probably an upstream issue for some OS, at least Ubuntu. The "()" appears when a command parameter is set, it seems the command label provider wants to inform user about the fact in such a weird way.
The workaround is very simple - explicitly set label attribute on the reference to the command in menu.
was (Author: scabanovich):
This is probably an upstream issue for some OS, at least Ubuntu. The "()" appears when a command parameter is set, it seems the command label provider wants to inform user about the fact in such a weird way. Since user does not need that kind of info, and since there is only one possible parameter value for Start Build (or it can be empty), we can workaround it by using two different command names and distinguish source not by parameter but by command name
> Properties: Remove "()" from context-menu name of Start Build
> --------------------------------------------------------------
>
> Key: JBIDE-21885
> URL: https://issues.jboss.org/browse/JBIDE-21885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202
> OS: Fedora 22 & Windows 10
> Reporter: Xia Zhao
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha2
>
> Attachments: build-config-properties-menu.png, start-build.png
>
>
> The "()" from context-menu name of Start Build should be removed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-21885) Properties: Remove "()" from context-menu name of Start Build
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21885?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21885:
-----------------------------------------------
This is probably an upstream issue for some OS, at least Ubuntu. The "()" appears when a command parameter is set, it seems the command label provider wants to inform user about the fact in such a weird way. Since user does not need that kind of info, and since there is only one possible parameter value for Start Build (or it can be empty), we can workaround it by using two different command names and distinguish source not by parameter but by command name
> Properties: Remove "()" from context-menu name of Start Build
> --------------------------------------------------------------
>
> Key: JBIDE-21885
> URL: https://issues.jboss.org/browse/JBIDE-21885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Environment: JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160316-2139-B1202
> OS: Fedora 22 & Windows 10
> Reporter: Xia Zhao
> Priority: Minor
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha2
>
> Attachments: build-config-properties-menu.png, start-build.png
>
>
> The "()" from context-menu name of Start Build should be removed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3887) Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3887?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3887:
----------------------------------
As decided between myself, Fred, and Alexey, I will:
1. Rename CloudTools to CloudAndContainerTools
2. Add Docker & Vagrant Tools to new CloudAndContainerTools
3. Add Docker Tools to CoreTools
> Include Docker & Vagrant tooling 2.0.0 in JBT 4.4 & DS 10
> ---------------------------------------------------------
>
> Key: JBDS-3887
> URL: https://issues.jboss.org/browse/JBDS-3887
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Task
> Components: installer, updatesite
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 10.0.0.Alpha2
>
>
> Include Docker & Vagrant tooling 2.0.0 in JBoss Tools 4.4 & DS 10... somehow. (Mechanism to be clarified below.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22243:
---------------------------------------
Worked on this a little bit and its more involved then I thought. Events are not propagating as I would expect (hope). I'm actually wondering the value of this in the explorer view now since there is limited value IMO of refreshing a pod or build. I think we would be better off allowing a user to only:
# refresh from a deployment/service up
# possibly refresh resources associated with a deployment in the tabbed view.
[~fbricon] [~adietish] thoughts?
> Properties: "Refresh" has no effect
> -----------------------------------
>
> Key: JBIDE-22243
> URL: https://issues.jboss.org/browse/JBIDE-22243
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Fix For: 4.4.0.Alpha2
>
> Attachments: refreshing-wont-help.ogv
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months