April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22264) Tracing: Distinguish OpenShift versions on Tracing preference page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22264: ------------------------------------- Labels: openshift_v2 openshift_v3 tracing (was: openshift_v2 openshift_v3) > Tracing: Distinguish OpenShift versions on Tracing preference page > ------------------------------------------------------------------ > > Key: JBIDE-22264 > URL: https://issues.jboss.org/browse/JBIDE-22264 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v2, openshift_v3, tracing > Fix For: 4.4.0.Alpha2 > > > On preference page Tracing there are OpenShift plugin to trace. At the moment plugins are not distinguished and if user does not know that \*express\* is related to OpenShift 2 he can be lost. It would be nice if plugins could be spotted distinct on first sight. In the tree on the preference page are at the moment tree items "OpenShift client" for both. It could be "OpenShift 2 client" and "OpenShift 3 client". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22264) Distinguish OpenShift versions on Tracing preference page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22264: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 > Distinguish OpenShift versions on Tracing preference page > --------------------------------------------------------- > > Key: JBIDE-22264 > URL: https://issues.jboss.org/browse/JBIDE-22264 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > On preference page Tracing there are OpenShift plugin to trace. At the moment plugins are not distinguished and if user does not know that \*express\* is related to OpenShift 2 he can be lost. It would be nice if plugins could be spotted distinct on first sight. In the tree on the preference page are at the moment tree items "OpenShift client" for both. It could be "OpenShift 2 client" and "OpenShift 3 client". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22264) Distinguish OpenShift versions on Tracing preference page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22264: ------------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Distinguish OpenShift versions on Tracing preference page > --------------------------------------------------------- > > Key: JBIDE-22264 > URL: https://issues.jboss.org/browse/JBIDE-22264 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > On preference page Tracing there are OpenShift plugin to trace. At the moment plugins are not distinguished and if user does not know that \*express\* is related to OpenShift 2 he can be lost. It would be nice if plugins could be spotted distinct on first sight. In the tree on the preference page are at the moment tree items "OpenShift client" for both. It could be "OpenShift 2 client" and "OpenShift 3 client". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22263) Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22263?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22263: ------------------------------------------ [~mlabuda]I feel like being able to reset individual vars is still usefull. I therefore think that we should add an additional button to reset all env vars, keeping the existing one as is. Same's true for the next page where I think that we should have both possibilities (reset single, reset all). We could also have a single button but reset based on a selection. > Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22263 > URL: https://issues.jboss.org/browse/JBIDE-22263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: deploy_, deploy_docker_wizard, docker, openshift_v3 > > In Deploy Image to OpenShift wizard on the wizard page containing environment variables there is a Reset button. At the moment reset works only for one environment variable at the moment. It would be nice, if reset would set all environment variables (whole table) to default state. Currently the next wizard page containing ports mapping behave in desired way (reset set ports to default values), therefore it would be nice to have it consistent across wizard pages which are next to each other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22263) Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22263?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22263: ------------------------------------- Summary: Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars (was: Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars) > Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22263 > URL: https://issues.jboss.org/browse/JBIDE-22263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: deploy_, deploy_docker_wizard, docker, openshift_v3 > > In Deploy Image to OpenShift wizard on the wizard page containing environment variables there is a Reset button. At the moment reset works only for one environment variable at the moment. It would be nice, if reset would set all environment variables (whole table) to default state. Currently the next wizard page containing ports mapping behave in desired way (reset set ports to default values), therefore it would be nice to have it consistent across wizard pages which are next to each other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22263) Deploy Image Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22263?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22263: ------------------------------------- Summary: Deploy Image Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars (was: Reset button on Deployment Configuration wizard page in Deploy Image to OpenShift wizard could reset all env. vars) > Deploy Image Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22263 > URL: https://issues.jboss.org/browse/JBIDE-22263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: deploy_, deploy_docker_wizard, docker, openshift_v3 > > In Deploy Image to OpenShift wizard on the wizard page containing environment variables there is a Reset button. At the moment reset works only for one environment variable at the moment. It would be nice, if reset would set all environment variables (whole table) to default state. Currently the next wizard page containing ports mapping behave in desired way (reset set ports to default values), therefore it would be nice to have it consistent across wizard pages which are next to each other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22263) Deploy Image Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22263?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22263: ------------------------------------- Labels: deploy_ deploy_docker_wizard docker openshift_v3 (was: docker openshift_v3) > Deploy Image Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22263 > URL: https://issues.jboss.org/browse/JBIDE-22263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: deploy_, deploy_docker_wizard, docker, openshift_v3 > > In Deploy Image to OpenShift wizard on the wizard page containing environment variables there is a Reset button. At the moment reset works only for one environment variable at the moment. It would be nice, if reset would set all environment variables (whole table) to default state. Currently the next wizard page containing ports mapping behave in desired way (reset set ports to default values), therefore it would be nice to have it consistent across wizard pages which are next to each other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22263) Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22263?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22263: ------------------------------------- Summary: Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars (was: Deploy Image Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars) > Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset all env. vars > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22263 > URL: https://issues.jboss.org/browse/JBIDE-22263 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: deploy_, deploy_docker_wizard, docker, openshift_v3 > > In Deploy Image to OpenShift wizard on the wizard page containing environment variables there is a Reset button. At the moment reset works only for one environment variable at the moment. It would be nice, if reset would set all environment variables (whole table) to default state. Currently the next wizard page containing ports mapping behave in desired way (reset set ports to default values), therefore it would be nice to have it consistent across wizard pages which are next to each other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21411) v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21411?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21411. --------------------------------- Verified in JBDS 10.0.0.Alpha1 B5240. > v3 (Template) Application wizard: error markers for missing content should be consistent with rest of OpenShift tooling > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21411 > URL: https://issues.jboss.org/browse/JBIDE-21411 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: edit-template-parameter-value.png, required-value-decoration.png > > > # ASSERT: make sure that you have a connection to a v3 OpenShift server > # EXEC: in OpenShift explorer: pick "New"->"Application" from the context menu of your v3 connection > # ASSERT: new application wizard pops up, listing your project > # EXEC: unfold your project to get a listing of the available templates and pick on. Hit "Next" > # EXEC: in "Template Parameters" wizard page: select an entry without value and hit "Edit" > # ASSERT: editing dialog pops up > Result: > !edit-template-parameter-value.png! > "OK" button is enabled even though I didnt change anything. There isnt any decoration to the text field either that would require me to provide a value? > # EXEC: provide some value and back in the wizard page hit "Next" > # ASSERT: "Resource Labels" page shows up. > # EXEC: Hit "Add" > # ASSERT: dialog pops up so that I can create a new label > Result: > !required-value-decoration.png! > The dialog decorates missing values with a red error marker. > In OpenShift tooling we usually use "*" when required values are missing, not the error icon. > Notice also the 2 additional error-decorations that are shown (there are 4 error decorations while we should have 2 only) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22264) Distinguish OpenShift versions on Tracing preference page

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22264: ---------------------------------- Description: On preference page Tracing there are OpenShift plugin to trace. At the moment plugins are not distinguished and if user does not know that \*express\* is related to OpenShift 2 he can be lost. It would be nice if plugins could be spotted distinct on first sight. In the tree on the preference page are at the moment tree items "OpenShift client" for both. It could be "OpenShift 2 client" and "OpenShift 3 client". (was: On preference page Tracing there are OpenShift plugin to trace. At the moment plugins are not distinguished and if user does not know that *express* is related to OpenShift 2 he can be lost. It would be nice if plugins could be spotted distinct on first sight. In the tree on the preference page are at the moment tree items "OpenShift client" for both. It could be "OpenShift 2 client" and "OpenShift 3 client".) > Distinguish OpenShift versions on Tracing preference page > --------------------------------------------------------- > > Key: JBIDE-22264 > URL: https://issues.jboss.org/browse/JBIDE-22264 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v2, openshift_v3 > > On preference page Tracing there are OpenShift plugin to trace. At the moment plugins are not distinguished and if user does not know that \*express\* is related to OpenShift 2 he can be lost. It would be nice if plugins could be spotted distinct on first sight. In the tree on the preference page are at the moment tree items "OpenShift client" for both. It could be "OpenShift 2 client" and "OpenShift 3 client". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016