May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22379) Server editor: closing it before the widgets are enabled ends up in "widget disposed" error

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22379?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22379: ----------------------------------------------- If there is an opportunity to merge the PR to base, then the PR to openshift is not needed. Otherwise, the PR to openshift solves the issue, and the PR to base may be merged at a future convenience. > Server editor: closing it before the widgets are enabled ends up in "widget disposed" error > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22379 > URL: https://issues.jboss.org/browse/JBIDE-22379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter_editor > Fix For: 4.4.0.Alpha2 > > Attachments: widget-disposed.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22379) Server editor: closing it before the widgets are enabled ends up in "widget disposed" error

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22379?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-22379: ------------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1170, https://github.com/jbosstools/jbosstools-base/pull/506 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1170) > Server editor: closing it before the widgets are enabled ends up in "widget disposed" error > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22379 > URL: https://issues.jboss.org/browse/JBIDE-22379 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter_editor > Fix For: 4.4.0.Alpha2 > > Attachments: widget-disposed.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22248) Some CI jobs fail at deploying to Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22248. ------------------------------ Resolution: Done I've reverted the changes I did to jbosstools-build and jbosstools-target-platforms because the load balancer is working again. Red deer job is blue again, as is parent pom. TP matrix is still running. > Some CI jobs fail at deploying to Nexus > --------------------------------------- > > Key: JBIDE-22248 > URL: https://issues.jboss.org/browse/JBIDE-22248 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha2 > > > Nick, can you take a look why mvn deploy fails here? > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > It worked for us in the past. > It says: > {code} > [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 04:49 min > [INFO] Finished at: 2016-04-26T09:42:02-04:00 > [INFO] Final Memory: 19M/612M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > {code} > I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team? > Cc: [~rawagner] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22386) Server Editor: Select different service takes too long

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22386?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22386 at 5/19/16 5:19 PM: ------------------------------------------------------------------------ I suggest enhancing WizardUtils class that has methods WizardUtils.runInWizard(... IWizardContainer ...) by adding to it new methods WizardUtils.runInUI(... IRunnableContext ...). Old methods may be implemented by calls to the new ones because IWizardContainer extends IRunnableContext. Then we may call runInUI from editors using the application window as the runnable context. For this issue, call WizardUtils.runInUI(new UIJob("Select a service") { /* call dialog here*/ }, PlatformUI.getWorkbench().getActiveWorkbenchWindow()) will disable the button while the dialog is starting, and show progress for the job. was (Author: scabanovich): I suggest enhancing WizardUtils class that has methods WizardUtils.runInWizard(... IWizardContainer ...) by adding to it new methods WizardUtils.runInUI(... IRunnableContext ...). Old methods may be implemented by calls to the new ones because IWizardContainer extends IRunnableContext. Then we may call runInUI from editors using the application window as the runnable context. For this issue, call WizardUtils.runInUI(new UIJob("Select a wiard") { /* call dialog here*/ }, PlatformUI.getWorkbench().getActiveWorkbenchWindow()) will disable the button while the dialog is starting, and show progress for the job. > Server Editor: Select different service takes too long > ------------------------------------------------------ > > Key: JBIDE-22386 > URL: https://issues.jboss.org/browse/JBIDE-22386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3, server_editor > > Trying to select a different service for an OpenShift 3 Server Adapter in Server Editor takes too long. After click on the Select... button it takes ~2-3 seconds to open dialog to select a different service. It would be ok to take it that time if there would be some indication that something is happening, but there is no job while "something" is happening. > Also clicking on the button multiple times (if it is not responsible, I clicked again and again and again), it takes a bit longer and open multiple dialogs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22386) Server Editor: Select different service takes too long

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22386?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22386: ----------------------------------------------- I suggest to enhance WizardUtils class that has methods WizardUtils.runInWizard(... IWizardContainer ...) by adding to it new methods WizardUtils.runInUI(... IRunnableContext ...). Old methods may be implemented by calls to the new ones because IWizardContainer extends IRunnableContext. Then we may call runInUI from editors using the application window as the runnable context. For this issue, call WizardUtils.runInUI(new UIJob("Select a wiard") { /* call dialog here*/ }, PlatformUI.getWorkbench().getActiveWorkbenchWindow()) will disable the button while the dialog is starting, and show progress for the job. > Server Editor: Select different service takes too long > ------------------------------------------------------ > > Key: JBIDE-22386 > URL: https://issues.jboss.org/browse/JBIDE-22386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3, server_editor > > Trying to select a different service for an OpenShift 3 Server Adapter in Server Editor takes too long. After click on the Select... button it takes ~2-3 seconds to open dialog to select a different service. It would be ok to take it that time if there would be some indication that something is happening, but there is no job while "something" is happening. > Also clicking on the button multiple times (if it is not responsible, I clicked again and again and again), it takes a bit longer and open multiple dialogs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22386) Server Editor: Select different service takes too long

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22386?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22386 at 5/19/16 5:16 PM: ------------------------------------------------------------------------ I suggest enhancing WizardUtils class that has methods WizardUtils.runInWizard(... IWizardContainer ...) by adding to it new methods WizardUtils.runInUI(... IRunnableContext ...). Old methods may be implemented by calls to the new ones because IWizardContainer extends IRunnableContext. Then we may call runInUI from editors using the application window as the runnable context. For this issue, call WizardUtils.runInUI(new UIJob("Select a wiard") { /* call dialog here*/ }, PlatformUI.getWorkbench().getActiveWorkbenchWindow()) will disable the button while the dialog is starting, and show progress for the job. was (Author: scabanovich): I suggest to enhance WizardUtils class that has methods WizardUtils.runInWizard(... IWizardContainer ...) by adding to it new methods WizardUtils.runInUI(... IRunnableContext ...). Old methods may be implemented by calls to the new ones because IWizardContainer extends IRunnableContext. Then we may call runInUI from editors using the application window as the runnable context. For this issue, call WizardUtils.runInUI(new UIJob("Select a wiard") { /* call dialog here*/ }, PlatformUI.getWorkbench().getActiveWorkbenchWindow()) will disable the button while the dialog is starting, and show progress for the job. > Server Editor: Select different service takes too long > ------------------------------------------------------ > > Key: JBIDE-22386 > URL: https://issues.jboss.org/browse/JBIDE-22386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3, server_editor > > Trying to select a different service for an OpenShift 3 Server Adapter in Server Editor takes too long. After click on the Select... button it takes ~2-3 seconds to open dialog to select a different service. It would be ok to take it that time if there would be some indication that something is happening, but there is no job while "something" is happening. > Also clicking on the button multiple times (if it is not responsible, I clicked again and again and again), it takes a bit longer and open multiple dialogs. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22412) Enhance JobChainBuilder with conditions for starting the next job

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-22412: --------------------------------------------- Summary: Enhance JobChainBuilder with conditions for starting the next job Key: JBIDE-22412 URL: https://issues.jboss.org/browse/JBIDE-22412 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Viacheslav Kabanovich For example, if the chain of jobs is loading content of a wizard or an editor, and user may close it before jobs are completed, there is no need to schedule the next job in the chain when the previous job is done. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21818?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21818: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > 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 > Priority: Minor > Labels: openshift_v3 > Fix For: 4.4.0.Alpha3 > > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22243: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha3 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21828?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21828: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.0.Alpha2) > 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: Jeff Cantrill > Fix For: 4.4.0.Alpha3 > > 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)

9 years, 10 months

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