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: ---------------------------- Story Points: 15 (was: 10) > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-129) Gulp / Grunt tasks processing does not work with new Esprima parser [EBZ#490999]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-129?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan resolved ERT-129. ------------------------------ Resolution: Done > Gulp / Grunt tasks processing does not work with new Esprima parser [EBZ#490999] > -------------------------------------------------------------------------------- > > Key: ERT-129 > URL: https://issues.jboss.org/browse/ERT-129 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > gulp / grunt task processing should be adjusted to the new esprima parser. For now, only launch of the default task (on the gulpfile.js / gruntfile.js directly) is available - other tasks are not contributed to CNF. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-127) Debugging should happen in JSDT editor if the project exist in workspace [EBZ#490626]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-127?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-127: ----------------------------- Story Points: 2 (was: 25) > Debugging should happen in JSDT editor if the project exist in workspace [EBZ#490626] > ------------------------------------------------------------------------------------- > > Key: ERT-127 > URL: https://issues.jboss.org/browse/ERT-127 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ilya Buziuk > Labels: 3.8_M7, Debug, bzira > Fix For: Neon (4.6) M7 > > > For now all debugging happens via Chromium JavaScript editor via virtual file system. However, if the target project exists in the workspace all debugging should happen in jsdt editor via real file system -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

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 resolved ERT-63. ----------------------------- Resolution: Done > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-90) Spike for refactoring and code manipulation

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-90?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-90: ---------------------------- Story Points: 25 (was: 10) > Spike for refactoring and code manipulation > ------------------------------------------- > > Key: ERT-90 > URL: https://issues.jboss.org/browse/ERT-90 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Gorkem Ercan > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Figure out what to do for refactoring and code manipulation -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

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 resolved ERT-19. ----------------------------- Resolution: Done > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22224) Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22224?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22224: ----------------------------------------------- The proposed change for JBIDE-22174 will open this wizard on the second page, if a project is selected in OpenShift explorer. > Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22224 > URL: https://issues.jboss.org/browse/JBIDE-22224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > > When I am trying to deploy a docker image via context menu of a docker image in Docker Explorer, I am prompted every time to confirm Connection dialog, although I have an established connection in OpenShift Explorer view. It's pretty annoying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

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 resolved ERT-15. ----------------------------- Resolution: Done > [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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-674. ------------------------------ Fix Version/s: 4.3.0.Final Resolution: Done Added deprecation of esb, guvnor and jBPM3. Please see attachments. Please comment quickly if there are any issues. [~maxandersen] [~apodhrad] [~ganandan-Redhat] [~shelly.mcgowan] [~bbrodt] > Deprecate 'SOA 5.x Compatibility' tooling > ----------------------------------------- > > Key: JBTIS-674 > URL: https://issues.jboss.org/browse/JBTIS-674 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.3.0.Final, 9.0.0.GA > > Attachments: dep1.png, dep2.png, dep3.png, dep4.png > > > The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of: > org.guvnor.tools.feature > org.jboss.tools.esb.feature > org.jboss.tools.jbpm3.feature > org.jboss.tools.jbpm.common.feature > org.jboss.tools.jbpm.convert.feature > The runtime detector features will not be deprecated: > org.jboss.tools.runtime.drools.detector.feature > org.jboss.tools.runtime.esb.detector.feature > org.jboss.tools.runtime.jbpm.detector.feature > FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-674: ----------------------------- Attachment: dep4.png dep3.png dep2.png dep1.png > Deprecate 'SOA 5.x Compatibility' tooling > ----------------------------------------- > > Key: JBTIS-674 > URL: https://issues.jboss.org/browse/JBTIS-674 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.0.GA > > Attachments: dep1.png, dep2.png, dep3.png, dep4.png > > > The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of: > org.guvnor.tools.feature > org.jboss.tools.esb.feature > org.jboss.tools.jbpm3.feature > org.jboss.tools.jbpm.common.feature > org.jboss.tools.jbpm.convert.feature > The runtime detector features will not be deprecated: > org.jboss.tools.runtime.drools.detector.feature > org.jboss.tools.runtime.esb.detector.feature > org.jboss.tools.runtime.jbpm.detector.feature > FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan] -- 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