April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-69) Create JSDT .target File [EBZ#486944]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-69?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-69: ---------------------------- Story Points: 2 > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-69) Create JSDT .target File [EBZ#486944]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-69?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-69: ---------------------------- Sprint: devex #6 April 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-12) [EPIC] [language support] Add support for ECMAScript 2015 [EBZ#473559]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-12?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-12: ---------------------------- Summary: [EPIC] [language support] Add support for ECMAScript 2015 [EBZ#473559] (was: [language support] Add support for ECMAScript 2015 [EBZ#473559]) > [EPIC] [language support] Add support for ECMAScript 2015 [EBZ#473559] > ---------------------------------------------------------------------- > > Key: ERT-12 > URL: https://issues.jboss.org/browse/ERT-12 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Priority: Trivial > Labels: 3.8_M6, Web, bzira > Fix For: Neon (4.6) M6 > > > As ECMAScript 6 aka ECMAScript 2015 got officially released in June 2015[1], the JSDT validator should integrate a related compliance level. > There was also a request for supporting ECMAScript 4[2], which got never released, though, and that bug never got traction. So I thought I'd open up a new one. This bug should serve as a meta-bug for the different features introduced in ECMAScript 2015. > Sebastian > [1] http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf > [2] Bug 223131 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-122) [content assist] See if we can dynamically add Nodejs context [EBZ#489366]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-122?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-122: ----------------------------- Story Points: 20 > [content assist] See if we can dynamically add Nodejs context [EBZ#489366] > -------------------------------------------------------------------------- > > Key: ERT-122 > URL: https://issues.jboss.org/browse/ERT-122 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > If a project has a node runtime associated with it, we should dynamically add a nodejs context such that appropriate node content assist templates can be proposed to the user. > Note: This may or may not be possible with the current JSDT codebase. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-84) Create oomph configuration to simplify development environment setup [EBZ#488343]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-84?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-84: ---------------------------- Story Points: 2 > Create oomph configuration to simplify development environment setup [EBZ#488343] > --------------------------------------------------------------------------------- > > Key: ERT-84 > URL: https://issues.jboss.org/browse/ERT-84 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > Would be good to have JSDT project available in eclipse-installer distribution. That would let potential contributors to configure development environment, get sources and start hacking the code much faster then doing all development setup manually. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-108) JSON Editor dies with large files [EBZ#487906]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-108?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-108: ----------------------------- Story Points: 35 > JSON Editor dies with large files [EBZ#487906] > ---------------------------------------------- > > Key: ERT-108 > URL: https://issues.jboss.org/browse/ERT-108 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: bzira, wst.json > > I have tried to open [1] [2] on JSON editor that caused the editor to completely freeze eclipse. Other than being large files I do not think there is any other reason for these files to cause a freeze > [1]https://github.com/jquery/esprima/blob/master/test/3rdparty/syntax/angu... > [2] https://github.com/jquery/esprima/blob/master/test/3rdparty/syntax/backbo... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-76) Sync of IJSONModel with editor should be improved/fixed [EBZ#486860]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-76?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan resolved ERT-76. ----------------------------- Resolution: Done > Sync of IJSONModel with editor should be improved/fixed [EBZ#486860] > -------------------------------------------------------------------- > > Key: ERT-76 > URL: https://issues.jboss.org/browse/ERT-76 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: bzira, wst.json > Fix For: Neon (4.6) M7 > > > IMHO the sync of IJSONModel with editor is the most important and should be done/fixed before fixing, improving other features. But it is the most hard too. > At first, we should validate the IJSONModel API > The big problem with JSON Editor is that the IJSONModel, IJSONPair, IJSONDocument, etc. There are a lot of copy/paste from XML/CSS plugins so this model and the implementation should be really fixed/improved. > For instance completion works when editor is opened, but it is broken after some changes of the text editor. It is because IJSONModel is not very well sync. > The most bugs that I see like: > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486606 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=485694 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486849 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486524 > are linked to this sync problem. > So tests https://github.com/angelozerr/eclipse-wtp-json/blob/master/core/org.eclip... must be completed when sync of model is improved. > I will try to create a patch for adding tests https://bugs.eclipse.org/bugs/show_bug.cgi?id=486238 > It's a very hard task, so good luck to do that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-98) V8 Debugging Menu is shown on too many places [EBZ#488865]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-98?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan closed ERT-98. --------------------------- Resolution: Duplicate Issue > V8 Debugging Menu is shown on too many places [EBZ#488865] > ---------------------------------------------------------- > > Key: ERT-98 > URL: https://issues.jboss.org/browse/ERT-98 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: Debug, bzira > > V8 debugging menu is very eager. We should tune down the places that it is shown. Also we need to consider if the menu is still needed after our integration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22225) Debugging for node.js applications on Openshift

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22225?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-22225: --------------------------------- Story Points: 15 > Debugging for node.js applications on Openshift > ----------------------------------------------- > > Key: JBIDE-22225 > URL: https://issues.jboss.org/browse/JBIDE-22225 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: javascript, openshift > Reporter: Gorkem Ercan > > We should be able to start and connect the new debugger to a node.js application running on Openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-141) Hot swap does not work in JSDT editor for Chromium/V8 debugging [EBZ#492038]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-141?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-141: ----------------------------- Sprint: devex #6 April 2016 > Hot swap does not work in JSDT editor for Chromium/V8 debugging [EBZ#492038] > ---------------------------------------------------------------------------- > > Key: ERT-141 > URL: https://issues.jboss.org/browse/ERT-141 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > > For now hot swap works only on Virtual File system and fails for workspace's files -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016