March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-114) JSON Preference page throws exceptions [EBZ#487377]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-114?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-114: ----------------------------- Sprint: devex #5 April 2016 > JSON Preference page throws exceptions [EBZ#487377] > --------------------------------------------------- > > Key: ERT-114 > URL: https://issues.jboss.org/browse/ERT-114 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: 3.8_M7, bzira, wst.json > Fix For: Neon (4.6) M7 > > > The following exception is thrown while selecting the "Editor" child node under JSON in the preference wizard. > Testing Neon M5 driver. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-99) [ES6] Update ECMA libraries to ES6 [EBZ#488912]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-99?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-99: ---------------------------- Sprint: devex #5 April 2016 > [ES6] Update ECMA libraries to ES6 [EBZ#488912] > ----------------------------------------------- > > Key: ERT-99 > URL: https://issues.jboss.org/browse/ERT-99 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > Update the built-in ECMA libraries to their latest level. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-90) Spike for refactoring and code manipulation

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-90?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-90: ---------------------------- Sprint: devex #5 April 2016 > Spike for refactoring and code manipulation > ------------------------------------------- > > Key: ERT-90 > URL: https://issues.jboss.org/browse/ERT-90 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Gorkem Ercan > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Figure out what to do for refactoring and code manipulation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-115) Create a common plugin for node.js plugins [EBZ#489148]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-115?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-115: ----------------------------- Sprint: devex #5 April 2016 > Create a common plugin for node.js plugins [EBZ#489148] > ------------------------------------------------------- > > Key: ERT-115 > URL: https://issues.jboss.org/browse/ERT-115 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > > Create a common plugin containing common utilities, etc. that can be reused by the different node.js plugins -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-91) bower dependency content assist is broken [EBZ#487888]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-91?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-91: ---------------------------- Sprint: devex #5 April 2016 > bower dependency content assist is broken [EBZ#487888] > ------------------------------------------------------ > > Key: ERT-91 > URL: https://issues.jboss.org/browse/ERT-91 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: 3.8_M7, bzira, wst.json > Fix For: Neon (4.6) M7 > > > The content assist has stopped working for me and started to constantly throw the exceptions (see below). The problem might be occurring because either the URL that is used to get the dependency proposals has stopped working or the site was/is just shut down for some purpose. > But anyway, probably just the displaying such a stack trace in the console is not a proper way to notify a user on the problem. We should properly log it into the Error Log instead. > The stack trace appearing in the console: > !ENTRY org.eclipse.wst.json.ui 4 4 2016-02-16 06:51:31.376 > !MESSAGE org.eclipse.json.provisonnal.com.eclipsesource.json.ParseException: Expected value at 1:0 > !STACK 0 > java.io.IOException: org.eclipse.json.provisonnal.com.eclipsesource.json.ParseException: Expected value at 1:0 > at org.eclipse.json.http.HttpHelper.makeRequest(HttpHelper.java:74) > at org.eclipse.wst.json.ui.contentassist.HttpCompletionProposalCollector.addProposals(HttpCompletionProposalCollector.java:28) > at org.eclipse.wst.json.ui.internal.contentassist.CompletionProposalMatcher.addProposalsIfMatch(CompletionProposalMatcher.java:42) > at org.eclipse.wst.json.ui.internal.contentassist.CompletionProposalCollectorsRegistryReader.addProposals(CompletionProposalCollectorsRegistryReader.java:62) > at org.eclipse.wst.json.ui.internal.contentassist.JSONCompletionProposalComputer.collectProposalsFromExtensionPoint(JSONCompletionProposalComputer.java:56) > at org.eclipse.wst.json.ui.internal.contentassist.JSONCompletionProposalComputer.addObjectKeyProposals(JSONCompletionProposalComputer.java:43) > at org.eclipse.wst.json.ui.contentassist.AbstractJSONCompletionProposalComputer.computeObjectKeyProposals(AbstractJSONCompletionProposalComputer.java:197) > at org.eclipse.wst.json.ui.contentassist.AbstractJSONCompletionProposalComputer.computeCompletionProposals(AbstractJSONCompletionProposalComputer.java:153) > at org.eclipse.wst.json.ui.contentassist.AbstractJSONCompletionProposalComputer.computeCompletionProposals(AbstractJSONCompletionProposalComputer.java:82) > at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284) > at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:290) > at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:484) > at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:255) > at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127) > at org.eclipse.jface.text.contentassist.ContentAssistant$5.run(ContentAssistant.java:1904) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1902) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499) > at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1720) > at org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOperation(StructuredTextViewer.java:488) > at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:122) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > 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:483) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:378) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:324) > at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1550) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1328) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1338) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1365) > at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:763) > at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3317) > at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:785) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1980) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:5590) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4717) > at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) > at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9279) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1225) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2425) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428) > 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:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > 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:483) > 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) > Caused by: org.eclipse.json.provisonnal.com.eclipsesource.json.ParseException: Expected value at 1:0 > at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.error(JsonParser.java:368) > at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.expected(JsonParser.java:361) > at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.readValue(JsonParser.java:97) > at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.parse(JsonParser.java:62) > at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonValue.readFrom(JsonValue.java:91) > at org.eclipse.json.http.HttpHelper.makeRequest(HttpHelper.java:70) > ... 87 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-87) Icons for JSON outline [EBZ#488606]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-87?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-87: ---------------------------- Sprint: devex #5 April 2016 > Icons for JSON outline [EBZ#488606] > ----------------------------------- > > Key: ERT-87 > URL: https://issues.jboss.org/browse/ERT-87 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: bzira, wst.json > > JSON editor's outline uses a single icon for all the nodes and it is the same icon as the editor's. We need different icons for JSON outlines. The icons should be different for different JSON node types (Object, Number, Boolean, String...) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-78) Improve the information shown while hovering over a variable during a JS debugging session [EBZ#487055]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-78?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-78: ---------------------------- Sprint: devex #4 March 2016, devex #5 April 2016 (was: devex #4 March 2016) > Improve the information shown while hovering over a variable during a JS debugging session [EBZ#487055] > ------------------------------------------------------------------------------------------------------- > > Key: ERT-78 > URL: https://issues.jboss.org/browse/ERT-78 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: 3.8_M6, Debug, bzira > Fix For: Neon (4.6) M7 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-96) Need to provide p2.inf to org.eclipse.wst.jsdt.nodejs.feature [EBZ#484810]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-96?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-96: ---------------------------- Sprint: devex #4 March 2016, devex #5 April 2016 (was: devex #4 March 2016) > Need to provide p2.inf to org.eclipse.wst.jsdt.nodejs.feature [EBZ#484810] > -------------------------------------------------------------------------- > > Key: ERT-96 > URL: https://issues.jboss.org/browse/ERT-96 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: General, bzira > > Originally npm / bower tools were located in the https://github.com/jbosstools/jbosstools-jst repository. Need to create p2 advice file to augment the metadata for an installable unit -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-93) gulp long-running task (e.g serve) can not be killed from eclipse console [EBZ#489041]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-93?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-93: ---------------------------- Sprint: devex #4 March 2016, devex #5 April 2016 (was: devex #4 March 2016) > gulp long-running task (e.g serve) can not be killed from eclipse console [EBZ#489041] > -------------------------------------------------------------------------------------- > > Key: ERT-93 > URL: https://issues.jboss.org/browse/ERT-93 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: General, bzira > > Long-running task (e.g serve) still locks the port after pressing "Terminate" button on Eclipse console. It looks like sending "exit" command to CLI does not kill the process -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-35) Launch configuration for node.js applications [EBZ#484597]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-35?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-35: ---------------------------- Sprint: devex #4 March 2016, devex #5 April 2016 (was: devex #4 March 2016) > Launch configuration for node.js applications [EBZ#484597] > ----------------------------------------------------------- > > Key: ERT-35 > URL: https://issues.jboss.org/browse/ERT-35 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Labels: 3.8_M7, Debug, bzira > Fix For: Neon (4.6) M7 > > > We need a launch configuration that can understand package.json file on a project and launch/debug a JS application on a local node.js instance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016