February 2016 - jbosstools-issues

[JBoss JIRA] (ERT-67) Bump JSDT feature/plugin versions to 2.0 [EBZ#485699]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-67?page=com.atlassian.jira.plugin.sys... ] Victor Rubezhny reassigned ERT-67: ---------------------------------- Assignee: Victor Rubezhny > Bump JSDT feature/plugin versions to 2.0 [EBZ#485699] > ----------------------------------------------------- > > Key: ERT-67 > URL: https://issues.jboss.org/browse/ERT-67 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > We have several new features and breaking changes coming to JSDT that affects UI, core and debugger. The plugin and feature versions should be updated to 2.0 to accommodate the adoption of these changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-12) [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: ---------------------------- Sprint: devex #1 February 2016 (was: devex #1 February 2016, devex #2 February 2016) > [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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-54) Need to add navigation from Project Explorer to Editor for gulp tasks [EBZ#486240]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-54?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-54: ---------------------------- Story Points: 5 (was: 10) > Need to add navigation from Project Explorer to Editor for gulp tasks [EBZ#486240] > ---------------------------------------------------------------------------------- > > Key: ERT-54 > URL: https://issues.jboss.org/browse/ERT-54 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > Original Estimate: 1 day, 2 hours > Remaining Estimate: 1 day, 2 hours > > Gulp task selection in Project Explorer should highlight task in the Editor if the suitable file is opened. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-73) JSON Editor missing some icon(s?) [EBZ#487036]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-73?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-73: ---------------------------- Sprint: devex #2 February 2016 > JSON Editor missing some icon(s?) [EBZ#487036] > ---------------------------------------------- > > Key: ERT-73 > URL: https://issues.jboss.org/browse/ERT-73 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Priority: Blocker > Labels: bzira, wst.json > Fix For: Neon (4.6) M6 > > > After installing the JSON editor from http://download.eclipse.org/webtools/downloads/drops/R3.8.0/S-3.8.0M5-201... it appears at least 1 icon is missing from the build. It's pretty visible in http://screencast.com/t/SVig7rgdDY -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-68) Rename Chome Developer Tools features and include them into main JSDT Debug feature [EBZ#486504]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/ERT-68?page=com.atlassian.jira.plugin.sys... ] Denis Golovin reassigned ERT-68: -------------------------------- Assignee: Denis Golovin > Rename Chome Developer Tools features and include them into main JSDT Debug feature [EBZ#486504] > ------------------------------------------------------------------------------------------------ > > Key: ERT-68 > URL: https://issues.jboss.org/browse/ERT-68 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Denis Golovin > Labels: 3.8_M6, Debug, bzira > Fix For: Neon (4.6) M6 > > > We need to rename ChDT features (according to the JSDT ones) and to include them into the main JSDT Debug Features in order to include ChDT into the overal WTP build. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-557) Errors about unknown categories when installing from JBoss Central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-557?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-557: -------------------------------- Assignee: Paul Leacu > Errors about unknown categories when installing from JBoss Central > ------------------------------------------------------------------ > > Key: JBTIS-557 > URL: https://issues.jboss.org/browse/JBTIS-557 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1.0.Beta2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: log.txt > > > Run JBDS with the following vm args > {code} > -Djboss.discovery.directory.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Beta1/earlyaccess/jbosstools-directory.xml > -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Beta1/ > -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Beta1/earlyaccess/ > -Djboss.discovery.earlyaccess.list.url=http://download.jboss.org/jbosstools/mars/staging/updates/integration-stack/discovery/jbosstools-earlyaccess.properties > {code} > and switch to Software/Update in JBoss Central and open Errors view -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-558) Cannot install Fuse Data Transformation when offline

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-558?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-558: -------------------------------- Assignee: Paul Leacu > Cannot install Fuse Data Transformation when offline > ---------------------------------------------------- > > Key: JBTIS-558 > URL: https://issues.jboss.org/browse/JBTIS-558 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Beta1 > Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1 EA Zip file > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > > Cannot install Fuse Data Transformation when offline. > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) > Missing requirement: org.jboss.tools.fuse.transformation.core 8.0.0.Beta1-v20160211-1659-B703 requires 'bundle javax.xml.bind 2.2.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Fuse Tooling Data Transformation 8.0.0.Beta1-v20160211-1659-B703 (org.jboss.tools.fuse.transformation.feature.feature.group 8.0.0.Beta1-v20160211-1659-B703) > To: org.jboss.tools.fuse.transformation.core [8.0.0.Beta1-v20160211-1659-B703] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21422) Server adapter editor: details should be editable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21422?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21422: ------------------------------------------ [~scabanovich] your logic seems legit. But there's still one open question here: We currently only save to the project settings file, not to the server. The basic idea in v2 was to be able to easily recreate the adapter when switching Eclipse instances while using the same workspace. In v2 there was a checkbox in the server editor that allowed the user to override the project settings and save to the server adapter. We're currently missing this logic and need to decide whether this is still a valid approach in v3. I'm not all sure. [~maxandersen] can you comment? > Server adapter editor: details should be editable > ------------------------------------------------- > > Key: JBIDE-21422 > URL: https://issues.jboss.org/browse/JBIDE-21422 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Currently when I open a server adapter overview (by double click on a server adapter) there is whole section of details to which project it is bind to, paths etc. in the Project Settings section. This area is not editable. It would be nice to allow user modify this, to allow to choose different eclipse project or fix path if it was filled in wrong... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.1+

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21307?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21307: ------------------------------------- Description: Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.1. Versions below require the user to manually {code} oc login --server=<server that we publish to> --token=... {code} We should check the version and warn if the user is using an oc that is older than this. the changelog of oc in [v1.1.1|https://github.com/openshift/origin/releases/tag/v1.1.1] states the following refering to the issue: {quote} Support some of the global rsync flags on oc rsync for displaying progress information - not supported on all rsync backends (like tar) {quote} was: Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.0.1. Versions below require the user to manually {code} oc login --server=<server that we publish to> --token=... {code} We should check the version and warn if the user is using an oc that is older than this. > Server Adapter: ensure oc binary that's used for rsync is v1.1.1+ > ----------------------------------------------------------------- > > Key: JBIDE-21307 > URL: https://issues.jboss.org/browse/JBIDE-21307 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: oc_binary, openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.1. Versions below require the user to manually > {code} > oc login --server=<server that we publish to> --token=... > {code} > We should check the version and warn if the user is using an oc that is older than this. > the changelog of oc in [v1.1.1|https://github.com/openshift/origin/releases/tag/v1.1.1] states the following refering to the issue: > {quote} > Support some of the global rsync flags on oc rsync for displaying progress information - not supported on all rsync backends (like tar) > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21307) Server Adapter: ensure oc binary that's used for rsync is v1.1.1+

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21307?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21307: ------------------------------------- Summary: Server Adapter: ensure oc binary that's used for rsync is v1.1.1+ (was: Server Adapter: ensure oc binary that's used for rsync is v1.1.0.1+) > Server Adapter: ensure oc binary that's used for rsync is v1.1.1+ > ----------------------------------------------------------------- > > Key: JBIDE-21307 > URL: https://issues.jboss.org/browse/JBIDE-21307 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: oc_binary, openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > Because of https://github.com/openshift/origin/issues/6109 publishing with the server adapter (which does a oc rsync behind the scenes) only properly works with oc v1.1.0.1. Versions below require the user to manually > {code} > oc login --server=<server that we publish to> --token=... > {code} > We should check the version and warn if the user is using an oc that is older than this. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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