February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21753) Explorer: connection name overlaps its icon until expanded with GTK3

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21753?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21753: --------------------------------------- It is reproducible with GTK 3.16 in the way you have described, but isn't with GTK 3.14 and 3.18. We could refresh the Openshift Explorer view (when it is opened) using the earlyStartup extension point, but I am not sure if such a patch would be acceptable because the issue happens only on some versions of GTK. [~adietish], [~jrichter1], [~maxandersen], What is your opinion about this? > Explorer: connection name overlaps its icon until expanded with GTK3 > -------------------------------------------------------------------- > > Key: JBIDE-21753 > URL: https://issues.jboss.org/browse/JBIDE-21753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Assignee: Snjezana Peco > Priority: Minor > Labels: gtk3 > Fix For: 4.4.0.Alpha1 > > Attachments: connection.png, explorer-view-connections.png > > > This is what the explorer looks like when I start up the tooling with GTK3: > !connection.png|thumbnail! > Expanding the connection will shift the text to its proper position. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21776: ---------------------------------- Attachment: selected_image.png > Cannot deploy docker image to OpenShift with manually entered details > --------------------------------------------------------------------- > > Key: JBIDE-21776 > URL: https://issues.jboss.org/browse/JBIDE-21776 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Attachments: manually_filled.png, selected_image.png > > > When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). > There is no error in error log. > Manually filled in details screenshot: > !manually_filled.png! > Automatically filled details via selecting a specific image screenshot: > !selected_image.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21776: ---------------------------------- Attachment: (was: via_search.png) > Cannot deploy docker image to OpenShift with manually entered details > --------------------------------------------------------------------- > > Key: JBIDE-21776 > URL: https://issues.jboss.org/browse/JBIDE-21776 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Attachments: manually_filled.png, selected_image.png > > > When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). > There is no error in error log. > Manually filled in details screenshot: > !manually_filled.png! > Automatically filled details via selecting a specific image screenshot: > !selected_image.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21776: ---------------------------------- Description: When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). There is no error in error log. Manually filled in details screenshot: !manually_filled.png! Automatically filled details via selecting a specific image screenshot: !selected_image.png! was: When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). There is no error in error log. Manually filled in details screenshot: !manually_filled.png! Automatically filled details via selecting a specific image screenshot: !via_search.png! > Cannot deploy docker image to OpenShift with manually entered details > --------------------------------------------------------------------- > > Key: JBIDE-21776 > URL: https://issues.jboss.org/browse/JBIDE-21776 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Attachments: manually_filled.png, selected_image.png > > > When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). > There is no error in error log. > Manually filled in details screenshot: > !manually_filled.png! > Automatically filled details via selecting a specific image screenshot: > !selected_image.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21776: ---------------------------------- Description: When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). There is no error in error log. Manually filled in details screenshot: !manually_filled.png! Automatically filled details via selecting a specific image screenshot: !via_search.png! was: When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one. There is no error in error log. Manually filled in details screenshot: !manually_filled.png! Automatically filled details via selecting a specific image screenshot: !via_search.png! > Cannot deploy docker image to OpenShift with manually entered details > --------------------------------------------------------------------- > > Key: JBIDE-21776 > URL: https://issues.jboss.org/browse/JBIDE-21776 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Attachments: manually_filled.png, via_search.png > > > When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one). > There is no error in error log. > Manually filled in details screenshot: > !manually_filled.png! > Automatically filled details via selecting a specific image screenshot: > !via_search.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21776: ------------------------------------- Summary: Cannot deploy docker image to OpenShift with manually entered details Key: JBIDE-21776 URL: https://issues.jboss.org/browse/JBIDE-21776 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Attachments: manually_filled.png, via_search.png When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one. There is no error in error log. Manually filled in details screenshot: !manually_filled.png! Automatically filled details via selecting a specific image screenshot: !via_search.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21770) OpenShift 2 connection loading message is archaic

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21770?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21770. --------------------------------- Verified on latest nightly build of JBT with OpenShift tooling build B197. > OpenShift 2 connection loading message is archaic > ------------------------------------------------- > > Key: JBIDE-21770 > URL: https://issues.jboss.org/browse/JBIDE-21770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Minor > Labels: openshift_v2 > Fix For: 4.3.1.CR1 > > Attachments: progress_dialog.png > > > When loading OS2 connection there is sometimes progress dialog informing about loading of connection details. It has deprecated "ExpressConnection" message, probably it remained from times when there was OpenShift Express. > !progress_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21775) OpenShift 2 connection loading message is archaic

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21775: ------------------------------------- Summary: OpenShift 2 connection loading message is archaic Key: JBIDE-21775 URL: https://issues.jboss.org/browse/JBIDE-21775 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Assignee: Marián Labuda Priority: Minor Fix For: 4.3.1.CR1 When loading OS2 connection there is sometimes progress dialog informing about loading of connection details. It has deprecated "ExpressConnection" message, probably it remained from times when there was OpenShift Express. !progress_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21775) OpenShift 2 connection loading message is archaic

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21775?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21775: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > OpenShift 2 connection loading message is archaic > ------------------------------------------------- > > Key: JBIDE-21775 > URL: https://issues.jboss.org/browse/JBIDE-21775 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Minor > Labels: openshift_v2 > Fix For: 4.4.0.Alpha1 > > Attachments: progress_dialog.png > > > When loading OS2 connection there is sometimes progress dialog informing about loading of connection details. It has deprecated "ExpressConnection" message, probably it remained from times when there was OpenShift Express. > !progress_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21775) OpenShift 2 connection loading message is archaic

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21775?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21775. ----------------------------------- Resolution: Done > OpenShift 2 connection loading message is archaic > ------------------------------------------------- > > Key: JBIDE-21775 > URL: https://issues.jboss.org/browse/JBIDE-21775 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Marián Labuda > Priority: Minor > Labels: openshift_v2 > Fix For: 4.4.0.Alpha1 > > Attachments: progress_dialog.png > > > When loading OS2 connection there is sometimes progress dialog informing about loading of connection details. It has deprecated "ExpressConnection" message, probably it remained from times when there was OpenShift Express. > !progress_dialog.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2016