July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-49) Launch Configuration for Browser based applications [EBZ#486066]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-49?page=com.atlassian.jira.plugin.sys... ] Ilya Buziuk reassigned ERT-49: ------------------------------ Assignee: Ilya Buziuk > Launch Configuration for Browser based applications [EBZ#486066] > ---------------------------------------------------------------- > > Key: ERT-49 > URL: https://issues.jboss.org/browse/ERT-49 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-49) Launch Configuration for Browser based applications [EBZ#486066]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-49?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-49: ---------------------------- Story Points: 15 (was: 25) > Launch Configuration for Browser based applications [EBZ#486066] > ---------------------------------------------------------------- > > Key: ERT-49 > URL: https://issues.jboss.org/browse/ERT-49 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-177) Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-177?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-177: ----------------------------- Sprint: devex #114 May 2016, devex #116 June 2016 (was: devex #114 May 2016, devex #116 June 2016, devex #117 July 2016) > Selection and dependent functionality works wrong when a file is modified in JS Editor [EBZ#492998] > --------------------------------------------------------------------------------------------------- > > Key: ERT-177 > URL: https://issues.jboss.org/browse/ERT-177 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.8_RC1, General, bzira > Fix For: Neon (4.6) RC3 > > > Created attachment 261462 > Selection related errors > See the screenshot attached for illustration. > Steps for reproduce: > - Create a javascript file with a function and a call to that function. > - Try to invoke content assist: FAIL: no new function appears in CA proposals > - Save, close and open the file again. > - Try to invoke content assist: Now the new function appears in CA proposals > - Put some text (like just new lines or some statements between the function declaration and its call and select the function name in the declaration > - FAIL: See wrong text regions highlighted. > - Try to rename the function (with inline rename): FAIL: See the wrong places for the inline editing are highlighted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21580) TernError: No type found at the given position when invoking Open On for taglib definition

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21580?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-21580: --------------------------------- Sprint: devex #118 July 2016 (was: devex #117 July 2016) > TernError: No type found at the given position when invoking Open On for taglib definition > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21580 > URL: https://issues.jboss.org/browse/JBIDE-21580 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, upstream > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0.Beta2-v20160122-0528-B256 + Mobile Tooling + AngularJS > Oracle Java 1.8 > Fedora 22 64 bit > Reporter: Vlado Pakan > Assignee: Victor Rubezhny > Fix For: 4.4.x > > > 1. Create JSF 1.2 project > 2. Open inputUserName.jsp in VPE > 3. Hover over <%@ taglib uri="http://java.sun.com/jsf/core" > 4. Press Ctrl > ERROR: > {noformat} > tern.TernException: TernError: No type found at the given position. > 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: tern.TernException: TernError: No type found at the given position. > at tern.server.nodejs.NodejsTernHelper.makeRequest(NodejsTernHelper.java:86) > 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 > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-49) Launch Configuration for Browser based applications [EBZ#486066]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-49?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-49: ---------------------------- Sprint: devex #118 July 2016 (was: devex #117 July 2016) > Launch Configuration for Browser based applications [EBZ#486066] > ---------------------------------------------------------------- > > Key: ERT-49 > URL: https://issues.jboss.org/browse/ERT-49 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: Debug, bzira > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-48) Support Chromium based browser debugging [EBZ#486065]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-48?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-48: ---------------------------- Sprint: (was: devex #117 July 2016) > Support Chromium based browser debugging [EBZ#486065] > ----------------------------------------------------- > > Key: ERT-48 > URL: https://issues.jboss.org/browse/ERT-48 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: Debug, bzira > > JSDT Should support running Chromium based browser in debug mode and start debug session for it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-89) Spike for changes on JSDT Search

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-89?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan resolved ERT-89. ----------------------------- Resolution: Done > Spike for changes on JSDT Search > -------------------------------- > > Key: ERT-89 > URL: https://issues.jboss.org/browse/ERT-89 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Gorkem Ercan > Assignee: Angel Misevski > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Figure out the action plan for search after the new parser -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-321) JavaScript as-you-type validation shouldn't appear for non-jJSDT projects [EBZ#491637]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-321?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-321: ----------------------------- Sprint: devex #118 July 2016 (was: devex #117 July 2016) > JavaScript as-you-type validation shouldn't appear for non-jJSDT projects [EBZ#491637] > -------------------------------------------------------------------------------------- > > Key: ERT-321 > URL: https://issues.jboss.org/browse/ERT-321 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > > JavaScript as-you-type validation works even if a project doesn't have a JSDT nature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-221) Exception when debugging with chromium [EBZ#494731]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-221?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-221: ----------------------------- Sprint: devex #116 June 2016, devex #118 July 2016 (was: devex #116 June 2016, devex #117 July 2016) > Exception when debugging with chromium [EBZ#494731] > --------------------------------------------------- > > Key: ERT-221 > URL: https://issues.jboss.org/browse/ERT-221 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: 3.8_RC3, Debug, bzira > Fix For: Neon (4.6) RC3 > > > Using EPP JavaScript RC2 package, using "Debug As > Node.js application" on some random file. > This error seems to happen whenever the program is interrupted, for example because a dependency doesn't compile or whatever. > Such remote interruption can happen pretty often, the shouldn't be treated as IDE error, but rather caught and presented to the user. Currently, it's logged in the IDE, and AERI suggests to open a ticket for that despite there is nothing wrong in the IDE. This gives an impression that debugger has bugs and this is going to flood AERI with no fair reason. > -- > eclipse.buildId=4.6.0.I20160519-1730 > java.version=1.8.0_77 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product org.eclipse.epp.package.javascript.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.javascript.product > org.eclipse.wst.jsdt.chromium.debug.core > Error > Fri May 27 11:23:55 CEST 2016 > SDK:org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection: Exception in message listener > java.lang.IllegalStateException: Connection not attached > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.checkAttached(SocketConnection.java:455) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection.send(SocketConnection.java:416) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$V8CommandOutputImpl.send(StandaloneVmImpl.java:249) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:133) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.send(V8CommandProcessor.java:1) > at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.send(BaseCommandProcessor.java:75) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.sendV8CommandAsync(V8CommandProcessor.java:84) > at org.eclipse.wst.jsdt.chromium.internal.v8native.DebugSession.sendMessageAsync(DebugSession.java:101) > at org.eclipse.wst.jsdt.chromium.internal.v8native.processor.AfterCompileProcessor.messageReceived(AfterCompileProcessor.java:44) > at org.eclipse.wst.jsdt.chromium.internal.v8native.DefaultResponseHandler.handleResponseWithHandler(DefaultResponseHandler.java:60) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:145) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor$HandlerImpl.acceptNonSeq(V8CommandProcessor.java:1) > at org.eclipse.wst.jsdt.chromium.internal.BaseCommandProcessor.processIncoming(BaseCommandProcessor.java:112) > at org.eclipse.wst.jsdt.chromium.internal.v8native.V8CommandProcessor.processIncomingJson(V8CommandProcessor.java:115) > at org.eclipse.wst.jsdt.chromium.internal.standalonev8.StandaloneVmImpl$4.messageReceived(StandaloneVmImpl.java:116) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$RegularMessageItem.report(SocketConnection.java:122) > at org.eclipse.wst.jsdt.chromium.internal.transport.SocketConnection$ResponseDispatcherThread.run(SocketConnection.java:211) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-197) JSON editor needs to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-197?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-197: ----------------------------- Sprint: devex #116 June 2016 (was: devex #116 June 2016, devex #117 July 2016) > JSON editor needs to use original minimal-json library instead of supporting org.eclipse.json plug-in [EBZ#494045] > ------------------------------------------------------------------------------------------------------------------ > > Key: ERT-197 > URL: https://issues.jboss.org/browse/ERT-197 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Priority: Trivial > Labels: bzira, wst.json > > The reason why org.eclipse.json (a modified copy of minimal-json library https://github.com/ralfstx/minimal-json) was the lack of information on offsets for tokens. > As issue https://github.com/ralfstx/minimal-json/issues/17 is fixed in original minimal-json library, probably we can request the adding of original minimal-json library to the Orbit bundle and depend on it instead of supporting its modified copy in org.eclipse.json plug-in. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016