February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21620) Intermitent issue - the tooltip displayed for an error (in the error log) is sometimes displayed as grey text on a black background - difficult to read

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21620?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21620: ----------------------------------- Component/s: upstream > Intermitent issue - the tooltip displayed for an error (in the error log) is sometimes displayed as grey text on a black background - difficult to read > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21620 > URL: https://issues.jboss.org/browse/JBIDE-21620 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: gwt, upstream > Affects Versions: 4.3.1.Beta2 > Environment: JBoss Developer Studio > Version: 9.1.0.Beta2 > Build id: Beta2-v20160127-2213-B262 > Build date: 20160127-2213 > RHEL7 > Reporter: Len DiMaggio > Attachments: Intermittent.png > > > Steps to reproduce: > If there are multiple errors displayed in the error log, hovering over one message, and then another, can sometimes result in the message box displaying the error as grey text on a black background - very difficult to read. > See attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21616 at 2/1/16 4:31 PM: ------------------------------------------------------------------ I bet this is only GTK3, right? This remembers me JBIDE-16877 where we also had to relayout the parent to correct the vertical size of the combos was (Author: adietish): I bet this is only GTK3, right? This remembers me JBIDE-16877 > Main tab for CDK launch configuration is not whole by default > ------------------------------------------------------------- > > Key: JBIDE-21616 > URL: https://issues.jboss.org/browse/JBIDE-21616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: Fedora 22, GTK3 > Reporter: Marián Labuda > Attachments: after.png, before.png > > > In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available. > !before.png! > After switching to Environment tab and back, Working directory and Arguments widgets become available. > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21616: ------------------------------------------ [~snjeza] can you please confirm the findings? This looks very much like an issue in GTK3 again, I bet we should file a bugzilla. [~mlabuda] can you please file this to Eclipse bugzilla for SWT/GTK3? > Main tab for CDK launch configuration is not whole by default > ------------------------------------------------------------- > > Key: JBIDE-21616 > URL: https://issues.jboss.org/browse/JBIDE-21616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: Fedora 22, GTK3 > Reporter: Marián Labuda > Attachments: after.png, before.png > > > In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available. > !before.png! > After switching to Environment tab and back, Working directory and Arguments widgets become available. > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21616: ------------------------------------- It displays fine on OSX > Main tab for CDK launch configuration is not whole by default > ------------------------------------------------------------- > > Key: JBIDE-21616 > URL: https://issues.jboss.org/browse/JBIDE-21616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: Fedora 22, GTK3 > Reporter: Marián Labuda > Attachments: after.png, before.png > > > In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available. > !before.png! > After switching to Environment tab and back, Working directory and Arguments widgets become available. > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21616: ------------------------------------------ I bet this is only GTK3, right? This remembers me JBIDE-16877 > Main tab for CDK launch configuration is not whole by default > ------------------------------------------------------------- > > Key: JBIDE-21616 > URL: https://issues.jboss.org/browse/JBIDE-21616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: Fedora 22, GTK3 > Reporter: Marián Labuda > Attachments: after.png, before.png > > > In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available. > !before.png! > After switching to Environment tab and back, Working directory and Arguments widgets become available. > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21617) Import wizard: Build config should be preselected if service in Explorer is selected

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21617?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-21617 at 2/1/16 4:26 PM: ------------------------------------------------------------- Alternative PR : https://github.com/jbosstools/jbosstools-openshift/pull/937 Only display BuildConfig selection when necessary. Only display relevant BuildConfigs when selecting a project Screencast http://screencast.com/t/6yiVDc1I9QfW was (Author: fbricon): Alternative PR : https://github.com/jbosstools/jbosstools-openshift/pull/937 Only display BuildConfig selection when necessary. Only display relevant BuildConfigs when selecting a project > Import wizard: Build config should be preselected if service in Explorer is selected > ------------------------------------------------------------------------------------ > > Key: JBIDE-21617 > URL: https://issues.jboss.org/browse/JBIDE-21617 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: explorer, import_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > When I am trying to import an OpenShift application via context menu of a service the Import OpenShift application wizard is opened, but first project is preselected in the wizard. It would be nice, if appropriate build config would be preselected if I have a selected service in OpenShift epxlorer view and opening Import OpenShift application wizard via its context menu. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-62: ---------------------------- Sprint: devex #1 February 2016 > Refactor JSDT Code Completion [EBZ#486776] > ------------------------------------------ > > Key: ERT-62 > URL: https://issues.jboss.org/browse/ERT-62 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions. > A proposal base for the code completion engine should include, but is not necessarily limited to: > - Keywords > - Identifiers (declared variables and functions in currently open JS file) > - Recently used methods of functions (currently open JS file as a bare minimum) > All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-62: ---------------------------- Story Points: 25 > Refactor JSDT Code Completion [EBZ#486776] > ------------------------------------------ > > Key: ERT-62 > URL: https://issues.jboss.org/browse/ERT-62 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions. > A proposal base for the code completion engine should include, but is not necessarily limited to: > - Keywords > - Identifiers (declared variables and functions in currently open JS file) > - Recently used methods of functions (currently open JS file as a bare minimum) > All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-36) Disable TypeBinding and deprecate internal ast model [EBZ#484598]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-36?page=com.atlassian.jira.plugin.sys... ] Victor Rubezhny updated ERT-36: ------------------------------- Fix Version/s: Neon (4.6) M6 (was: Neon (4.6) M5) > Disable TypeBinding and deprecate internal ast model [EBZ#484598] > ----------------------------------------------------------------- > > Key: ERT-36 > URL: https://issues.jboss.org/browse/ERT-36 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Labels: 3.8_M5, General, bzira > Fix For: Neon (4.6) M6 > > > Disable type binding to allow the replacement for a new Parser. > maintaining 2 ast models is wasteful deprecate org.eclipse.wst.jsdt.internal.compiler.ast model in favor of dom ast model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-62: ------------------------------- Assignee: Ian Stewart-Binks > Refactor JSDT Code Completion [EBZ#486776] > ------------------------------------------ > > Key: ERT-62 > URL: https://issues.jboss.org/browse/ERT-62 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ian Stewart-Binks > Labels: General, bzira > > The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions. > A proposal base for the code completion engine should include, but is not necessarily limited to: > - Keywords > - Identifiers (declared variables and functions in currently open JS file) > - Recently used methods of functions (currently open JS file as a bare minimum) > All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first. -- 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