April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-140) Hovering over variables does not work in JSDT editor while V8 debugging [EBZ#492027]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-140?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk resolved ERT-140. ----------------------------- Resolution: Done > Hovering over variables does not work in JSDT editor while V8 debugging [EBZ#492027] > ------------------------------------------------------------------------------------ > > Key: ERT-140 > URL: https://issues.jboss.org/browse/ERT-140 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Gorkem Ercan > Labels: Debug, bzira > > Nothing happens while hovering over variables in JSDT editor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22264: ----------------------------------- Assignee: Viacheslav Kabanovich Resolution: Done PR merged in master > 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: Task > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > 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) Tracing: Distinguish OpenShift versions on Tracing preference page

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22264: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.0.Alpha2) Story Points: 1 Sprint: devex #113 April 2016 > 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: Task > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v2, openshift_v3, tracing > Fix For: 4.4.0.Alpha1 > > > 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) Tracing: Distinguish OpenShift versions on Tracing preference page

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22264: -------------------------------- Issue Type: Task (was: Enhancement) > 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: Task > 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) Tracing: Distinguish OpenShift versions on Tracing preference page

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22264: -------------------------------- Priority: Minor (was: Major) > 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: Task > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > 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-22118) Application wizard: Should support "builder" images

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22118?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22118: -------------------------------- Labels: new_and_noteworthy (was: ) > Application wizard: Should support "builder" images > --------------------------------------------------- > > Key: JBIDE-22118 > URL: https://issues.jboss.org/browse/JBIDE-22118 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Jeff Cantrill > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > Attachments: buildconfig page.png, page_1.png > > > I installed the following image stream: https://raw.githubusercontent.com/jboss-openshift/application-templates/m... > It contains several "builder" images. I would like to use jboss-eap70-openshift:1.3-Beta to build a JavaEE 7 application available at https://github.com/redhat-helloworld-msa/hello . But the Openshift plugin only shows "templates". > Openshift plugin should support "builder" images. These images contain "builder" on their tags. > Ref: Jan-5-2016 discussion: http://etherpad.corp.redhat.com/OpenShiftAndJBossStudio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22264?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22264: ----------------------------------------------- [~fbricon], please take a look at the pull request. > 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-22263) Deploy Docker Wizard: Reset button on Deployment Configuration wizard page in Deploy Image could reset ALL env. vars

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22263?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22263: ----------------------------------------------- [~adietish], [~fbricon], please take a look at the pull request. > 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 > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: EnvVarsEnhancement.png > > > 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] (TOOLSDOC-734) migrate docs from old URL to new one

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-734?page=com.atlassian.jira.plug... ] Nick Boldt updated TOOLSDOC-734: -------------------------------- Project: Documentation for JBoss Tools and Developer Studio (was: Developer Studio (JBoss Developer Studio)) Key: TOOLSDOC-734 (was: JBDS-3870) Issue Type: Task (was: Feature Request) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Component/s: General documentation issues (was: documentation) Target Release: (was: 10.0.0.GA) Affects Version/s: 9.0.0 (was: 10.0.0.Alpha1) > migrate docs from old URL to new one > ------------------------------------ > > Key: TOOLSDOC-734 > URL: https://issues.jboss.org/browse/TOOLSDOC-734 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: General documentation issues > Affects Versions: 9.0.0 > Reporter: Nick Boldt > > Currently, we host doc here [1],[2],[3] (which all redirect to [4]), but as part of the rebranding we should move the docs to a new URL [5] and set up a URL redirect so people with the old bookmark can find the new content. > [1] https://access.redhat.com/knowledge/docs/Red_Hat_JBoss_Developer_Studio/ > [2] https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/ > [3] https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > [4] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio/ > [5] https://access.redhat.com/documentation/en/red-hat-developer-studio/ -- 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 Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22263?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22263 at 4/28/16 1:52 PM: ------------------------------------------------------------------------ There is a couple of points that can be fixed and enhanced. 1. Added env var is not selected. Edited/reset env var looses selection. 2. User cannot see which env vars he added, and which values he edited. I suggest to select to set background to added/edited values to a light grey color. 3. Implementing (2) will allow to enable buttons 'Reset' and 'Reset All' only when there is something they can change. 4. When 'Edit Environment Variable' is opened with uneditable Name field, it has cursor which unnecessary makes user to change focus to value. Value field in this case should be initially focused and value selected. Screenshot EnvVarsEnhancement.png illustrates points (2) and (3): - Line 'n141 yyyyy' is all grey, because I added this env var, - Line 'n13 v13xxxxx' has grey value cell because it is edited, - Button Reset is disabled because value in line 'n11 v11' is not edited, - Button 'Reset All' is enabled because there is an edited value (in line 'n13 v13xxxxx') was (Author: scabanovich): There is a couple of points that can be fixed and enhanced. 1. Added env var is not selected. Edited/reset env var looses selection. 2. User cannot see which env vars he added, and which values he edited. I suggest to select to set background to added/edited values to a light grey color. 3. Implementing (2) will allow to enable buttons 'Reset' and 'Reset All' only when there is something they can change. 4. When 'Edit Environment Variable' is opened with uneditable Name field, it has cursor which unnecessary makes user to change focus to value. Value field in this case should be initially focused and value selected. > 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 > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > Attachments: EnvVarsEnhancement.png > > > 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

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