May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-173) Need to find a better solution for npm dependencies content assistant [EBZ#492192]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-173?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-173: ----------------------------- Story Points: 25 > Need to find a better solution for npm dependencies content assistant [EBZ#492192] > ---------------------------------------------------------------------------------- > > Key: ERT-173 > URL: https://issues.jboss.org/browse/ERT-173 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > In order to show content assist proposals for npm dependencies a 3rd party web service was used. It was a really problematic due to its unstable work, slowness and a tendency to change an URL for requests and formats of response. > I do believe, we should not provide any content assist for dependencies in case no search pattern is provided (typed in) by a user because of really huge memory requirements and network overload in such case: > - Native "npm search" command fails to list all the available packages on my environment after about 5 minutes of downloading packages > Given this, IMHO, we have not to show *all* available packages in content assistant, but show package list only if at least first letter (or a couple of beginning letters) of package name is typed in by a user. > Also the way to get the proposals itself is also a question: we cannot rely on 3rd party services as they are not enough stable and fast. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-174) JSON empty Array not properly recognized in the outline view [EBZ#491944]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-174?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan resolved ERT-174. ------------------------------ Resolution: Done > JSON empty Array not properly recognized in the outline view [EBZ#491944] > ------------------------------------------------------------------------- > > Key: ERT-174 > URL: https://issues.jboss.org/browse/ERT-174 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > Created attachment 261054 > Looks like the comma is not recognized as a comma after an empty array > Apparently is a lexical issue -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-172) Need to find a better solution for bower dependencies content assistant [EBZ#492191]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-172?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-172: ----------------------------- Story Points: 25 > Need to find a better solution for bower dependencies content assistant [EBZ#492191] > ------------------------------------------------------------------------------------ > > Key: ERT-172 > URL: https://issues.jboss.org/browse/ERT-172 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > In order to show content assist proposals for bower dependencies a 2rd party web service was used. It was a really problematic due to its unstable work, slowness and a tendency to change an URL for requests and formats of response. > I do believe, we should not provide any content assist for dependencies in case no search pattern is provided (typed in) by a user because of really huge memory requirements and network overload in such case: > - Native "bower search" command also takes a couple of minutes to complete and returns ~3.2MB of data (which means even more amount of network transfers). > Given this, IMHO, we have not to show *all* available packages in content assistant, but show package list only if at least first letter (or a couple of beginning letters) of package name is typed in by a user. > Also the way to get the proposals itself is also a question: we cannot rely on 3rd party services as they are not enough stable and fast. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-171) [ES6] Define a way to enable module parsing [EBZ#492130]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-171?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-171: ----------------------------- Sprint: devex #114 May 2016 > [ES6] Define a way to enable module parsing [EBZ#492130] > -------------------------------------------------------- > > Key: ERT-171 > URL: https://issues.jboss.org/browse/ERT-171 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Shane Bryzak > Labels: General, bzira > > By default JSDT uses "script" source type parsing, which causes import/exports to be marked as erors. JSDT needs to define a way for projects to opt-int to use "module" parsing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-171) [ES6] Define a way to enable module parsing [EBZ#492130]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-171?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-171: ----------------------------- Story Points: 5 > [ES6] Define a way to enable module parsing [EBZ#492130] > -------------------------------------------------------- > > Key: ERT-171 > URL: https://issues.jboss.org/browse/ERT-171 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Shane Bryzak > Labels: General, bzira > > By default JSDT uses "script" source type parsing, which causes import/exports to be marked as erors. JSDT needs to define a way for projects to opt-int to use "module" parsing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-13) Allow for connection settings edition [EBZ#476387]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-13?page=com.atlassian.jira.plugin.sys... ] Xavier Coulon updated ERT-13: ----------------------------- Sprint: devex #114 May 2016 > Allow for connection settings edition [EBZ#476387] > -------------------------------------------------- > > Key: ERT-13 > URL: https://issues.jboss.org/browse/ERT-13 > Project: Eclipse Release Train > Issue Type: Feature Request > Components: Linux Tools > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Labels: Docker, bzira > Attachments: 2016-04-19 09.48.bmml, 2016-04-19 09.48.png > > > The user should be able to view and edit the connection settings once the connection exists. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-187) Add context menu to remove a connection [EBZ#493443]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-187?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-187: ------------------------------ Issue Type: Enhancement (was: Task) Priority: Minor (was: Major) > 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: Enhancement > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Priority: Minor > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-184) NPE when chromium feature is not present [EBZ#493234]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-184?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-184: ----------------------------- Story Points: 5 > NPE when chromium feature is not present [EBZ#493234] > ----------------------------------------------------- > > Key: ERT-184 > URL: https://issues.jboss.org/browse/ERT-184 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Priority: Critical > Labels: 3.8_RC1, Debug, bzira > Fix For: Neon (4.6) RC1 > > > Starting a debugging session without Chromium feature available causes an NPE. This can have 2 solutions (and maybe both of them are desirable). > * A better error message than a NPE when there is no debug support > * Include the chromium feature by default, as "included" by the main JSDT feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-184) NPE when chromium feature is not present [EBZ#493234]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-184?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-184: ----------------------------- Sprint: devex #114 May 2016 > NPE when chromium feature is not present [EBZ#493234] > ----------------------------------------------------- > > Key: ERT-184 > URL: https://issues.jboss.org/browse/ERT-184 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Priority: Critical > Labels: 3.8_RC1, Debug, bzira > Fix For: Neon (4.6) RC1 > > > Starting a debugging session without Chromium feature available causes an NPE. This can have 2 solutions (and maybe both of them are desirable). > * A better error message than a NPE when there is no debug support > * Include the chromium feature by default, as "included" by the main JSDT feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-170) Chromium Debug: Terminating V8 debugger process should also kill main(Node) process. [EBZ#491735]

by Gorkem Ercan (JIRA)

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

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