[ https://issues.jboss.org/browse/ERT-170?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan updated ERT-170:
-----------------------------
Story Points: 20 (was: 15)
> Chromium Debug: Terminating V8 debugger process should also kill main(Node) process. [EBZ#491735]
> -------------------------------------------------------------------------------------------------
>
> Key: ERT-170
> URL: https://issues.jboss.org/browse/ERT-170
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Labels: Debug, bzira
>
> The normal scenario for starting a chomium debugger process includes both launching the main js runtime (Node), and also starting the V8 debugger process...
> Users will expect the same when terminating (both are killed).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ERT-187?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon reassigned ERT-187:
---------------------------------
Assignee: Xavier Coulon
> Add context menu to remove a connection [EBZ#493443]
> ----------------------------------------------------
>
> Key: ERT-187
> URL: https://issues.jboss.org/browse/ERT-187
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> There's already a toolbar action but adding the same command in the context menu when selecting a connection would would fill user's expectation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ERT-187?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-187:
------------------------------
Story Points: 1
> Add context menu to remove a connection [EBZ#493443]
> ----------------------------------------------------
>
> Key: ERT-187
> URL: https://issues.jboss.org/browse/ERT-187
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> There's already a toolbar action but adding the same command in the context menu when selecting a connection would would fill user's expectation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ERT-187?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-187:
------------------------------
Sprint: devex #114 May 2016
> Add context menu to remove a connection [EBZ#493443]
> ----------------------------------------------------
>
> Key: ERT-187
> URL: https://issues.jboss.org/browse/ERT-187
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> There's already a toolbar action but adding the same command in the context menu when selecting a connection would would fill user's expectation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ERT-167?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan resolved ERT-167.
------------------------------
Resolution: Done
> Node.js launch is still available for closed / deleted projects [EBZ#492478]
> ----------------------------------------------------------------------------
>
> Key: ERT-167
> URL: https://issues.jboss.org/browse/ERT-167
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Labels: General, bzira
>
> If the project is closed / removed the launch configuration is still runable via Run Configurations -> Node.js Application. It is expected that all project launches will be unavailable though. Basically, the "Project" field should be created for Node.js Launch configuration in order to tight launches to appropriate projects
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ERT-142?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan updated ERT-142:
-----------------------------
Sprint: devex #113 April 2016 (was: devex #113 April 2016, devex #115 May 2016)
> 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
> 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)
[ https://issues.jboss.org/browse/ERT-134?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan updated ERT-134:
-----------------------------
Sprint: devex #113 April 2016 (was: devex #113 April 2016, devex #115 May 2016)
> Make ReconcileWorkingCopyOperation to use new parser completely [EBZ#490714]
> ----------------------------------------------------------------------------
>
> Key: ERT-134
> URL: https://issues.jboss.org/browse/ERT-134
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Labels: General, bzira
>
> The change https://git.eclipse.org/r/69179 has turned ReconcileWorkingCopyOperation to use ASTParser.newParser()/createAST().
> But we still need to make it to use new parser completely.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ERT-69?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-69:
----------------------------
Sprint: devex #113 April 2016 (was: devex #113 April 2016, devex #115 May 2016)
> Create JSDT .target File [EBZ#486944]
> -------------------------------------
>
> Key: ERT-69
> URL: https://issues.jboss.org/browse/ERT-69
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Friendly Jira Robot
> Labels: General, bzira
>
> Setting up JSDT for development right now is an arduous task. There are several steps, many of which are not fully documented. A .target file can be used to facilitate this process.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ERT-135?page=com.atlassian.jira.plugin.sy... ]
Gorkem Ercan resolved ERT-135.
------------------------------
Resolution: Done
> [contentassist] Some templates have multiple ${cursor} variables [EBZ#490800]
> -----------------------------------------------------------------------------
>
> Key: ERT-135
> URL: https://issues.jboss.org/browse/ERT-135
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Nick Boldt
> Assignee: Ian Stewart-Binks
> Labels: General, bzira
>
> Some templates fail the validation check because they have more than one ${cursor} variable.
> Simple fix: remove other ${cursor} variables.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ERT-89?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-89:
----------------------------
Sprint: devex #4 March 2016, devex #113 April 2016 (was: devex #4 March 2016, devex #113 April 2016, devex #115 May 2016)
> 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
> 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)