[JBoss JIRA] (JBIDE-22445) Server adapter wizard: NPE when finishing
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22445?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich reassigned JBIDE-22445:
---------------------------------------------
Assignee: Viacheslav Kabanovich
> Server adapter wizard: NPE when finishing
> ------------------------------------------
>
> Key: JBIDE-22445
> URL: https://issues.jboss.org/browse/JBIDE-22445
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Radim Hopp
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: openshift_v3, server_adapter_wizard
> Fix For: 4.4.0.Alpha3
>
>
> I'm getting NPE when finishing New Server Wizard of Openshift 3 server adapter.
> mlabuda was also able to reproduce this bug.
> {noformat}
> java.lang.NullPointerException
> at org.eclipse.wst.server.ui.internal.wizard.TaskWizardPage.update(TaskWizardPage.java:126)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$ServerSettingsWizardPageWrapper.setPageComplete(ServerSettingsWizardFragment.java:200)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage.setComplete(ServerSettingsWizardPage.java:189)
> at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardPage$1.setComplete(ServerSettingsWizardPage.java:207)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.handleComplete(FormPresenterSupport.java:243)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.handleStatusChanged(FormPresenterSupport.java:232)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.statusProviderChanged(FormPresenterSupport.java:200)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport.access$2(FormPresenterSupport.java:190)
> at org.jboss.tools.openshift.internal.common.ui.databinding.FormPresenterSupport$4.handleValueChange(FormPresenterSupport.java:158)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:70)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:82)
> at org.eclipse.core.databinding.observable.value.ComputedValue.makeDirty(ComputedValue.java:240)
> at org.eclipse.core.databinding.observable.value.ComputedValue$PrivateInterface.handleChange(ComputedValue.java:183)
> at org.eclipse.core.databinding.observable.ChangeEvent.dispatch(ChangeEvent.java:42)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:117)
> at org.eclipse.core.databinding.observable.AbstractObservable.fireChange(AbstractObservable.java:71)
> at org.eclipse.core.databinding.observable.list.ObservableList.fireListChange(ObservableList.java:81)
> at org.eclipse.core.databinding.observable.list.WritableList.remove(WritableList.java:235)
> at org.eclipse.core.databinding.DataBindingContext.removeValidationStatusProvider(DataBindingContext.java:489)
> at org.eclipse.core.databinding.DataBindingContext.removeBinding(DataBindingContext.java:476)
> at org.eclipse.core.databinding.Binding.dispose(Binding.java:135)
> at org.eclipse.core.databinding.ValueBinding.dispose(ValueBinding.java:269)
> at org.eclipse.core.databinding.DataBindingContext.dispose(DataBindingContext.java:367)
> at org.jboss.tools.openshift.internal.common.ui.utils.DataBindingUtils.dispose(DataBindingUtils.java:107)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$1.widgetDisposed(AbstractOpenShiftWizardPage.java:79)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:124)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1345)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1153)
> at org.eclipse.swt.widgets.Control.release(Control.java:3989)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:479)
> at org.eclipse.swt.widgets.Shell.dispose(Shell.java:2660)
> at org.eclipse.jface.window.Window.close(Window.java:330)
> at org.eclipse.jface.dialogs.Dialog.close(Dialog.java:989)
> at org.eclipse.jface.wizard.WizardDialog.hardClose(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:798)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:423)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.wst.server.ui.internal.actions.LaunchWizardAction.run(LaunchWizardAction.java:57)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22431) Rename CDK Server Adapter and other CDK ui enities
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22431?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22431:
-----------------------------------
Description:
We need to rename some UI stuff where CDK name is used in our tooling.
1. New->Server->CDK Server Adapter *should be renamed to* New->Server->Red Hat Container Development Kit
2. But the default name for server should be "Container Development Environment" instead of the current "CDK Server Adapter at local host".
3. If the server created by runtime detector when our windows installation completed (platform-installer) then the server should has the same "Container Development Environment" instead of the current "rhel-ose CDK Server". Please open an issue for [platform-installer|https://issues.jboss.org/browse/JBDS-3909?jql=project%...] if something should be changed in the files generated by our installer.
4. Runtime detector should be renamed from CDK to "Container Development Environment".
5. In org.jboss.tools.openshift.cdk.server/about.properties and feature and plugin names change "CDK Server Adapter" to "Container Development Kit Support"
was:
We need to rename some UI stuff where CDK name is used in our tooling.
1. New->Server->CDK Server Adapter *should be renamed to* New->Server->Red Hat Container Development Kit
2. But the default name for server should be "Container Development Environment" instead of the current "CDK Server Adapter at local host".
3. Runtime detector should be renamed from CDK to "Container Development Environment".
4. In org.jboss.tools.openshift.cdk.server/about.properties and feature and plugin names change "CDK Server Adapter" to "Container Development Kit Support"
> Rename CDK Server Adapter and other CDK ui enities
> --------------------------------------------------
>
> Key: JBIDE-22431
> URL: https://issues.jboss.org/browse/JBIDE-22431
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdk
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.0.Alpha3
>
>
> We need to rename some UI stuff where CDK name is used in our tooling.
> 1. New->Server->CDK Server Adapter *should be renamed to* New->Server->Red Hat Container Development Kit
> 2. But the default name for server should be "Container Development Environment" instead of the current "CDK Server Adapter at local host".
> 3. If the server created by runtime detector when our windows installation completed (platform-installer) then the server should has the same "Container Development Environment" instead of the current "rhel-ose CDK Server". Please open an issue for [platform-installer|https://issues.jboss.org/browse/JBDS-3909?jql=project%...] if something should be changed in the files generated by our installer.
> 4. Runtime detector should be renamed from CDK to "Container Development Environment".
> 5. In org.jboss.tools.openshift.cdk.server/about.properties and feature and plugin names change "CDK Server Adapter" to "Container Development Kit Support"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22413) Connection Editor: dont launch further jobs if editor is already closed
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22413?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22413:
-----------------------------------------------
[~adietish], please take a look at the pull request.
> Connection Editor: dont launch further jobs if editor is already closed
> -----------------------------------------------------------------------
>
> Key: JBIDE-22413
> URL: https://issues.jboss.org/browse/JBIDE-22413
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha3
>
>
> ASSERT: make sure that you have a server adapter
> EXEC: open it in the server editor
> ASSERT: the widgets in the openshift section are disabled, in the status bar (or progress view) you see a job "Loading projects..." running
> EXEC: close the editor
> ASSERT: nothing happens so far, but you see another job running "Setting connection, deploy..."
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22431) Rename CDK Server Adapter and other CDK ui enities
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22431?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22431:
-----------------------------------
Description:
We need to rename some UI stuff where CDK name is used in our tooling.
1. New->Server->CDK Server Adapter *should be renamed to* New->Server->Red Hat Container Development Kit
2. But the default name for server should be "Container Development Environment" instead of the current "CDK Server Adapter at local host".
3. Runtime detector should be renamed from CDK to "Container Development Environment".
4. In org.jboss.tools.openshift.cdk.server/about.properties and feature and plugin names change "CDK Server Adapter" to "Container Development Kit Support"
was:
We need to rename some UI stuff where CDK name is used in our tooling.
I will provide new names and the list of places where it should be changed later.
> Rename CDK Server Adapter and other CDK ui enities
> --------------------------------------------------
>
> Key: JBIDE-22431
> URL: https://issues.jboss.org/browse/JBIDE-22431
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdk
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.0.Alpha3
>
>
> We need to rename some UI stuff where CDK name is used in our tooling.
> 1. New->Server->CDK Server Adapter *should be renamed to* New->Server->Red Hat Container Development Kit
> 2. But the default name for server should be "Container Development Environment" instead of the current "CDK Server Adapter at local host".
> 3. Runtime detector should be renamed from CDK to "Container Development Environment".
> 4. In org.jboss.tools.openshift.cdk.server/about.properties and feature and plugin names change "CDK Server Adapter" to "Container Development Kit Support"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ]
Roland Grunberg commented on JBDS-3739:
---------------------------------------
I believe the issue with vagrant-service-manager is resolved. Stopping/starting the CDK VM any number of times doesn't fail any of the docker cli invocations. The last issue needing to be addressed on our end is that the CDK VM appears to update the certificates used or at least change something about them requiring us to re-create the connection. This is s something that will likely be addressed on the Eclipse Docker Tooling side as well. Xavier has a fix for this that we're reviewing.
> Docker connection does not work after cdk restart
> -------------------------------------------------
>
> Key: JBDS-3739
> URL: https://issues.jboss.org/browse/JBDS-3739
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: cdk, platform-installer, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Marián Labuda
> Priority: Blocker
> Labels: havoc
> Fix For: 10.0.0.Alpha3
>
> Attachments: docker-frozen.txt
>
>
> When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work.
> This is caused by a bug in vagrant-service-manager 0.0.4:
> https://github.com/projectatomic/vagrant-service-manager/issues/80
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months