March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3609) update splashscreen, about gfx, start icon for developers.redhat.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3609?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3609: ----------------------------- Component/s: build installer > update splashscreen, about gfx, start icon for developers.redhat.com > -------------------------------------------------------------------- > > Key: JBDS-3609 > URL: https://issues.jboss.org/browse/JBDS-3609 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, installer, p2-product > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.1.0.CR1 > > > update splashscreen, about gfx, start icon for developers.redhat.com -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21821: ---------------------------------------- Providing a more recent EGit (inluding the importer bundle) to users via composite, TP or whatever should work. However, it's another delivery, that should probably be QE'd and so on. > JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2 > ---------------------------------------------------------------- > > Key: JBIDE-21821 > URL: https://issues.jboss.org/browse/JBIDE-21821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, marketplace > Reporter: Thomas Mäder > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: FrameworkEvent ERROR.txt, jbt-error, jgit40_41_JBDS.installed.txt, jgit40_41_JBT.installed.txt > > > Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break. > # Install Eclipse 4.5.2 > # In the Marketplace, search for "jboss developer studio" > # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA > # Install it > # Restart > # Observe: the EGit views and preferences are missing > # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21821) JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21821: ------------------------------------ What if, for existing JBT 4.3.0.Final users, we simply add http://download.eclipse.org/egit/updates-4.1.1/ into the composite TP site http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/ so people can either install the 4.0.x bits or the 4.1.x bits, as dictated by p2? > JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2 > ---------------------------------------------------------------- > > Key: JBIDE-21821 > URL: https://issues.jboss.org/browse/JBIDE-21821 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, marketplace > Reporter: Thomas Mäder > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: FrameworkEvent ERROR.txt, jbt-error, jgit40_41_JBDS.installed.txt, jgit40_41_JBT.installed.txt > > > Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break. > # Install Eclipse 4.5.2 > # In the Marketplace, search for "jboss developer studio" > # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA > # Install it > # Restart > # Observe: the EGit views and preferences are missing > # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21823: ---------------------------------- Sprint: devex #3 February 2016 > Unable to re-edit Service config > -------------------------------- > > Key: JBIDE-21823 > URL: https://issues.jboss.org/browse/JBIDE-21823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.CR1 > > > Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes. > Steps to reproduce: > - select a service in the OpenShift Explorer > - click on the {{Edit...}} command. > - in the JSON editor for the service config, note the resource version. Eg: > {code} > { > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38301", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > }, > ... > {code} > - make some changes and save > - the service config version should have incremented: > {code} > { > "kind" : "Service", > "apiVersion" : "v1", > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38390", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > } > .... > {code} > - close the config editor > - re-open the config editor > *ASSERT: the editor displays the latest config* > *FAIL the editor displays the initial config* > *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version* > {code} > Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again > Could not update resource jee-sample: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "jee-sample", > "kind": "services" > }, > "code": 409 > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-21828: ------------------------------------- Assignee: Xavier Coulon > OpenShift Explorer view flickers when refreshing a service > ---------------------------------------------------------- > > Key: JBIDE-21828 > URL: https://issues.jboss.org/browse/JBIDE-21828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Attachments: Screenshot 2016-03-08 10.32.39.png > > > When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls. > Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod. > Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services. > Custom/added logs in the console: > {code} > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21828) OpenShift Explorer view flickers when refreshing a service

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21828: ---------------------------------- Sprint: devex #3 February 2016 > OpenShift Explorer view flickers when refreshing a service > ---------------------------------------------------------- > > Key: JBIDE-21828 > URL: https://issues.jboss.org/browse/JBIDE-21828 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Attachments: Screenshot 2016-03-08 10.32.39.png > > > When calling the "Refresh" command on a service, the tree view flickers because of too many refresh calls. > Adding some traces revealed 25 calls to {{BaseExplorerContentProvider#refreshViewer(Object)}}, which seems way too much for a service with a single pod. > Attachement: screenshot of the OpenShift Server view, showing 2 projects, one of which has 3 services. > Custom/added logs in the console: > {code} > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/mongodb > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/jee-sample > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from sample/nodejs-mongodb-example > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > Refreshing viewer from org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectUIModel@431dafbc > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3676) BrowserSim cannot start on Azul openjdk (windows)

by Jan Richter (JIRA)

Jan Richter created JBDS-3676: --------------------------------- Summary: BrowserSim cannot start on Azul openjdk (windows) Key: JBDS-3676 URL: https://issues.jboss.org/browse/JBDS-3676 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: browsersim Affects Versions: 9.1.0.CR1 Reporter: Jan Richter Running JBDS on Azul OpenJDK 8, Windows 10. Starting BrowserSim fails with the following error: {noformat} BrowserSim has failed to start with the following error: "To use BrowserSim please install Safari or run BrowserSim with Oracle Java 7u7 and higher." Also see BrowserSim FAQ. {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20984) Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20984?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-20984: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.4.x) > Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20984 > URL: https://issues.jboss.org/browse/JBIDE-20984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Final > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > Attachments: JBoss - JBoss Central - JBoss Developer Studio _001.png > > > Default JBDS installation contains "Arquillia Cruiser" (missing n) view. Arquillian from central isn't installed. View is missing icon and does not work at all - if you try to open it you will get view with "Could not create the view: org.jboss.tools.arquillian.ui.views.arquillianView" text. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20984) Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20984?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-20984. ----------------------------------- Resolution: Done The upstream bug has been fixed on Neon. The issue can still be reproduced on Mars.2. > Arquillian Cruiser view is in default JBDS or JBT installation if you use an old workspace with Arquillian projects > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20984 > URL: https://issues.jboss.org/browse/JBIDE-20984 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Final > Reporter: Rastislav Wagner > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > Attachments: JBoss - JBoss Central - JBoss Developer Studio _001.png > > > Default JBDS installation contains "Arquillia Cruiser" (missing n) view. Arquillian from central isn't installed. View is missing icon and does not work at all - if you try to open it you will get view with "Could not create the view: org.jboss.tools.arquillian.ui.views.arquillianView" text. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 (Beta)

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21038: --------------------------------------- The issue can't be reproduced after applying the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=478962 It has been applied only to Neon. It would also be good to apply the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=354842 (https://git.eclipse.org/r/60027) that fixes a potential UI freeze in all SWT ports. See https://issues.jboss.org/browse/JBIDE-21816?focusedCommentId=13172449&pag... > Software/Update page is not working on Fedora 23 (Beta) > ------------------------------------------------------- > > Key: JBIDE-21038 > URL: https://issues.jboss.org/browse/JBIDE-21038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, upstream > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%. > java version "1.8.0_65" > gtk3 version 3.18.2 > jstack: http://pastebin.com/a7U02yjt > Everything is fine with GTK2. -- 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