July 2016 - jbosstools-issues - Jboss List Archives

[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: ---------------------------- Fix Version/s: Neon.1 (4.6) > 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

[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 reassigned ERT-342: ------------------------------- Assignee: Ilya Buziuk > 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 > Assignee: Ilya Buziuk > 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

[JBoss JIRA] (ERT-341) Need to add Chromium / Chrome Runtime for front-end Debugging [EBZ#497765]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-341?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-341: ---------------------------- Story Points: 10 > Need to add Chromium / Chrome Runtime for front-end Debugging [EBZ#497765] > -------------------------------------------------------------------------- > > Key: ERT-341 > URL: https://issues.jboss.org/browse/ERT-341 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > Fix For: Neon.1 (4.6) > > > As part of Neon release mechanism to register different JS Runtime has been implemented (Bug 359436 - Investigate defining browsers / runtimes to use for debugging). The main idea behind this is that is possible to provide different > JavaScript runtimes through runtime providers. All of the runtime > providers must be associated to a runtime type (previously defined > through another extension point), and all those contributions are > managed and accessed through a JavaScript runtime manager. > Need to add `Chrome / Chromium Runtime` that will be used for front-end debugging. > Chromium Runtime will be launched with parameter like --remote-debugging-port=9222 (debug port) / 'www.example.com' (start page). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-341) Need to add Chromium / Chrome Runtime for front-end Debugging [EBZ#497765]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-341?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-341: ------------------------------- Assignee: Ilya Buziuk > Need to add Chromium / Chrome Runtime for front-end Debugging [EBZ#497765] > -------------------------------------------------------------------------- > > Key: ERT-341 > URL: https://issues.jboss.org/browse/ERT-341 > 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) > > > As part of Neon release mechanism to register different JS Runtime has been implemented (Bug 359436 - Investigate defining browsers / runtimes to use for debugging). The main idea behind this is that is possible to provide different > JavaScript runtimes through runtime providers. All of the runtime > providers must be associated to a runtime type (previously defined > through another extension point), and all those contributions are > managed and accessed through a JavaScript runtime manager. > Need to add `Chrome / Chromium Runtime` that will be used for front-end debugging. > Chromium Runtime will be launched with parameter like --remote-debugging-port=9222 (debug port) / 'www.example.com' (start page). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-341) Need to add Chromium / Chrome Runtime for front-end Debugging [EBZ#497765]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-341?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-341: ---------------------------- Fix Version/s: Neon.1 (4.6) > Need to add Chromium / Chrome Runtime for front-end Debugging [EBZ#497765] > -------------------------------------------------------------------------- > > Key: ERT-341 > URL: https://issues.jboss.org/browse/ERT-341 > 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) > > > As part of Neon release mechanism to register different JS Runtime has been implemented (Bug 359436 - Investigate defining browsers / runtimes to use for debugging). The main idea behind this is that is possible to provide different > JavaScript runtimes through runtime providers. All of the runtime > providers must be associated to a runtime type (previously defined > through another extension point), and all those contributions are > managed and accessed through a JavaScript runtime manager. > Need to add `Chrome / Chromium Runtime` that will be used for front-end debugging. > Chromium Runtime will be launched with parameter like --remote-debugging-port=9222 (debug port) / 'www.example.com' (start page). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-349) Add JavaScript formatting option for anonymous functions [EBZ#315507]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-349?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-349: ---------------------------- Story Points: 5 > Add JavaScript formatting option for anonymous functions [EBZ#315507] > --------------------------------------------------------------------- > > Key: ERT-349 > URL: https://issues.jboss.org/browse/ERT-349 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Priority: Trivial > Labels: Future, General, bzira > Fix For: Neon.1 (4.6) > > > Build Identifier: Build id: 20100218-1602 > It should be possible to set white-space formatting rules differently for anonymous functions and named functions. > Use-case: It should be possible to stipulate that white-space must precede the opening parenthesis in an anonymous function declaration while named function declaration should not. > Example: > var foo = function () { > // some code > }; > function foo() { > // some code > } > Reproducible: Always > Steps to Reproduce: > Not really a bug, more of a feature request. Go to Window > Preferences > Web > JavaScript > Code Style > Formatter. Under the White Space tab open Declarations and see that there is only a setting for Functions (not Named Functions and Anonymous Functions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-349) Add JavaScript formatting option for anonymous functions [EBZ#315507]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-349?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-349: ---------------------------- Fix Version/s: Neon.1 (4.6) (was: Future) > Add JavaScript formatting option for anonymous functions [EBZ#315507] > --------------------------------------------------------------------- > > Key: ERT-349 > URL: https://issues.jboss.org/browse/ERT-349 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Priority: Trivial > Labels: Future, General, bzira > Fix For: Neon.1 (4.6) > > > Build Identifier: Build id: 20100218-1602 > It should be possible to set white-space formatting rules differently for anonymous functions and named functions. > Use-case: It should be possible to stipulate that white-space must precede the opening parenthesis in an anonymous function declaration while named function declaration should not. > Example: > var foo = function () { > // some code > }; > function foo() { > // some code > } > Reproducible: Always > Steps to Reproduce: > Not really a bug, more of a feature request. Go to Window > Preferences > Web > JavaScript > Code Style > Formatter. Under the White Space tab open Declarations and see that there is only a setting for Functions (not Named Functions and Anonymous Functions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-339) Array initializer auto-formatting is a hideous, broken nightmare [EBZ#419931]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-339?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-339: ---------------------------- Fix Version/s: Neon.1 (4.6) > Array initializer auto-formatting is a hideous, broken nightmare [EBZ#419931] > ----------------------------------------------------------------------------- > > Key: ERT-339 > URL: https://issues.jboss.org/browse/ERT-339 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > Fix For: Neon.1 (4.6) > > > If you are writing an array initializer in JavaScript, you most likely want to it to look like this: > var myArray = [ > item1, > item2, > item3, > ... > ]; > However, no matter how you configure Eclipse to format array initializers, it ignores it all and instead tries to make you kill yourself with frustration. > Actually *typing* an array initializer goes like this, cursor position indicated by _ > 1. You type the following: > var myArray = [_ > 2. Eclipse inserts a closing paren: > var myArray = [_] > 3. You press enter, expecting to a get a newline, but instead Eclipse interprets it as "move the cursor to the end of the line: > var myArray = []_ > 4. You left-arrow the cursor back a position, and press enter again. This time, Eclipse does insert a newline. But it auto-indents as follows: > var myArray = [ > _] > Rather than following the same, sane behaviour it provides for object initializers, Eclipse idents the following line to the same column as the opening paren, it idents using spaces, even if you've configured it to use tabs and only tabs for indentation, and it leaves the closing paren on the same line, rather than moving it to the start of the next. > Trying to fix the indentation is impossible, because it has used spaces instead of tabs. If you delete the spaces and press tab, it merely re-inserts the spaces and re-indents back to the column of the open paren! > It's hard to adequately emphasise what a frustrating, poisonous impression this makes on someone using Eclipse as a tool for JavaScript development. It feels actively user-hostile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-339) Array initializer auto-formatting is a hideous, broken nightmare [EBZ#419931]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-339?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-339: ---------------------------- Story Points: 10 > Array initializer auto-formatting is a hideous, broken nightmare [EBZ#419931] > ----------------------------------------------------------------------------- > > Key: ERT-339 > URL: https://issues.jboss.org/browse/ERT-339 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > Fix For: Neon.1 (4.6) > > > If you are writing an array initializer in JavaScript, you most likely want to it to look like this: > var myArray = [ > item1, > item2, > item3, > ... > ]; > However, no matter how you configure Eclipse to format array initializers, it ignores it all and instead tries to make you kill yourself with frustration. > Actually *typing* an array initializer goes like this, cursor position indicated by _ > 1. You type the following: > var myArray = [_ > 2. Eclipse inserts a closing paren: > var myArray = [_] > 3. You press enter, expecting to a get a newline, but instead Eclipse interprets it as "move the cursor to the end of the line: > var myArray = []_ > 4. You left-arrow the cursor back a position, and press enter again. This time, Eclipse does insert a newline. But it auto-indents as follows: > var myArray = [ > _] > Rather than following the same, sane behaviour it provides for object initializers, Eclipse idents the following line to the same column as the opening paren, it idents using spaces, even if you've configured it to use tabs and only tabs for indentation, and it leaves the closing paren on the same line, rather than moving it to the start of the next. > Trying to fix the indentation is impossible, because it has used spaces instead of tabs. If you delete the spaces and press tab, it merely re-inserts the spaces and re-indents back to the column of the open paren! > It's hard to adequately emphasise what a frustrating, poisonous impression this makes on someone using Eclipse as a tool for JavaScript development. It feels actively user-hostile. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-356) JavaScript Debugger should support mapping between original and minified js files [EBZ#498518]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-356: --------------------------------------- Summary: JavaScript Debugger should support mapping between original and minified js files [EBZ#498518] Key: ERT-356 URL: https://issues.jboss.org/browse/ERT-356 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot minified js files should be mapped to original js files located in the workspace for JavaScript WIP debugging -- 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