April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]

by Nick Boldt (JIRA)

Nick Boldt created ERT-132: ------------------------------ Summary: Need to create launch configuration for npm "scripts" [EBZ#491474] Key: ERT-132 URL: https://issues.jboss.org/browse/ERT-132 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e. all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-124) [ES6] Support for ES exports on Outline view [EBZ#489656]

by Nick Boldt (JIRA)

Nick Boldt created ERT-124: ------------------------------ Summary: [ES6] Support for ES exports on Outline view [EBZ#489656] Key: ERT-124 URL: https://issues.jboss.org/browse/ERT-124 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt Priority: Trivial Outline view should show the ES6 exports in a similar manner to imports. This task involves two parts. 1. Enhance IJavaScriptElement model to include Exports. Enhance CompilationUnit.buildStructure() to include exports. 2. Enhance the Outline viewer to show the exports. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-125) Need to add possibility to select debug port for Node.js launch [EBZ#490208]

by Nick Boldt (JIRA)

Nick Boldt created ERT-125: ------------------------------ Summary: Need to add possibility to select debug port for Node.js launch [EBZ#490208] Key: ERT-125 URL: https://issues.jboss.org/browse/ERT-125 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt Fix For: Neon (4.6) M7 For now node debug simply runs node.js app with debug flag. Triggering Chromium V8 debug launch is also required to perform on this step. For now there is no UI provided so 5858 port will be used -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-126) org.eclipse.wst.jsdt.nodejs.feature is missing node plugins [EBZ#490618]

by Nick Boldt (JIRA)

Nick Boldt created ERT-126: ------------------------------ Summary: org.eclipse.wst.jsdt.nodejs.feature is missing node plugins [EBZ#490618] Key: ERT-126 URL: https://issues.jboss.org/browse/ERT-126 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt Fix For: Neon (4.6) M7 The following plugins are absent in org.eclipse.wst.jsdt.nodejs.feature: - org.eclipse.wst.jsdt.js.node - org.eclipse.wst.jsdt.js.node.common -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-125) Need to add possibility to select debug port for Node.js launch [EBZ#490208]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-125?page=com.atlassian.jira.plugin.sy... ] Nick Boldt resolved ERT-125. ---------------------------- Resolution: Done > Need to add possibility to select debug port for Node.js launch [EBZ#490208] > ---------------------------------------------------------------------------- > > Key: ERT-125 > URL: https://issues.jboss.org/browse/ERT-125 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: 3.8_M7, Debug, bzira > Fix For: Neon (4.6) M7 > > > For now node debug simply runs node.js app with debug flag. Triggering Chromium V8 debug launch is also required to perform on this step. For now there is no UI provided so 5858 port will be used -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-126) org.eclipse.wst.jsdt.nodejs.feature is missing node plugins [EBZ#490618]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-126?page=com.atlassian.jira.plugin.sy... ] Nick Boldt resolved ERT-126. ---------------------------- Resolution: Done > org.eclipse.wst.jsdt.nodejs.feature is missing node plugins [EBZ#490618] > ------------------------------------------------------------------------ > > Key: ERT-126 > URL: https://issues.jboss.org/browse/ERT-126 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: 3.8_M7, General, bzira > Fix For: Neon (4.6) M7 > > > The following plugins are absent in org.eclipse.wst.jsdt.nodejs.feature: > - org.eclipse.wst.jsdt.js.node > - org.eclipse.wst.jsdt.js.node.common -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-127) Debugging should happen in JSDT editor if the project exist in workspace [EBZ#490626]

by Nick Boldt (JIRA)

Nick Boldt created ERT-127: ------------------------------ Summary: Debugging should happen in JSDT editor if the project exist in workspace [EBZ#490626] Key: ERT-127 URL: https://issues.jboss.org/browse/ERT-127 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt Fix For: Neon (4.6) M7 For now all debugging happens via Chromium JavaScript editor via virtual file system. However, if the target project exists in the workspace all debugging should happen in jsdt editor via real file system -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-130) TernException during code completion [EBZ#491237]

by Nick Boldt (JIRA)

Nick Boldt created ERT-130: ------------------------------ Summary: TernException during code completion [EBZ#491237] Key: ERT-130 URL: https://issues.jboss.org/browse/ERT-130 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt Im getting error an exception when using content assist on html5 file tern.TernException: 127.0.0.1:50063 failed to respond at tern.server.DefaultResponseHandler.getData(DefaultResponseHandler.java:45) at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:43) at tern.eclipse.ide.internal.core.resources.IDETernServerAsyncReqProcessor.run(IDETernServerAsyncReqProcessor.java:104) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: org.apache.http.NoHttpResponseException: 127.0.0.1:50063 failed to respond at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:143) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:260) at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:283) at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:251) at org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(ManagedClientConnectionImpl.java:197) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:271) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123) at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:685) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:487) at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:74) at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:163) at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127) at tern.server.protocol.TernResultsProcessorsFactory.makeRequestAndProcess(TernResultsProcessorsFactory.java:42) ... 2 more How to reproduce: 1. import this project http://mvnrepository.com/artifact/org.jboss.aerogear.archetypes/jboss-htm... 2. open src/main/webapp/index.html 3. try calling content assist and check error log -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-129) Gulp / Grunt tasks processing does not work with new Esprima parser [EBZ#490999]

by Nick Boldt (JIRA)

Nick Boldt created ERT-129: ------------------------------ Summary: Gulp / Grunt tasks processing does not work with new Esprima parser [EBZ#490999] Key: ERT-129 URL: https://issues.jboss.org/browse/ERT-129 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt gulp / grunt task processing should be adjusted to the new esprima parser. For now, only launch of the default task (on the gulpfile.js / gruntfile.js directly) is available - other tasks are not contributed to CNF. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-128) IllegalArgumentException in CompletionProposal.setReplaceRange(CompletionProposal.java:1114) [EBZ#490831]

by Nick Boldt (JIRA)

Nick Boldt created ERT-128: ------------------------------ Summary: IllegalArgumentException in CompletionProposal.setReplaceRange(CompletionProposal.java:1114) [EBZ#490831] Key: ERT-128 URL: https://issues.jboss.org/browse/ERT-128 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt An exception occurs when invoking content assist in HTML Editor on JavaScript code: java.lang.IllegalArgumentException: [LOCAL_VARIABLE_REF]{completion:test, declSign:, sign:, declKey:, key:, name:test, [0,0], relevance=1} at org.eclipse.wst.jsdt.core.CompletionProposal.setReplaceRange(CompletionProposal.java:1114) at org.eclipse.wst.jsdt.web.ui.internal.contentassist.JSDTProposalCollector.createJSDTProposal(JSDTProposalCollector.java:96) at org.eclipse.wst.jsdt.web.ui.internal.contentassist.JSDTProposalCollector.createJavaCompletionProposal(JSDTProposalCollector.java:87) at org.eclipse.wst.jsdt.ui.text.java.CompletionProposalCollector.accept(CompletionProposalCollector.java:221) at org.eclipse.wst.jsdt.internal.codeassist.DOMCompletionEngine$ScopedCodeAssistVisitor.endVisit(DOMCompletionEngine.java:82) at org.eclipse.wst.jsdt.core.dom.JavaScriptUnit.accept0(JavaScriptUnit.java:244) at org.eclipse.wst.jsdt.core.dom.ASTNode.accept(ASTNode.java:2424) at org.eclipse.wst.jsdt.internal.codeassist.DOMCompletionEngine.complete(DOMCompletionEngine.java:232) at org.eclipse.wst.jsdt.internal.core.Openable.codeComplete(Openable.java:143) at org.eclipse.wst.jsdt.internal.core.CompilationUnit.codeComplete(CompilationUnit.java:224) at org.eclipse.wst.jsdt.web.ui.internal.contentassist.JSDTContentAssistantProcessor.computeCompletionProposals(JSDTContentAssistantProcessor.java:90) at org.eclipse.wst.jsdt.web.ui.internal.contentassist.JSDTContentAssistant.computeCompletionProposals(JSDTContentAssistant.java:143) 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$3.run(ContentAssistant.java:1931) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1928) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:565) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:560) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:494) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:487) at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1747) at org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOperation(StructuredTextViewer.java:488) at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:84) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:81) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:118) 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:498) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) 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:494) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) 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:1545) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1338) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1365) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1377) 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:3462) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:819) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1988) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5832) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4865) 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:9501) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1226) 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:2480) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3576) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:692) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:605) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) 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:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) 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:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609) at org.eclipse.equinox.launcher.Main.run(Main.java:1516) at org.eclipse.equinox.launcher.Main.main(Main.java:1489) -- 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 April 2016