April 2016 - jbosstools-issues - Jboss List Archives

[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 #6 April 2016 (was: devex #4 March 2016, devex #5 April 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] (JBDS-3787) Installer - Installation of each component should be optional

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3787: --------------------------------- Fix Version/s: 10.0.0.Alpha1 > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3787) Installer - Installation of each component should be optional

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3787?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3787: ------------------------------------ Assignee: Denis Golovin > Installer - Installation of each component should be optional > ------------------------------------------------------------- > > Key: JBDS-3787 > URL: https://issues.jboss.org/browse/JBDS-3787 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Affects Versions: 9.1.0.GA > Reporter: Len DiMaggio > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.0.0.Alpha1 > > > Feature request - It would be ideal of the installer allowed to the user to select to install/not install any of the installer's components (JDK, CDK, etc.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-115) Create a common plugin for node.js plugins [EBZ#489148]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-115?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan resolved ERT-115. ------------------------------ Resolution: Done > Create a common plugin for node.js plugins [EBZ#489148] > ------------------------------------------------------- > > Key: ERT-115 > URL: https://issues.jboss.org/browse/ERT-115 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: Debug, bzira > Fix For: Neon (4.6) M6 > > > Create a common plugin containing common utilities, etc. that can be reused by the different node.js plugins -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-93) gulp long-running task (e.g serve) can not be killed from eclipse console [EBZ#489041]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-93?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-93: ---------------------------- Sprint: devex #4 March 2016, devex #6 April 2016 (was: devex #4 March 2016, devex #5 April 2016) > gulp long-running task (e.g serve) can not be killed from eclipse console [EBZ#489041] > -------------------------------------------------------------------------------------- > > Key: ERT-93 > URL: https://issues.jboss.org/browse/ERT-93 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: General, bzira > > Long-running task (e.g serve) still locks the port after pressing "Terminate" button on Eclipse console. It looks like sending "exit" command to CLI does not kill the process -- 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 #6 April 2016 (was: devex #2 February 2016, devex #4 March 2016, devex #5 April 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-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, devex #6 April 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] (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 #6 April 2016 (was: devex #1 February 2016, devex #2 February 2016, devex #4 March 2016, devex #5 April 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] (TOOLSDOC-710) JBDS 9.1 GA: Document a use case for Hibernate Tooling

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-710?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-710: -------------------------------------------- Hi [~mhusnain], I am trying to get this completed by Wednesday and sent to QE by Thursday so that I have time over the weekend to convert it into md and adoc and have it ready for GA on Tuesday. Shall keep the JIRA updated with my status. > JBDS 9.1 GA: Document a use case for Hibernate Tooling > ------------------------------------------------------ > > Key: TOOLSDOC-710 > URL: https://issues.jboss.org/browse/TOOLSDOC-710 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Hibernate-tools > Fix For: 9.1 GA > > > Draft a use case and document it for Hibernate Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-65) Create Keyword Completion Engine

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-65?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan resolved ERT-65. ----------------------------- Resolution: Done > Create Keyword Completion Engine > -------------------------------- > > Key: ERT-65 > URL: https://issues.jboss.org/browse/ERT-65 > Project: Eclipse Release Train > Issue Type: Sub-task > Components: JSDT > Reporter: Ian Stewart-Binks > Assignee: Ian Stewart-Binks > > When a user invokes code completion, a list of contextually practical keywords should be suggested. > * After a user has typed a few characters and invoked code completion, keywords prefixed by those few characters should be suggested. For instance, if the user has just typed 'del', 'delete' should be suggested. Similarly, if the user has just typed 'd', all of the keywords that start with the letter 'd' should be suggested. > * Keywords based on relevance should also be suggested. For instance, consider the case when a user has begun a *do while* block. If the user writes the *do* and the *block* and invokes code completion, *while(<CR>);* should be one of the suggestions. A similar functionality for an *if else* should be implemented, as well. > Questions: > * Should keywords that match templates be suggested even though their template counterpart is in the list of suggestions? > * Should keywords be suggested within JSDocs? -- 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 April 2016