[JBoss JIRA] (JBIDE-21531) New Application wizard: Template parameter with empty/generated value has wrong validation
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21531?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21531:
-----------------------------------
Assignee: Viacheslav Kabanovich
> New Application wizard: Template parameter with empty/generated value has wrong validation
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21531
> URL: https://issues.jboss.org/browse/JBIDE-21531
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> In New OpenShift application wizard on the wizard page with template parameters when I select to edit a parameter with empty ("") or generated ("(generated)") value, text widget to enter new value is marked with error validation mark, that new value is required, but OK button is enabled. It either should be without validation mark or OK button should be disabled, if confirmation is meant to be allowed only for a new value.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21301) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21301:
------------------------------------------
I cannot replicate this. I tried with a clean installation and had the oc binary picked from path.
Do you have it on your path?
> Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-21301
> URL: https://issues.jboss.org/browse/JBIDE-21301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: openshift_v3, preferences
> Fix For: 4.3.1.Beta2
>
>
> In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21301) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21301 at 1/22/16 2:45 PM:
-------------------------------------------------------------------
I cannot replicate this. I tried with a clean installation and had the oc binary picked from path.
[~mlabuda] Do you have it on your path?
was (Author: adietish):
I cannot replicate this. I tried with a clean installation and had the oc binary picked from path.
Do you have it on your path?
> Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-21301
> URL: https://issues.jboss.org/browse/JBIDE-21301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: openshift_v3, preferences
> Fix For: 4.3.1.Beta2
>
>
> In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21563) [regression] Explorer: (Multiple application) deletion does not work anymore
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21563?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21563 at 1/22/16 2:27 PM:
-------------------------------------------------------------------
reopened to indicate that we want this to make it into the respin-a (jbosstools-4.3.1.Beta2x)
was (Author: adietish):
reopened to indicate that we want this to make it into the respin-a
> [regression] Explorer: (Multiple application) deletion does not work anymore
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21563
> URL: https://issues.jboss.org/browse/JBIDE-21563
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v2, respin-a
> Fix For: 4.3.1.Beta2, 4.3.1.CR1
>
>
> Previously it was possible to select multiple OpenShift 2 applications and delete them at once via context menu Delete application(s).... Currently there is no such context menu anymore and it is a pain to delete several applications one by one.
> Added by Slava: In my environment, Delete for objects of OpenShift 2 does not work at all (menu is shown, but nothing happens). It seems the cause is a slip in plugin.xml for Openshift 3, handler org.jboss.tools.openshift.internal.ui.handler.DeleteResourceHandler declared activeWhen with <or> (count==1 _or_ instanceof IResource). So, formally having a lot of restrictions but passing them, this handler imposes itself on all selections. Though, it is possible that the bug reveals not in all environments.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21563) [regression] Explorer: (Multiple application) deletion does not work anymore
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21563?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21563:
-------------------------------------
Labels: explorer openshift_v2 respin-a (was: explorer openshift_v2)
> [regression] Explorer: (Multiple application) deletion does not work anymore
> ----------------------------------------------------------------------------
>
> Key: JBIDE-21563
> URL: https://issues.jboss.org/browse/JBIDE-21563
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v2, respin-a
> Fix For: 4.3.1.Beta2, 4.3.1.CR1
>
>
> Previously it was possible to select multiple OpenShift 2 applications and delete them at once via context menu Delete application(s).... Currently there is no such context menu anymore and it is a pain to delete several applications one by one.
> Added by Slava: In my environment, Delete for objects of OpenShift 2 does not work at all (menu is shown, but nothing happens). It seems the cause is a slip in plugin.xml for Openshift 3, handler org.jboss.tools.openshift.internal.ui.handler.DeleteResourceHandler declared activeWhen with <or> (count==1 _or_ instanceof IResource). So, formally having a lot of restrictions but passing them, this handler imposes itself on all selections. Though, it is possible that the bug reveals not in all environments.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months