March 2016 - jbosstools-issues - Jboss List Archives

[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 reassigned ERT-15: ------------------------------- Assignee: Gorkem Ercan > [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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-21) Update or replace JSDT parser to support ES6 [EBZ#481706]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-21?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-21: ------------------------------- Assignee: Gorkem Ercan > Update or replace JSDT parser to support ES6 [EBZ#481706] > --------------------------------------------------------- > > Key: ERT-21 > URL: https://issues.jboss.org/browse/ERT-21 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > Support ecma-262 standard Javascript language features with the JSDT parser so that other functionality can provide relevant support -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21818) Too large margins in wizards

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21818: ----------------------------------------------- The patch for JBIDE-20755 adds to margin more 15. Was it an improvement of margin width? > Too large margins in wizards > ---------------------------- > > Key: JBIDE-21818 > URL: https://issues.jboss.org/browse/JBIDE-21818 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > Attachments: Screenshot 2016-03-04 11.19.59.png > > > Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general. > See attached screenshot as an example -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21818) Too large margins in wizards

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21818: --------------------------------------- See the patch for JBIDE-20755 > Too large margins in wizards > ---------------------------- > > Key: JBIDE-21818 > URL: https://issues.jboss.org/browse/JBIDE-21818 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > Attachments: Screenshot 2016-03-04 11.19.59.png > > > Some wizard have too large margins, wasting space and making them inconsistent with the other Eclipse wizards in general. > See attached screenshot as an example -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21816) Table is not refreshed properly in SWT_GTK3

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21816?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21816: --------------------------------------- {quote} Do you have enough entries in tables for them to display vertical scroll? Without that scroll, table is rendered correctly. {quote} I have tried to resize the wizard in order to show the vertical scroll, but it isn't shown even though there are enough entries. That is the same for GTK 3.10, GTK 3.14 and GTK 3.16. {quote} What Linux distro are you using with 3.10? {quote} Ubuntu 15.04 (GTK 3.14.3), compiled GTK 3.10.8, GTK 3.16.7 and GTK 3.18.7 {quote} I have fc23/GTK 3.18 and I never experienced JBIDE-21038. {quote} I have tested Ubuntu 15.04, compiled GTK 3.18.7, Mars.2, JBT 4.3.1 nightly as follows: - created Openshift 3 connection with a token on the secure storage - restarted Eclipse - tried to open the Openshift connection The Secure Storage Password wizard isn't shown. It shows up when I minimize all editors/views or exit Eclipse. The issue is always reproducible. It doesn't happen on Neon or GTK3 <= 3.16. The patch for https://bugs.eclipse.org/bugs/show_bug.cgi?id=478962 fixes the issue. > Table is not refreshed properly in SWT_GTK3 > ------------------------------------------- > > Key: JBIDE-21816 > URL: https://issues.jboss.org/browse/JBIDE-21816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > This issue was found while testing JBIDE-21815 and description to that issue fits to what happens in SWT_GTK3 with table. Difference is that the other issue is caused by some model failures and can be reproduced on all OS, and this case is relevant only to SWT_GTK3 when wizard model works without failures. > Steps for some generic wizard (Deploy Image to Openshift is an example). > 1. Create a wizard with two pages. First page has some text input, second table. Content of table is refreshed on change of text input on the first page. Input object for the table is the same, only content provider returns new values. Table has scroll, and content should be large enough to make scroll appear (without scroll, the issue is not reproduced). > 2. Change text input on the first page, and push 'Next->' to open the second page. > 3. At the very first navigating to the second page, the content of the table is correct, as provided by the logic binding the text input and the table. > 4. Go back to the first page and change text input. > 5. Again navigate to the second page. > 6. Failure - content of the table remains as it was for the previous text input. > 7. Recovering - just pass mouse over the table, its data in cells passed is refreshed. That means that table model is refreshed, but rendering was not completed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20568) Duplicate templates in different OpenShift projects are not distinguishable from each other

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20568?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20568: ----------------------------------------------- Namespace is added to the label of template. [~adietish], please take a look at the pull request. > Duplicate templates in different OpenShift projects are not distinguishable from each other > ------------------------------------------------------------------------------------------- > > Key: JBIDE-20568 > URL: https://issues.jboss.org/browse/JBIDE-20568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png, TemplateLableWithNamespace.png > > > New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20568) Duplicate templates in different OpenShift projects are not distinguishable from each other

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20568?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-20568: ------------------------------------------ Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) > Duplicate templates in different OpenShift projects are not distinguishable from each other > ------------------------------------------------------------------------------------------- > > Key: JBIDE-20568 > URL: https://issues.jboss.org/browse/JBIDE-20568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png, TemplateLableWithNamespace.png > > > New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20568) Duplicate templates in different OpenShift projects are not distinguishable from each other

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20568?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-20568: ------------------------------------------ Attachment: TemplateLableWithNamespace.png > Duplicate templates in different OpenShift projects are not distinguishable from each other > ------------------------------------------------------------------------------------------- > > Key: JBIDE-20568 > URL: https://issues.jboss.org/browse/JBIDE-20568 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Jeff Cantrill > Priority: Minor > Fix For: 4.4.x > > Attachments: screenshot-1.png, TemplateLableWithNamespace.png > > > New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-93: -------------------------------------- Summary: 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 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 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21820) Update service-manager parsing for cygwin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21820?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21820: -------------------------------- Affects Version/s: 4.3.1.Beta2 (was: 4.4.0.Alpha1) > Update service-manager parsing for cygwin > ----------------------------------------- > > Key: JBIDE-21820 > URL: https://issues.jboss.org/browse/JBIDE-21820 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > Link to https://github.com/projectatomic/vagrant-service-manager/issues/10 > If the service-manager issue ever gets solved, we'll need to update our parsing code to check for cygwin. -- 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 March 2016