February 2016 - jbosstools-issues

[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 reassigned JBIDE-21665: ------------------------------------- Assignee: Jeff Cantrill > 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 > Assignee: Jeff Cantrill > 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-76) Sync of IJSONModel with editor should be improved/fixed [EBZ#486860]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-76?page=com.atlassian.jira.plugin.sys... ] Victor Rubezhny updated ERT-76: ------------------------------- Story Points: 20 > Sync of IJSONModel with editor should be improved/fixed [EBZ#486860] > -------------------------------------------------------------------- > > Key: ERT-76 > URL: https://issues.jboss.org/browse/ERT-76 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: bzira, wst.json > > IMHO the sync of IJSONModel with editor is the most important and should be done/fixed before fixing, improving other features. But it is the most hard too. > At first, we should validate the IJSONModel API > The big problem with JSON Editor is that the IJSONModel, IJSONPair, IJSONDocument, etc. There are a lot of copy/paste from XML/CSS plugins so this model and the implementation should be really fixed/improved. > For instance completion works when editor is opened, but it is broken after some changes of the text editor. It is because IJSONModel is not very well sync. > The most bugs that I see like: > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486606 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=485694 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486849 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486524 > are linked to this sync problem. > So tests https://github.com/angelozerr/eclipse-wtp-json/blob/master/core/org.eclip... must be completed when sync of model is improved. > I will try to create a patch for adding tests https://bugs.eclipse.org/bugs/show_bug.cgi?id=486238 > It's a very hard task, so good luck to do that. -- 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 commented on JBTIS-558: ---------------------------------- Hey [~nickboldt] - another question for you *javax.xml.bind* was around in the Luna SR1a jbt requirements mirror. It then disappeared for the Luna SR2-RC3 mirror (and is still gone). Does this need to be dragged into locus? wdyt? > 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] (ERT-76) Sync of IJSONModel with editor should be improved/fixed [EBZ#486860]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-76?page=com.atlassian.jira.plugin.sys... ] Victor Rubezhny reassigned ERT-76: ---------------------------------- Assignee: Victor Rubezhny > Sync of IJSONModel with editor should be improved/fixed [EBZ#486860] > -------------------------------------------------------------------- > > Key: ERT-76 > URL: https://issues.jboss.org/browse/ERT-76 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Labels: bzira, wst.json > > IMHO the sync of IJSONModel with editor is the most important and should be done/fixed before fixing, improving other features. But it is the most hard too. > At first, we should validate the IJSONModel API > The big problem with JSON Editor is that the IJSONModel, IJSONPair, IJSONDocument, etc. There are a lot of copy/paste from XML/CSS plugins so this model and the implementation should be really fixed/improved. > For instance completion works when editor is opened, but it is broken after some changes of the text editor. It is because IJSONModel is not very well sync. > The most bugs that I see like: > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486606 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=485694 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486849 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486524 > are linked to this sync problem. > So tests https://github.com/angelozerr/eclipse-wtp-json/blob/master/core/org.eclip... must be completed when sync of model is improved. > I will try to create a patch for adding tests https://bugs.eclipse.org/bugs/show_bug.cgi?id=486238 > It's a very hard task, so good luck to do that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-32) Create icons for bower/npm utilities' wizards and actions [EBZ#484218]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-32?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-32: ------------------------------- Assignee: Victor Rubezhny > Create icons for bower/npm utilities' wizards and actions [EBZ#484218] > ---------------------------------------------------------------------- > > Key: ERT-32 > URL: https://issues.jboss.org/browse/ERT-32 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Labels: General, bzira > > We need to create icons for wizards and actions for bower and npm dependency management tools to be shown for: > - Init Wizard > - Install Action > - Update Action > The icons are to be based on the according ones for bower and npm utilities logos: > For Bower: > - Site: http://bower.io > - License: > https://github.com/bower/bower/blob/master/README.md#license > https://github.com/bower/bower/blob/master/LICENSE > - Logo Info: http://bower.io/docs/about/#logo > - Logo Image: http://bower.io/img/bower-logo.png > For NPM: > - Site: https://www.npmjs.com > - License: > https://docs.npmjs.com/policies/license > https://www.npmjs.com/policies/npm-license > https://github.com/npm/npm/blob/master/LICENSE > - Trademark And Logo policies: > https://docs.npmjs.com/policies/trademark#the-npm-trademark-policy > https://docs.npmjs.com/policies/trademark#the-npm-logo > - Logo Images: > https://github.com/npm/npm/blob/master/html/npm.png > https://github.com/npm/npm/blob/master/html/n-large.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-32) Create icons for bower/npm utilities' wizards and actions [EBZ#484218]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-32?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-32: ---------------------------- Sprint: devex #2 February 2016 > Create icons for bower/npm utilities' wizards and actions [EBZ#484218] > ---------------------------------------------------------------------- > > Key: ERT-32 > URL: https://issues.jboss.org/browse/ERT-32 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Labels: General, bzira > > We need to create icons for wizards and actions for bower and npm dependency management tools to be shown for: > - Init Wizard > - Install Action > - Update Action > The icons are to be based on the according ones for bower and npm utilities logos: > For Bower: > - Site: http://bower.io > - License: > https://github.com/bower/bower/blob/master/README.md#license > https://github.com/bower/bower/blob/master/LICENSE > - Logo Info: http://bower.io/docs/about/#logo > - Logo Image: http://bower.io/img/bower-logo.png > For NPM: > - Site: https://www.npmjs.com > - License: > https://docs.npmjs.com/policies/license > https://www.npmjs.com/policies/npm-license > https://github.com/npm/npm/blob/master/LICENSE > - Trademark And Logo policies: > https://docs.npmjs.com/policies/trademark#the-npm-trademark-policy > https://docs.npmjs.com/policies/trademark#the-npm-logo > - Logo Images: > https://github.com/npm/npm/blob/master/html/npm.png > https://github.com/npm/npm/blob/master/html/n-large.png -- 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 commented on JBTIS-557: ---------------------------------- [~nickboldt] - I'm not sure how this was working before. I saw angularjs-eclipse-feature was using "experimental" early access so I tried using that - but I get the same error: {code} !ENTRY org.eclipse.mylyn.discovery.core 4 0 2016-02-15 15:50:26.625 !MESSAGE Unknown category 'com.jboss.jbds.discovery.certification.experimental.earlyaccess' referenced by connector 'jboss.integr ation-stack.bundle.bpr' declared in com.jboss.jbds.central.discovery.integration_stack.earlyaccess_9.0.0.Beta1_v20160215_1445_B16 8.jar_1423367654270837465.jar {code} Do I need to declare the certificationId extension point category locally (in my plugin.xml) for either com.jboss.jbds.discovery.certification.experimental.earlyaccesscom.jboss.jbds.discovery.certification.supported.earlyaccess?? I thought it founds the extension in com.jboss.jbds.central.discovery.earlyaccess/plugin.xml somehow... > 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] (ERT-24) JSDT to utilize org.eclipse.wst.validation.validatorV2 extension point [EBZ#482841]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-24?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-24: ---------------------------- Sprint: devex #2 February 2016 > JSDT to utilize org.eclipse.wst.validation.validatorV2 extension point [EBZ#482841] > ----------------------------------------------------------------------------------- > > Key: ERT-24 > URL: https://issues.jboss.org/browse/ERT-24 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > Use org.eclipse.wst.validation.validatorV2 to allow 3rd parties to introduce new validator. > In the process the internal syntax validation should also be moved to use the same extension point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-24) JSDT to utilize org.eclipse.wst.validation.validatorV2 extension point [EBZ#482841]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-24?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-24: ---------------------------- Story Points: 25 > JSDT to utilize org.eclipse.wst.validation.validatorV2 extension point [EBZ#482841] > ----------------------------------------------------------------------------------- > > Key: ERT-24 > URL: https://issues.jboss.org/browse/ERT-24 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Trivial > Labels: 3.8_M6, General, bzira > Fix For: Neon (4.6) M6 > > > Use org.eclipse.wst.validation.validatorV2 to allow 3rd parties to introduce new validator. > In the process the internal syntax validation should also be moved to use the same extension point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-24) JSDT to utilize org.eclipse.wst.validation.validatorV2 extension point [EBZ#482841]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-24?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan reassigned ERT-24: ------------------------------- Assignee: Gorkem Ercan (was: Max Rydahl Andersen) > JSDT to utilize org.eclipse.wst.validation.validatorV2 extension point [EBZ#482841] > ----------------------------------------------------------------------------------- > > Key: ERT-24 > URL: https://issues.jboss.org/browse/ERT-24 > 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 > > > Use org.eclipse.wst.validation.validatorV2 to allow 3rd parties to introduce new validator. > In the process the internal syntax validation should also be moved to use the same extension point. -- 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