[JBoss JIRA] (ERT-15) [ES6] Support for ECMAScript 6 validation [EBZ#477031]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-15?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-15:
----------------------------
Sprint: devex #4 March 2016, devex #6 April 2016 (was: devex #4 March 2016, devex #5 April 2016)
> [ES6] Support for ECMAScript 6 validation [EBZ#477031]
> ------------------------------------------------------
>
> Key: ERT-15
> URL: https://issues.jboss.org/browse/ERT-15
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Gorkem Ercan
> Labels: 3.8_M6, General, bzira
> Fix For: Neon (4.6) M6
>
>
> JSDT Validator doesn't support ES6 syntax and display a lot of error with ES6 syntax.
> To fix this problem, there are 2 solutions :
> * improve the JSDT Validator to support ES6 syntax (I think it's a lot of work).
> * gives the capability to disable the JSDT Validator (with extension point and with preferences). With those solution, we could delegate the validator to another component like Tern JSHint (https://github.com/angelozerr/tern.java/wiki/Tern-Linter-JSHint) where JSHint is able to validate ES6 syntax.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-19) JSDT should support the use of sourcevalidation extension point [EBZ#481344]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-19?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-19:
----------------------------
Sprint: devex #1 February 2016, devex #2 February 2016, devex #4 March 2016, devex #6 April 2016 (was: devex #1 February 2016, devex #2 February 2016, devex #4 March 2016, devex #5 April 2016)
> JSDT should support the use of sourcevalidation extension point [EBZ#481344]
> ----------------------------------------------------------------------------
>
> Key: ERT-19
> URL: https://issues.jboss.org/browse/ERT-19
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Victor Rubezhny
> Priority: Trivial
> Labels: 3.8_M6, General, bzira
> Fix For: Neon (4.6) M7
>
>
> JSDT editor does not activate org.eclipse.wst.sse.ui.sourcevalidation extension point. We should enable the use of sourcevalidation extension point as a way for third party validators to extend/augment JSDT validation.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-45) Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-45?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan resolved ERT-45.
-----------------------------
Resolution: Done
> Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
> --------------------------------------------------------------------------------
>
> Key: ERT-45
> URL: https://issues.jboss.org/browse/ERT-45
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
>
> Chromium JavaScript Debugger by default expose scripts loaded in JavaScript VM through virtual file system. It looks like normal workspace project with name matches the launch configuration name.
> All interactions with VM are done through actions available on files in that virtual system.
> Ideally that virtual FS should not be exposed to user if project that targeted for debug is already presented in workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-45) Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-45?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-45:
----------------------------
Sprint: devex #4 March 2016, devex #5 April 2016 (was: devex #4 March 2016, devex #6 April 2016)
> Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
> --------------------------------------------------------------------------------
>
> Key: ERT-45
> URL: https://issues.jboss.org/browse/ERT-45
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
>
> Chromium JavaScript Debugger by default expose scripts loaded in JavaScript VM through virtual file system. It looks like normal workspace project with name matches the launch configuration name.
> All interactions with VM are done through actions available on files in that virtual system.
> Ideally that virtual FS should not be exposed to user if project that targeted for debug is already presented in workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-45) Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-45?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-45:
----------------------------
Sprint: devex #4 March 2016, devex #6 April 2016 (was: devex #4 March 2016, devex #5 April 2016)
> Hide Chromium JavaScript Debugger Virtual FS from Eclipse Workspace [EBZ#486057]
> --------------------------------------------------------------------------------
>
> Key: ERT-45
> URL: https://issues.jboss.org/browse/ERT-45
> Project: Eclipse Release Train
> Issue Type: Task
> Components: JSDT
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Labels: Debug, bzira
>
> Chromium JavaScript Debugger by default expose scripts loaded in JavaScript VM through virtual file system. It looks like normal workspace project with name matches the launch configuration name.
> All interactions with VM are done through actions available on files in that virtual system.
> Ideally that virtual FS should not be exposed to user if project that targeted for debug is already presented in workspace.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22150) Selected service in Properties view is not chosen in New OpenShift Server Adapter wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22150?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22150:
-----------------------------------
Assignee: Viacheslav Kabanovich (was: Andre Dietisheim)
Resolution: Done
Applied PR in master. Thanks [~scabanovich]!
> Selected service in Properties view is not chosen in New OpenShift Server Adapter wizard
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-22150
> URL: https://issues.jboss.org/browse/JBIDE-22150
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha1
>
>
> When opening a New OpenShift 3 Server Adapter wizard via context menu of a service in Properties view, the selected service from properties view is not preselected in the wizard. This is happening for more services within one project. It select first service under a project in the wizard. Preselection of a service for different projects works fine.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years