June 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-27300) Exception from databinding in create component wizard

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-27300: ---------------------------------- Summary: Exception from databinding in create component wizard Key: JBIDE-27300 URL: https://issues.redhat.com/browse/JBIDE-27300 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.15.0.Final Reporter: Jeff MAURY Fix For: 4.16.x The databinding framework logs the following exceptions when the create dialog wizard is used: {code:java} !ENTRY org.eclipse.core.databinding 2 0 2020-06-04 16:49:25.787 !MESSAGE Could not attach listener to org.jboss.tools.openshift.core.odo.ComponentTypesDeserializer$1@24f97c59 !STACK 0 java.lang.NoSuchMethodException: org.jboss.tools.openshift.core.odo.ComponentTypesDeserializer$1.addPropertyChangeListener(java.beans.PropertyChangeListener) at java.lang.Class.getMethod(Class.java:1786) at org.eclipse.core.internal.databinding.beans.BeanPropertyListenerSupport.processListener(BeanPropertyListenerSupport.java:95) at org.eclipse.core.internal.databinding.beans.BeanPropertyListenerSupport.hookListener(BeanPropertyListenerSupport.java:46) at org.eclipse.core.internal.databinding.beans.BeanPropertyListener.doAddTo(BeanPropertyListener.java:64) at org.eclipse.core.databinding.property.NativePropertyListener.addTo(NativePropertyListener.java:49) at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.lambda$2(SimplePropertyObservableList.java:94) at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:151) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45) at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:155) at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:173) at org.eclipse.core.internal.databinding.property.list.SimplePropertyObservableList.firstListenerAdded(SimplePropertyObservableList.java:89) at org.eclipse.core.databinding.observable.list.AbstractObservableList$PrivateChangeSupport.firstListenerAdded(AbstractObservableList.java:63) at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:72) at org.eclipse.core.databinding.observable.ChangeSupport.addListener(ChangeSupport.java:34) at org.eclipse.core.databinding.observable.list.AbstractObservableList.addListChangeListener(AbstractObservableList.java:118) at org.eclipse.core.databinding.observable.list.DecoratingObservableList.firstListenerAdded(DecoratingObservableList.java:86) at org.eclipse.core.databinding.observable.ChangeManager.addListener(ChangeManager.java:72) at org.eclipse.core.databinding.observable.list.DecoratingObservableList.addListChangeListener(DecoratingObservableList.java:60) at org.eclipse.core.internal.databinding.observable.masterdetail.DetailObservableList.updateInnerObservableList(DetailObservableList.java:131) at org.eclipse.core.internal.databinding.observable.masterdetail.DetailObservableList.<init>(DetailObservableList.java:85) at org.eclipse.core.databinding.observable.masterdetail.MasterDetailObservables.detailList(MasterDetailObservables.java:95) at org.eclipse.core.databinding.property.list.ListProperty.observeDetail(ListProperty.java:154) at org.eclipse.core.internal.databinding.beans.BeanListPropertyDecorator.observeDetail(BeanListPropertyDecorator.java:105) at org.jboss.tools.openshift.internal.ui.wizard.applicationexplorer.CreateComponentWizardPage.doCreateControls(CreateComponentWizardPage.java:114) at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:78) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:178) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:743) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:635) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1094) at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:243) at org.jboss.tools.openshift.internal.ui.handler.applicationexplorer.CreateComponentHandler.execute(CreateComponentHandler.java:59) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:283) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:318) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:252) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:173) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:488) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:438) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449) at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:475) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4105) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1037) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3922) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3524) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1160) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1049) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155) at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:658) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:557) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:154) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:150) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:657) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:594) at org.eclipse.equinox.launcher.Main.run(Main.java:1447) at org.eclipse.equinox.launcher.Main.main(Main.java:1420) {code} We should check the create service wizard as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27257) Find suitable testing framework for the UI/integration tests

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27257?page=com.atlassian.jira.plug... ] Zbyněk Červinka commented on JBIDE-27257: ----------------------------------------- h2. Update on this issue: here is a sheet with the comparison of the test frameworks: https://docs.google.com/spreadsheets/d/1eFVL_byY8djzFU2C8OVLk0iyX3MGRmDDI... > Find suitable testing framework for the UI/integration tests > ------------------------------------------------------------ > > Key: JBIDE-27257 > URL: https://issues.redhat.com/browse/JBIDE-27257 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Affects Versions: 4.16.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.16.0.AM1 > > > *Tasks to complete:* > * Compare options on the market, discuss the benefits and shortcomings > * Start a debate at qe-dept-list > *Test frameworks candidates:* > * Test GUI Framework - https://plugins.jetbrains.com/plugin/11114-test-gui-framework > * Jemmy - http://wiki.netbeans.org/Jemmy > * FEST - https://code.google.com/archive/p/fest/ > * Abbot - http://abbot.sourceforge.net/ > *Not suitable (but discussed) frameworks:* > * https://plugins.jetbrains.com/plugin/13267-qa-lithium > * https://plugins.jetbrains.com/plugin/13691-selenium-ui-automation-testing > * https://plugins.jetbrains.com/plugin/7676-selenium-plugin > * http://www.protractortest.org/#/ > * https://jasmine.github.io/ > * https://www.chaijs.com/ > * https://mochajs.org/ > * https://robotframework.org/ > * http://sikulix.com/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27287) Add reporting to odo experience

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27287?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27287: ------------------------------- Description: Add reporting to the odo based developer experience. The following info will be reported: * create component: component type, success/failure * create service: service template, success/failure * create storage: size, success/failure * create url: secure, success/failure * login: counter * logout: counter * push/watch: counter * debug: counter * link: counter was: Add reporting to the odo based developer experience. The following info will be reported: * create component: component type, success/failure * create service: service template, success/failure * create storage: size, success/failure * create url: secure, success/failure * login: counter * push/watch: counter * debug: counter * link: counter > Add reporting to odo experience > ------------------------------- > > Key: JBIDE-27287 > URL: https://issues.redhat.com/browse/JBIDE-27287 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.15.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.16.0.AM1 > > > Add reporting to the odo based developer experience. > The following info will be reported: > * create component: component type, success/failure > * create service: service template, success/failure > * create storage: size, success/failure > * create url: secure, success/failure > * login: counter > * logout: counter > * push/watch: counter > * debug: counter > * link: counter -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27066) Cannot login to OpenShift 4.4.0 cluster

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27066?page=com.atlassian.jira.plug... ] Jeff MAURY commented on JBIDE-27066: ------------------------------------ Not that simple as certain versions of JDK11 will be fixed > Cannot login to OpenShift 4.4.0 cluster > --------------------------------------- > > Key: JBIDE-27066 > URL: https://issues.redhat.com/browse/JBIDE-27066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.14.0.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Critical > Fix For: 4.16.x > > > I was not able to connect to openshift 4.4.0 cluster with openshift tooling(based on openshift restclient). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27257) Find suitable testing framework for the UI/integration tests

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27257?page=com.atlassian.jira.plug... ] Zbyněk Červinka edited comment on JBIDE-27257 at 6/4/20 9:34 AM: ----------------------------------------------------------------- [~jkopriva] ok, I am going to update that. On the other hand, there are not going to be a lot of details in the document, the list of benefits and shortcomings will be short. In the end we will decide between 2 usable frameworks I guess. was (Author: zcervink): [~jkopriva] ok, I am going to update that. On the other hand, there are not going to be a lot of details in the document, the list of benefits and shortcomings will be short. In the end we will decide between 2 usable frameworks. > Find suitable testing framework for the UI/integration tests > ------------------------------------------------------------ > > Key: JBIDE-27257 > URL: https://issues.redhat.com/browse/JBIDE-27257 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Affects Versions: 4.16.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.16.0.AM1 > > > *Tasks to complete:* > * Compare options on the market, discuss the benefits and shortcomings > * Start a debate at qe-dept-list > *Test frameworks candidates:* > * Test GUI Framework - https://plugins.jetbrains.com/plugin/11114-test-gui-framework > * Jemmy - http://wiki.netbeans.org/Jemmy > * FEST - https://code.google.com/archive/p/fest/ > * Abbot - http://abbot.sourceforge.net/ > *Not suitable (but discussed) frameworks:* > * https://plugins.jetbrains.com/plugin/13267-qa-lithium > * https://plugins.jetbrains.com/plugin/13691-selenium-ui-automation-testing > * https://plugins.jetbrains.com/plugin/7676-selenium-plugin > * http://www.protractortest.org/#/ > * https://jasmine.github.io/ > * https://www.chaijs.com/ > * https://mochajs.org/ > * https://robotframework.org/ > * http://sikulix.com/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27257) Find suitable testing framework for the UI/integration tests

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27257?page=com.atlassian.jira.plug... ] Zbyněk Červinka edited comment on JBIDE-27257 at 6/4/20 9:34 AM: ----------------------------------------------------------------- [~jkopriva] ok, I am going to update that. On the other hand, there are not going to be a lot of details in the document, the list of benefits and shortcomings will be short. In the end we will decide between 2 usable frameworks. was (Author: zcervink): [~jkopriva] ok, I am going to update that. On the other hand, there are not going to be a lot of details, the list of benefits and shortcomings will be short. In the end we will decide between 2 usable frameworks. > Find suitable testing framework for the UI/integration tests > ------------------------------------------------------------ > > Key: JBIDE-27257 > URL: https://issues.redhat.com/browse/JBIDE-27257 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Affects Versions: 4.16.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.16.0.AM1 > > > *Tasks to complete:* > * Compare options on the market, discuss the benefits and shortcomings > * Start a debate at qe-dept-list > *Test frameworks candidates:* > * Test GUI Framework - https://plugins.jetbrains.com/plugin/11114-test-gui-framework > * Jemmy - http://wiki.netbeans.org/Jemmy > * FEST - https://code.google.com/archive/p/fest/ > * Abbot - http://abbot.sourceforge.net/ > *Not suitable (but discussed) frameworks:* > * https://plugins.jetbrains.com/plugin/13267-qa-lithium > * https://plugins.jetbrains.com/plugin/13691-selenium-ui-automation-testing > * https://plugins.jetbrains.com/plugin/7676-selenium-plugin > * http://www.protractortest.org/#/ > * https://jasmine.github.io/ > * https://www.chaijs.com/ > * https://mochajs.org/ > * https://robotframework.org/ > * http://sikulix.com/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27257) Find suitable testing framework for the UI/integration tests

