July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-338) [formatter] Unwanted alignment on Enter when inside array literal [EBZ#356606]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-338?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-338: ---------------------------- Fix Version/s: Neon.1 (4.6) (was: Future) > [formatter] Unwanted alignment on Enter when inside array literal [EBZ#356606] > ------------------------------------------------------------------------------ > > Key: ERT-338 > URL: https://issues.jboss.org/browse/ERT-338 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Future, General, bzira > Fix For: Neon.1 (4.6) > > > Eclipse 3.7 (I20110613-1736) > JSDT 1.3.0 (20110527214303) > WTP 3.3.0 (20100921193530) > 1. Create a new JavaScript file and add this code: > function() { > var myArray = []; > } > 2. Put the editing caret between the square brackets, and press Enter. > 3. You get > function() { > var myArray = [ > ]; > } > Inside array literals, pressing Enter causes the editor to insert spaces to align the new line with the opening [ bracket. I expected it to just increase the indentation level. > This happens when using a new workspace with all the default preference settings. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-142) JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-142?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk resolved ERT-142. ----------------------------- Resolution: Done > JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751] > -------------------------------------------------------------------- > > Key: ERT-142 > URL: https://issues.jboss.org/browse/ERT-142 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > > Created attachment 260976 > Doubled problems in Problem view > JavaScript Problems are doubling in Dynamic Web Projects (See the attached screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-142) JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-142?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-142: ---------------------------- Fix Version/s: Neon.1 (4.6) > JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751] > -------------------------------------------------------------------- > > Key: ERT-142 > URL: https://issues.jboss.org/browse/ERT-142 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > Fix For: Neon.1 (4.6) > > > Created attachment 260976 > Doubled problems in Problem view > JavaScript Problems are doubling in Dynamic Web Projects (See the attached screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22740) Show selection tag bar preferences does not work for VPV

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22740?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22740: -------------------------------- Story Points: 1 > Show selection tag bar preferences does not work for VPV > -------------------------------------------------------- > > Key: JBIDE-22740 > URL: https://issues.jboss.org/browse/JBIDE-22740 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.1.AM1 > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Priority: Minor > Fix For: 4.4.1.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22752) Remove SWT_GTK3=0 variable from tests pom

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22752?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-22752: -------------------------------- Story Points: 2 > Remove SWT_GTK3=0 variable from tests pom > ----------------------------------------- > > Key: JBIDE-22752 > URL: https://issues.jboss.org/browse/JBIDE-22752 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.1.AM2 > > > Tests do not work on RHEL7 machines because only v3 libwebkit is available but vpe tests pom.xml disables SWT_GTK3 by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-333) An internal error occurred during: "Requesting JavaScript AST from selection". [EBZ#496749]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-333?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk resolved ERT-333. ----------------------------- Resolution: Done > An internal error occurred during: "Requesting JavaScript AST from selection". [EBZ#496749] > ------------------------------------------------------------------------------------------- > > Key: ERT-333 > URL: https://issues.jboss.org/browse/ERT-333 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: 3.8.1, General, bzira > Fix For: Neon.1 (4.6) > > > OSX Fresh install of Neon, editing a relatively complex JavaScript file. > An internal error occurred during: "Requesting JavaScript AST from selection". > org.eclipse.wst.jsdt.internal.core.dom.binding.VariableBinding cannot be cast to org.eclipse.wst.jsdt.core.dom.IFunctionBinding > -- Configuration Details -- > Product: Eclipse 4.6.0.20160613-1800 (org.eclipse.epp.package.javascript.product) > Installed Features: > org.eclipse.platform 4.6.0.v20160606-1342 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-337) Need to switch to static parser for Web Inspector Protocol (front-end debugging) [EBZ#497532]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-337?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk resolved ERT-337. ----------------------------- Resolution: Done > Need to switch to static parser for Web Inspector Protocol (front-end debugging) [EBZ#497532] > --------------------------------------------------------------------------------------------- > > Key: ERT-337 > URL: https://issues.jboss.org/browse/ERT-337 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > Fix For: Neon.1 (4.6) > > > Currently dynamic parser model is used for from-end debugging (Web Inspector Protocol) which is incompatible with new versions of blink / chromium. Need to switch to static parser model which is claimed to have backward compatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-337) Need to switch to static parser for Web Inspector Protocol (front-end debugging) [EBZ#497532]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-337?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-337: ------------------------------- Assignee: Ilya Buziuk > Need to switch to static parser for Web Inspector Protocol (front-end debugging) [EBZ#497532] > --------------------------------------------------------------------------------------------- > > Key: ERT-337 > URL: https://issues.jboss.org/browse/ERT-337 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > Fix For: Neon.1 (4.6) > > > Currently dynamic parser model is used for from-end debugging (Web Inspector Protocol) which is incompatible with new versions of blink / chromium. Need to switch to static parser model which is claimed to have backward compatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-337) Need to switch to static parser for Web Inspector Protocol (front-end debugging) [EBZ#497532]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-337?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-337: ---------------------------- Fix Version/s: Neon.1 (4.6) > Need to switch to static parser for Web Inspector Protocol (front-end debugging) [EBZ#497532] > --------------------------------------------------------------------------------------------- > > Key: ERT-337 > URL: https://issues.jboss.org/browse/ERT-337 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > Fix For: Neon.1 (4.6) > > > Currently dynamic parser model is used for from-end debugging (Web Inspector Protocol) which is incompatible with new versions of blink / chromium. Need to switch to static parser model which is claimed to have backward compatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-342) Breakpoints doesn't hit if create Project from existing source. [EBZ#439778]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-342?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-342: ---------------------------- Story Points: 2 > Breakpoints doesn't hit if create Project from existing source. [EBZ#439778] > ---------------------------------------------------------------------------- > > Key: ERT-342 > URL: https://issues.jboss.org/browse/ERT-342 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > Fix For: Neon.1 (4.6) > > > I created JavaScript project (Name: Sample) using "Create Project from existing source" Let see in "C:\TestProject" which contains test.js script. > Now i opened test.js and added some breakpoint in that script, now when I'm running the script breakpoint is Not Hitting. > *****************Investigation******************** > org.eclipse.wst.jsdt.debug.internal.core.model.ScriptResolutionManager there is a function guessScriptMatches(ScriptReference script, IPath path). > JavaDoc of this function: "Guesses if the paths are considered equal by walking backward from the last segment of the paths and counting the matching segments. The paths are guessed to be equal iff any two or more segments match in order." > So in My case because Project name and physical folder name are different. That why only file name is matching, but this function is checking for at least 2 segment to match, so it returns false and caller function will not add JavaScriptDebugTarget for this script. > ******************** Solution Proposal********************* > We can check if current script is inside root folder of project then if one segment matches we'll return true, for other case it will remain check for at least two segment to match -- 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