May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-44) JSON Schema extension for JSON editor [EBZ#485701]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-44?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-44: ---------------------------- Story Points: 40 > JSON Schema extension for JSON editor [EBZ#485701] > -------------------------------------------------- > > Key: ERT-44 > URL: https://issues.jboss.org/browse/ERT-44 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Labels: bzira, wst.json > > JSON editor should have a generic extension for mapping JSON schemas to files.The extension should allow 3rd parties to contribute a JSON schema and get code assist, validation etc. through JSON editor without introducing a new editor type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-44) JSON Schema extension for JSON editor [EBZ#485701]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-44?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-44: ---------------------------- Story Points: 30 (was: 40) > JSON Schema extension for JSON editor [EBZ#485701] > -------------------------------------------------- > > Key: ERT-44 > URL: https://issues.jboss.org/browse/ERT-44 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Labels: bzira, wst.json > > JSON editor should have a generic extension for mapping JSON schemas to files.The extension should allow 3rd parties to contribute a JSON schema and get code assist, validation etc. through JSON editor without introducing a new editor type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[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: ----------------------------- Sprint: devex #114 May 2016 > 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] (JBIDE-22325) Clean up enablement on module deploy page of server editor

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22325?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-22325: ----------------------------------- Fix Version/s: 4.4.0.Alpha2 Assignee: Rob Stryker Resolution: Done pushed to master > Clean up enablement on module deploy page of server editor > ---------------------------------------------------------- > > Key: JBIDE-22325 > URL: https://issues.jboss.org/browse/JBIDE-22325 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > As mentioned in JBIDE-20577, enablement must be more clear. Unfortunately this requires moving a useful utility class from openshift into foundation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-166) Chromium Debug context menu's enabled for everything [EBZ#491480]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-166?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-166: ----------------------------- Sprint: devex #114 May 2016 > Chromium Debug context menu's enabled for everything [EBZ#491480] > ----------------------------------------------------------------- > > Key: ERT-166 > URL: https://issues.jboss.org/browse/ERT-166 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > > The context menu "V8 Debugging" is available for any type of selection. > I tracked this menu contribution to: "org.eclipse.wst.jsdt.chromium.debug.ui.ChromiumSourceFileActionsId.MenuId" > Should filter to only *.js files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-111) Need to add "JavaScript Development Tools Chromium/V8 Remote Debugger" features into WTP Repositories [EBZ#488144]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-111?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan resolved ERT-111. ------------------------------ Resolution: Done > Need to add "JavaScript Development Tools Chromium/V8 Remote Debugger" features into WTP Repositories [EBZ#488144] > ------------------------------------------------------------------------------------------------------------------ > > Key: ERT-111 > URL: https://issues.jboss.org/browse/ERT-111 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Labels: bzira, releng > > We need to add "JavaScript Development Tools Chromium/V8 Remote Debugger" features to webtools.releng.aggregator/webtools.repositories to allow a standalone installation for these features. > The features are: > - org.eclipse.wst.jsdt.chromium.debug.feature > - org.eclipse.wst.jsdt.chromium_sdk.feature > - org.eclipse.wst.jsdt.chromium_tests.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-166) Chromium Debug context menu's enabled for everything [EBZ#491480]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-166?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-166: ----------------------------- Story Points: 10 > Chromium Debug context menu's enabled for everything [EBZ#491480] > ----------------------------------------------------------------- > > Key: ERT-166 > URL: https://issues.jboss.org/browse/ERT-166 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > > The context menu "V8 Debugging" is available for any type of selection. > I tracked this menu contribution to: "org.eclipse.wst.jsdt.chromium.debug.ui.ChromiumSourceFileActionsId.MenuId" > Should filter to only *.js files. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-144) Gulp is not available in the Quick access [EBZ#492124]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-144?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-144: ----------------------------- Story Points: 15 > Gulp is not available in the Quick access [EBZ#492124] > ------------------------------------------------------ > > Key: ERT-144 > URL: https://issues.jboss.org/browse/ERT-144 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > "Run as Gulp task" is not available via quick access. Basically, selection should be tracked and the following behavior is expected: > - IProject with gulpfile.js (launch default task from gulpfile.js) > - IFile gulpfile.js (default task should be run) > - ITask (run gulp task) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-145) Grunt is not available in the Quick access [EBZ#492125]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-145?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-145: ----------------------------- Story Points: 15 > Grunt is not available in the Quick access [EBZ#492125] > ------------------------------------------------------- > > Key: ERT-145 > URL: https://issues.jboss.org/browse/ERT-145 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > "Run as Grunt task" is not available via quick access. Basically, selection should be tracked and the following behavior is expected: > - IProject with gruntfile.js (launch default task from gruntfile.js) > - IFile gruntfile.js (default task should be run) > - ITask (run grunt task) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-25) JavaScript Task Runner: grunt [EBZ#483398]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-25?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan resolved ERT-25. ----------------------------- Resolution: Done > JavaScript Task Runner: grunt [EBZ#483398] > ------------------------------------------ > > Key: ERT-25 > URL: https://issues.jboss.org/browse/ERT-25 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > Need to add grunt support to Eclipse. > official site - http://gruntjs.com/ > github - https://github.com/gruntjs/grunt > LICENSE-MIT - https://github.com/gruntjs/grunt/blob/master/LICENSE-MIT -- 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