[JBoss JIRA] (JBIDE-21139) OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21139?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21139:
--------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.Beta1)
> OpenShift 3 connection in OpenShift Explorer view is not refreshed upon editing
> -------------------------------------------------------------------------------
>
> Key: JBIDE-21139
> URL: https://issues.jboss.org/browse/JBIDE-21139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Labels: connection_wizard, explorer, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: connection.png
>
>
> After editing a connection which was without credentials (e.g. token was not stored in secure storage and eclipse got restarted) and there is tree item informing about such an error, editing the connection does not refresh connection item in OpenShift explorer view and it is necessary to refresh it via context menu of the connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21143) Triggering action on one connection refresh whole OpenShift Explorer view
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21143?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21143:
--------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.Beta1)
> Triggering action on one connection refresh whole OpenShift Explorer view
> -------------------------------------------------------------------------
>
> Key: JBIDE-21143
> URL: https://issues.jboss.org/browse/JBIDE-21143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Labels: explorer
> Fix For: 4.3.1.Beta2
>
>
> Actions such as deleting or creating a new project for an OpenShift connection (those which change content of OpenShift Explorer visually) causes refreshing all connection in OpenShift Explorer view - I have spotted it when I was creating a project for a connection of local OpenShift instance and while this project was being shown in OpenShift Explorer view under the connection, a connection to internal OSE instance had been refreshed too and loading tree item was shown underneath.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20755) Import OpenShift Application wizard contains redundant validation mark
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20755?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20755:
--------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.Beta1)
> Import OpenShift Application wizard contains redundant validation mark
> ----------------------------------------------------------------------
>
> Key: JBIDE-20755
> URL: https://issues.jboss.org/browse/JBIDE-20755
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Fix For: 4.3.1.Beta2
>
> Attachments: validation_mark.png
>
>
> In Import OpenShift Application wizard is one validation mark (red cross) on a text widget for a git clone location in case of already imported such repo. But there is shown also another validation mark in the middle of checkbox label.
> !validation_mark.png!
> This one is redundant and also its rendering is performed only when mouse is moved over the checkbox or its label.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 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 Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20716:
--------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.Beta1)
> 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
> Fix For: 4.3.1.Beta2
>
>
> 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)
10 years, 4 months
[JBoss JIRA] (JBIDE-20731) Finish button in Import OpenShift Application wizard does nothing if repo is already cloned
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20731?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20731:
--------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.3.1.Beta1)
> Finish button in Import OpenShift Application wizard does nothing if repo is already cloned
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-20731
> URL: https://issues.jboss.org/browse/JBIDE-20731
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Fix For: 4.3.1.Beta2
>
>
> Finish button in OpenShift 3 Import OpenShift Application wizard is enabled if the wizard is opened via context menu of a build config even though the repository is already cloned in default git location. This allows users to click on Finish button, but nothing happens. If Import OpenShift Application is opened via context menu of a project or connection or the build config in Import OpenShift Application is selected, then the Finish button for already cloned repositories of a build config is disabled.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months