March 2016 - jbosstools-issues - Jboss List Archives

[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) > 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

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 updated ERT-89: ---------------------------- Sprint: devex #4 March 2016, devex #5 April 2016 (was: devex #4 March 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)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-97) Syntax Highighting for template literals [EBZ#488724]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-97?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-97: ---------------------------- Sprint: devex #4 March 2016, devex #5 April 2016 (was: devex #4 March 2016) > Syntax Highighting for template literals [EBZ#488724] > ----------------------------------------------------- > > Key: ERT-97 > URL: https://issues.jboss.org/browse/ERT-97 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Shane Bryzak > Labels: General, bzira > > Provide highlighting for ES6 Template strings[1] on JSDT editor. > [1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Templat... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21996) Order of project in New OS3 Server Adapter wizard could be better

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21996?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21996: ----------------------------------- Assignee: Andre Dietisheim > Order of project in New OS3 Server Adapter wizard could be better > ----------------------------------------------------------------- > > Key: JBIDE-21996 > URL: https://issues.jboss.org/browse/JBIDE-21996 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter_wizard > > With latest changes to New OS3 Server Adapter wizard the current order of projects, listed on wizard page where service selection is done, is a bit strange. At first there are alphanumeric ordered projects with no services and therefore they are not useful for creation of a new OS3 Server Adapter and then there are projects with any service ordered in alphanumberic order. It results in following. > Assume project aproject with no services, bproject with a service, c project with no services, d project with a service. Order on the wizard page is following: > a > c > b > d > I think we are safe not to list projects with no services there or otherwise we should keep alphanumeric order regardless existence of a service under a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-63) npm dependency content assist is broken [EBZ#486849]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-63?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-63: ---------------------------- Sprint: devex #2 February 2016, devex #4 March 2016, devex #5 April 2016 (was: devex #2 February 2016, devex #4 March 2016) > npm dependency content assist is broken [EBZ#486849] > ---------------------------------------------------- > > Key: ERT-63 > URL: https://issues.jboss.org/browse/ERT-63 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Labels: bzira, wst.json > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[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 #5 April 2016 (was: devex #1 February 2016, devex #2 February 2016, devex #4 March 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

1
0
0 / 0

[JBoss JIRA] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-62: ---------------------------- Sprint: devex #1 February 2016, devex #2 February 2016, devex #4 March 2016, devex #5 April 2016 (was: devex #1 February 2016, devex #2 February 2016, devex #4 March 2016) > Refactor JSDT Code Completion [EBZ#486776] > ------------------------------------------ > > Key: ERT-62 > URL: https://issues.jboss.org/browse/ERT-62 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ian Stewart-Binks > Labels: General, bzira > > The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions. > A proposal base for the code completion engine should include, but is not necessarily limited to: > - Keywords > - Identifiers (declared variables and functions in currently open JS file) > - Recently used methods of functions (currently open JS file as a bare minimum) > All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[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 #5 April 2016 (was: devex #4 March 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

1
0
0 / 0

[JBoss JIRA] (JBDS-3613) Support OpenShift 3.2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3613?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3613: -------------------------------------- Correct, CDK 2.0 will use OS 3.1. But it looks like JBDS works fine with the beta of OSE 3.2 so I think we can close this issue as done. When CDK will migrate to OS 3.2 we will make sure JBDS.next works fine with the new CDK & OSE 3.2. But it will be covered by other issues. > Support OpenShift 3.2 > --------------------- > > Key: JBDS-3613 > URL: https://issues.jboss.org/browse/JBDS-3613 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Affects Versions: 9.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 9.1.0.CR1 > > > CDK will GA with OpenShift 3.2 we will need to support 3.2 in OpenShift tooling. > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21994) Cannot show OpenShift 3 application via live reload

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21994?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21994: --------------------------------------- [~mlabuda] The LiveReload tooling will trigger a refresh at the browser level and as a consequence, the user will see the changes in action. So yes, I would say it makes sense. [~adietish], yes, I can look at this issue. > Cannot show OpenShift 3 application via live reload > --------------------------------------------------- > > Key: JBIDE-21994 > URL: https://issues.jboss.org/browse/JBIDE-21994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Currently Show In - Web Browser via Live Reload Server does not work for OpenShift 3 server adapters. It opens url localhost:port but a page is empty. Page is of type text/plain. > There is also a question - do we really need showing via live reload anymore? We have already incremental deployment what reflect similar(/same) behaviour as Live Reload. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016