June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24539: ------------------------------------- Labels: explorer openshift_v2 openshift_v3 properties (was: ) > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.AM2 > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24539?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24539: ------------------------------------- Fix Version/s: 4.5.0.AM2 > Explorer, Properties: User should be able to see what OpenShift version a connection is > --------------------------------------------------------------------------------------- > > Key: JBIDE-24539 > URL: https://issues.jboss.org/browse/JBIDE-24539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Andre Dietisheim > Labels: explorer, openshift_v2, openshift_v3, properties > Fix For: 4.5.0.AM2 > > Attachments: image-2017-06-06-11-54-02-000.png > > > steps: > # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively > # EXEC: look at the entries in the explorer and in the Properties view > Result: > !image-2017-06-06-11-54-02-000.png! > You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24539) Explorer, Properties: User should be able to see what OpenShift version a connection is

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24539: ---------------------------------------- Summary: Explorer, Properties: User should be able to see what OpenShift version a connection is Key: JBIDE-24539 URL: https://issues.jboss.org/browse/JBIDE-24539 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.0.AM1 Reporter: Andre Dietisheim Attachments: image-2017-06-06-11-54-02-000.png steps: # ASSERT: have a connection to an OpenShift 3 and an OpenShift 2 server respectively # EXEC: look at the entries in the explorer and in the Properties view Result: !image-2017-06-06-11-54-02-000.png! You have no idea about the versions of the OpenShift servers of the connections that you have. You may only figure out implicitly by the "Domains" displayed in the properties for the OpenShift 2 connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21448) Port Forwarding: Allow port-forwarding of ports not defined on pod metadata

by Jiri Pechanec (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21448?page=com.atlassian.jira.plugi... ] Jiri Pechanec commented on JBIDE-21448: --------------------------------------- {noformat} docker inspect registry.access.redhat.com/jboss-eap-7/eap70-openshift "ExposedPorts": { "8080/tcp": {}, "8443/tcp": {}, "8778/tcp": {} }, {noformat} But if you run the pod with EAP it has management port available bound on localhost - port 9990. It is useful to be able to easily port-forward to such port too > Port Forwarding: Allow port-forwarding of ports not defined on pod metadata > --------------------------------------------------------------------------- > > Key: JBIDE-21448 > URL: https://issues.jboss.org/browse/JBIDE-21448 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jiri Pechanec > Priority: Critical > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.5.0.AM2 > > > Some of the pods have services that are available via ports that are not defined in pod template. It is useful to have an option to port-forward such ports too. > And example is EAP CLI -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers 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: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM2) > Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers 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.5.x > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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 (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers 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: ------------------------------------- Summary: Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers usage of default server (was: Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server) > Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers 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.5.0.AM2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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 (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers 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: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 triggers 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.5.0.AM2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > 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 (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20730: ------------------------------------- Labels: explorer openshift_v3 (was: ) > Displaying of a project in OpenShift Explorer view is not consistent > -------------------------------------------------------------------- > > Key: JBIDE-20730 > URL: https://issues.jboss.org/browse/JBIDE-20730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > Fix For: 4.5.0.AM2 > > > OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example: > Project 01 has name: project01 > Project 02 has name: project02 and displayName: projectName02 > In OpenShift Explorer view are those projects shown as > project01 > projectName02 (project02) > One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this: > project01 (project01) > projectName02 (project02) > because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20730: ------------------------------------- Story Points: 4 > Displaying of a project in OpenShift Explorer view is not consistent > -------------------------------------------------------------------- > > Key: JBIDE-20730 > URL: https://issues.jboss.org/browse/JBIDE-20730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > Fix For: 4.5.0.AM2 > > > OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example: > Project 01 has name: project01 > Project 02 has name: project02 and displayName: projectName02 > In OpenShift Explorer view are those projects shown as > project01 > projectName02 (project02) > One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this: > project01 (project01) > projectName02 (project02) > because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20730: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Displaying of a project in OpenShift Explorer view is not consistent > -------------------------------------------------------------------- > > Key: JBIDE-20730 > URL: https://issues.jboss.org/browse/JBIDE-20730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > Fix For: 4.5.0.AM2 > > > OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example: > Project 01 has name: project01 > Project 02 has name: project02 and displayName: projectName02 > In OpenShift Explorer view are those projects shown as > project01 > projectName02 (project02) > One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this: > project01 (project01) > projectName02 (project02) > because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

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 June 2017