February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21689) 82 updated schema unavailable on jboss.org

by Rob Stryker (JIRA)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21665) Scaling OS3 application does not work properly

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21665?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21665: --------------------------------------- [~adietish] I think refreshing before scaling is probably a reasonable solution but there is an underlying bug here which probably is pervasive across the plugin. We should have received a change notification from the watch, but we probably don't reasonably guarantee that we have the latest version of a resource. Since we are mostly readonly, this generally isn't an issue, but we should probably do a GET before we take any action that requires us to update a resource. The larger question might be how to ensure that 'get' is propagated to all the listeners. This change https://issues.jboss.org/browse/OSJC-238 is probably the one that gets us towards it. > Scaling OS3 application does not work properly > ---------------------------------------------- > > Key: JBIDE-21665 > URL: https://issues.jboss.org/browse/JBIDE-21665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > Attachments: edit_error.png > > > When I am trying to scale application via tooling, first attempt to set replicas amount works but every consecutive attempt to edit same resource fails. See following screenshot of the error followed by stack trace > !edit_error.png! > {code} > com.openshift.restclient.OpenShiftException: Could not update resource eap-app-1: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:480) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:247) > at org.jboss.tools.openshift.internal.ui.property.OpenShiftResourceDocumentProvider$2.run(OpenShiftResourceDocumentProvider.java:92) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.openshift.internal.restclient.http.HttpClientException: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:226) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:191) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.put(UrlConnectionHttpClient.java:119) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:243) > ... 2 more > Caused by: java.io.IOException: Server returned HTTP response code: 409 for URL: https://10.1.2.2:8443/api/v1/namespaces/project01/replicationcontrollers/... > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1840) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:187) > ... 4 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-4) Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-4?page=com.atlassian.jira.plugin.syst... ] Max Rydahl Andersen updated ERT-4: ---------------------------------- Sprint: devex #1 February 2016, devex #2 February 2016 (was: devex #1 February 2016) > Ignore undefined HTML attributes, elements validation with extension point [EBZ#443097] > --------------------------------------------------------------------------------------- > > Key: ERT-4 > URL: https://issues.jboss.org/browse/ERT-4 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Labels: bzira, wst.html > Fix For: Neon (4.6) M6 > > > I'm developping a plugin for AngularJS https://github.com/angelozerr/angularjs-eclipse which is based on WTP. > I have implemented validation for Angular which ignores (ng-* attributes, etc) with Java code without using your feature https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980 > But there is some limitation and it should be fantastic if WTP provides an extension point like this : > --------------------------------------------------- > public interface IHTMLIgnoreValidator { > boolean shouldValidateAttributeName(IProject project, Element target, String attrName); > boolean shouldValidateElementName((IProject project, Element target); > } > --------------------------------------------------- > For more information please read https://github.com/angelozerr/angularjs-eclipse/issues/80#issuecomment-53... > https://bugs.eclipse.org/bugs/show_bug.cgi?id=415980 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-36) Disable TypeBinding and deprecate internal ast model [EBZ#484598]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-36?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-36: ----------------------------------- Sprint: devex #1 February 2016, devex #2 February 2016 (was: devex #1 February 2016) > Disable TypeBinding and deprecate internal ast model [EBZ#484598] > ----------------------------------------------------------------- > > Key: ERT-36 > URL: https://issues.jboss.org/browse/ERT-36 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Labels: 3.8_M5, General, bzira > Fix For: Neon (4.6) M6 > > > Disable type binding to allow the replacement for a new Parser. > maintaining 2 ast models is wasteful deprecate org.eclipse.wst.jsdt.internal.compiler.ast model in favor of dom ast model. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-19) JSDT should support the use of sourcevalidation extension point [EBZ#481344]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-19?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-19: ----------------------------------- Sprint: devex #1 February 2016, devex #2 February 2016 (was: devex #1 February 2016) > 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) M6 > > > 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)

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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-68?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-68: ----------------------------------- Sprint: devex #1 February 2016, devex #2 February 2016 (was: devex #1 February 2016) > 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 > 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] (ERT-62) Refactor JSDT Code Completion [EBZ#486776]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-62?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-62: ----------------------------------- Sprint: devex #1 February 2016, devex #2 February 2016 (was: devex #1 February 2016) > Refactor JSDT Code Completion [EBZ#486776] > ------------------------------------------ > > Key: ERT-62 > URL: https://issues.jboss.org/browse/ERT-62 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Assignee: Ian Stewart-Binks > Labels: General, bzira > > The current code completion modules depend on JSDT's current internal AST model, and type binding. JSDT will be disabling type binding and will be deprecating the internal AST model. As such, the code completion engine needs to be refactored in such a way that complies with the new AST model. JSDT is expected to provide an elegant and useful set of code completion suggestions. > A proposal base for the code completion engine should include, but is not necessarily limited to: > - Keywords > - Identifiers (declared variables and functions in currently open JS file) > - Recently used methods of functions (currently open JS file as a bare minimum) > All proposals should be made where they are deemed practical. ECMA5 keywords should be supported first. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-67?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-67: ----------------------------------- Sprint: devex #1 February 2016, devex #2 February 2016 (was: devex #1 February 2016) > 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 > 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] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21302: ---------------------------------------- Sprint: devex #0 January 2016, devex #1 February 2016, devex #2 February 2016 (was: devex #0 January 2016, devex #1 February 2016) > Removing user from credentials framework while not authenticated to secure storage should not work > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21302 > URL: https://issues.jboss.org/browse/JBIDE-21302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > Removing credentials (which are stored in secure storage) using > CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage". -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-54?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-54: ----------------------------------- Sprint: devex #1 February 2016, devex #2 February 2016 (was: devex #1 February 2016) > 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

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