[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22152:
-------------------------------
Sprint: devex #116 June 2017
> Unknown launch is left in Debug view after deletion of an OS 3 server adapter
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22152
> URL: https://issues.jboss.org/browse/JBIDE-22152
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Minor
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.x
>
> Attachments: AfterDeleteLaunchConfiguration.png, BeforeDeleteLaunchConfiguration.png, launches.png
>
>
> When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them.
> !launches.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20716:
-------------------------------------
Estimated Difficulty: Low
> Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20716
> URL: https://issues.jboss.org/browse/JBIDE-20716
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
>
> In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked.
> We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20686) Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20686:
------------------------------------------
Isnt the point of being able to restore defaults to override custom settings to a valid default. A blank field is simply not valid, I would not expect this. Can you argue why you expect this non-valid value when you choose to return to the defaults.
> Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20686
> URL: https://issues.jboss.org/browse/JBIDE-20686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, preferences
> Fix For: 4.4.x
>
>
> In OpenShift 3 workbench preference page restoring default setting by clicking on a button Restore Defaults pops up a warning dialog with title "No OpenShift Client binary" and text "Could not find the OpenShift binary "oc" on your path". I would expect that choosing default settings would just clear text field with oc binary location and no dialog is shown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20686) Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20686 at 6/14/16 8:08 AM:
-------------------------------------------------------------------
[~mlabuda] Isnt the point of being able to restore defaults to override custom settings to a valid default. A blank field is simply not valid, I would not expect this. Can you argue why you expect this non-valid value when you choose to return to the defaults.
was (Author: adietish):
Isnt the point of being able to restore defaults to override custom settings to a valid default. A blank field is simply not valid, I would not expect this. Can you argue why you expect this non-valid value when you choose to return to the defaults.
> Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20686
> URL: https://issues.jboss.org/browse/JBIDE-20686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, preferences
> Fix For: 4.4.x
>
>
> In OpenShift 3 workbench preference page restoring default setting by clicking on a button Restore Defaults pops up a warning dialog with title "No OpenShift Client binary" and text "Could not find the OpenShift binary "oc" on your path". I would expect that choosing default settings would just clear text field with oc binary location and no dialog is shown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20686) Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-20686:
----------------------------------------
Assignee: (was: Andre Dietisheim)
> Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20686
> URL: https://issues.jboss.org/browse/JBIDE-20686
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Labels: openshift_v3, preferences
> Fix For: 4.4.x
>
>
> In OpenShift 3 workbench preference page restoring default setting by clicking on a button Restore Defaults pops up a warning dialog with title "No OpenShift Client binary" and text "Could not find the OpenShift binary "oc" on your path". I would expect that choosing default settings would just clear text field with oc binary location and no dialog is shown.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months