by Zbyněk Červinka (Jira)

[ https://issues.redhat.com/browse/JBIDE-27257?page=com.atlassian.jira.plug... ] Zbyněk Červinka commented on JBIDE-27257: ----------------------------------------- [~jkopriva] ok, I am going to update that. On the other hand, there are not going to be a lot of details, the list of benefits and shortcomings will be short. In the end we will decide between 2 usable frameworks. > Find suitable testing framework for the UI/integration tests > ------------------------------------------------------------ > > Key: JBIDE-27257 > URL: https://issues.redhat.com/browse/JBIDE-27257 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Affects Versions: 4.16.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.16.0.AM1 > > > *Tasks to complete:* > * Compare options on the market, discuss the benefits and shortcomings > * Start a debate at qe-dept-list > *Test frameworks candidates:* > * Test GUI Framework - https://plugins.jetbrains.com/plugin/11114-test-gui-framework > * Jemmy - http://wiki.netbeans.org/Jemmy > * FEST - https://code.google.com/archive/p/fest/ > * Abbot - http://abbot.sourceforge.net/ > *Not suitable (but discussed) frameworks:* > * https://plugins.jetbrains.com/plugin/13267-qa-lithium > * https://plugins.jetbrains.com/plugin/13691-selenium-ui-automation-testing > * https://plugins.jetbrains.com/plugin/7676-selenium-plugin > * http://www.protractortest.org/#/ > * https://jasmine.github.io/ > * https://www.chaijs.com/ > * https://mochajs.org/ > * https://robotframework.org/ > * http://sikulix.com/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27257) Find suitable testing framework for the UI/integration tests

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27257?page=com.atlassian.jira.plug... ] Josef Kopriva commented on JBIDE-27257: --------------------------------------- [~zcervink] I would say Google Sheet would be more suitable format for comparison of test frameworks. > Find suitable testing framework for the UI/integration tests > ------------------------------------------------------------ > > Key: JBIDE-27257 > URL: https://issues.redhat.com/browse/JBIDE-27257 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: qa > Affects Versions: 4.16.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.16.0.AM1 > > > *Tasks to complete:* > * Compare options on the market, discuss the benefits and shortcomings > * Start a debate at qe-dept-list > *Test frameworks candidates:* > * Test GUI Framework - https://plugins.jetbrains.com/plugin/11114-test-gui-framework > * Jemmy - http://wiki.netbeans.org/Jemmy > * FEST - https://code.google.com/archive/p/fest/ > * Abbot - http://abbot.sourceforge.net/ > *Not suitable (but discussed) frameworks:* > * https://plugins.jetbrains.com/plugin/13267-qa-lithium > * https://plugins.jetbrains.com/plugin/13691-selenium-ui-automation-testing > * https://plugins.jetbrains.com/plugin/7676-selenium-plugin > * http://www.protractortest.org/#/ > * https://jasmine.github.io/ > * https://www.chaijs.com/ > * https://mochajs.org/ > * https://robotframework.org/ > * http://sikulix.com/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26959) Prepare CRS Ansible-Tower instance

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-26959?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-26959. --------------------------------- Resolution: Done Closing, Ansible instance is running and jobs are working. Improvements will be tracked in separate JIRAs. > Prepare CRS Ansible-Tower instance > ---------------------------------- > > Key: JBIDE-26959 > URL: https://issues.redhat.com/browse/JBIDE-26959 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: integration-tests, qa > Affects Versions: 4.14.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Major > Fix For: 4.16.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27219) Prepare job for Windows

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-27219?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-27219. --------------------------------- Resolution: Done > Prepare job for Windows > ----------------------- > > Key: JBIDE-27219 > URL: https://issues.redhat.com/browse/JBIDE-27219 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.16.0.AM1 > Reporter: Josef Kopriva > Assignee: Jan Richter > Priority: Major > Fix For: 4.16.0.AM1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 June 2020