February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21088) Implement grunt and gulp support

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21088?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-21088. -------------------------------- Resolution: Migrated to another ITS > Implement grunt and gulp support > -------------------------------- > > Key: JBIDE-21088 > URL: https://issues.jboss.org/browse/JBIDE-21088 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: nodejs > Reporter: Gorkem Ercan > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Implement a way to present and invoke tasks on a grunt/gulp file? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-66) Create Identifier Completion Engine

by Ian Stewart-Binks (JIRA)

Ian Stewart-Binks created ERT-66: ------------------------------------ Summary: Create Identifier Completion Engine Key: ERT-66 URL: https://issues.jboss.org/browse/ERT-66 Project: Eclipse Release Train Issue Type: Sub-task Reporter: Ian Stewart-Binks When a user invokes code completion, a set of useful identifier should be suggested to them. These identifiers should only be identifiers that are visible within the current scope from the current file. This should first support identifiers using ES5 keywords, and be extensible enough for ES6 keywords to fit in later on. Function identifiers from the current file and scope should be included as well. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21552) Core/General New and Noteworthy for 4.3.1.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21552?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21552: -------------------------------------- Resolution: (was: Rejected) Assignee: Alexey Kazakov (was: Rob Stryker) Reopened to mention Mars.2 in the N&N. > Core/General New and Noteworthy for 4.3.1.Beta2 > ----------------------------------------------- > > Key: JBIDE-21552 > URL: https://issues.jboss.org/browse/JBIDE-21552 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.1.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Core/General is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Core/General by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ] Len DiMaggio commented on TOOLSDOC-705: --------------------------------------- The information on the new features added for OpenShift v3 (http://docbuilder.usersys.redhat.com/23108/#New_Features_in_Beta2) look good. > JBDS 9.1 Beta2: Release Notes > ----------------------------- > > Key: TOOLSDOC-705 > URL: https://issues.jboss.org/browse/TOOLSDOC-705 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Martin Malina > > Create new Beta2 release notes, fix the script and update the relevant details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ] Len DiMaggio edited comment on TOOLSDOC-705 at 2/1/16 2:47 PM: --------------------------------------------------------------- The information on the new features added for OpenShift v3 (http://docbuilder.usersys.redhat.com/23108/#New_Features_in_Beta2) look good. If Martin and Marian agree - - this is good to go. was (Author: ldimaggio): The information on the new features added for OpenShift v3 (http://docbuilder.usersys.redhat.com/23108/#New_Features_in_Beta2) look good. > JBDS 9.1 Beta2: Release Notes > ----------------------------- > > Key: TOOLSDOC-705 > URL: https://issues.jboss.org/browse/TOOLSDOC-705 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Martin Malina > > Create new Beta2 release notes, fix the script and update the relevant details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-65) Create Keyword Completion Engine

by Ian Stewart-Binks (JIRA)

Ian Stewart-Binks created ERT-65: ------------------------------------ Summary: Create Keyword Completion Engine Key: ERT-65 URL: https://issues.jboss.org/browse/ERT-65 Project: Eclipse Release Train Issue Type: Sub-task Reporter: Ian Stewart-Binks When a user invokes code completion, a list of contextually practical keywords should be suggested. * After a user has typed a few characters and invoked code completion, keywords prefixed by those few characters should be suggested. For instance, if the user has just typed 'del', 'delete' should be suggested. Similarly, if the user has just typed 'd', all of the keywords that start with the letter 'd' should be suggested. * Keywords based on relevance should also be suggested. For instance, consider the case when a user has begun a *do while* block. If the user writes the *do* and the *block* and invokes code completion, *while(<CR>);* should be one of the suggestions. A similar functionality for an *if else* should be implemented, as well. Questions: * Should keywords that match templates be suggested even though their template counterpart is in the list of suggestions? * Should keywords be suggested within JSDocs? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[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 Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21620?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-21620: --------------------------------- Summary: 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 (was: Intermitent issue - the tooltip displayed for an error (in the error log) is sometimes dispalyed as grey text on a black background - difficult to read) > 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 > 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-21620) Intermitent issue - the tooltip displayed for an error (in the error log) is sometimes dispalyed as grey text on a black background - difficult to read

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21620?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-21620: --------------------------------- Attachment: Intermittent.png > Intermitent issue - the tooltip displayed for an error (in the error log) is sometimes dispalyed 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 > 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-21620) Intermitent issue - the tooltip displayed for an error (in the error log) is sometimes dispalyed as grey text on a black background - difficult to read

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-21620: ------------------------------------ Summary: Intermitent issue - the tooltip displayed for an error (in the error log) is sometimes dispalyed 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 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 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-21619) Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface".

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21619?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21619: ---------------------------------------- Looks like a duplicate of JBIDE-21613 > Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface". > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21619 > URL: https://issues.jboss.org/browse/JBIDE-21619 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > 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 > Java 1.8 > Reporter: Len DiMaggio > > To recreate the error: > 1) Create a new CDL server runtime - I used CDK2, Beta4 > 2) In the server explorer, start the server, and then left click on the running server > This message is generated: > Problems occurred when invoking code from plug-in: "org.eclipse.jface". > And, this exception is raised: > java.lang.NullPointerException > at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:53) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:111) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:188) > at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85) > at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:203) > at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144) > at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) > at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197) > at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228) > at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461) > at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257) > at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236) > at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) -- 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