[JBoss JIRA] (JBIDE-22549) "Result" dialog enhancements
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-22549:
-------------------------------------
Summary: "Result" dialog enhancements
Key: JBIDE-22549
URL: https://issues.jboss.org/browse/JBIDE-22549
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: jmx
Affects Versions: 4.4.0.Final
Reporter: Xavier Coulon
Attachments: Screenshot 2016-06-07 11.35.28.png
When executing a JMX remote operation, the "Result" dialog displays a single column that cannot be expanded, and the row content cannot be copied into the clipboard.
See the attached screenshot for visual explanations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22513) [launchbar] NPE when null target
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22513?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22513:
---------------------------------------
[~rob.stryker], was there ever a way to reproduce this? Is there some scenario where the target would really be null and the NPE thrown?
If target is the Launch Target in the UI, then it's Local by default and there is no way to unset this AFAICS.
> [launchbar] NPE when null target
> --------------------------------
>
> Key: JBIDE-22513
> URL: https://issues.jboss.org/browse/JBIDE-22513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Alpha2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.0.Final
>
>
> Stacktrace is as follows
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.getLaunchConfiguration(ModuleLaunchConfigurationProvider.java:76)
> at org.jboss.tools.wtp.server.launchbar.ModuleLaunchConfigurationProvider.launchDescriptorMatches(ModuleLaunchConfigurationProvider.java:128)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.launchDescriptorMatches(LaunchBarManager.java:964)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.getLaunchDescriptor(LaunchBarManager.java:942)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.setActive(LaunchBarManager.java:424)
> at org.eclipse.launchbar.core.internal.LaunchBarManager.access$0(LaunchBarManager.java:423)
> at org.eclipse.launchbar.core.internal.LaunchBarManager$2.launchAdded(LaunchBarManager.java:169)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.run(LaunchManager.java:446)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.debug.internal.core.LaunchManager$LaunchNotifier.notify(LaunchManager.java:433)
> at org.eclipse.debug.internal.core.LaunchManager.fireUpdate(LaunchManager.java:1043)
> at org.eclipse.debug.internal.core.LaunchManager.addLaunch(LaunchManager.java:703)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:834)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:329)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$4(OpenShiftLaunchController.java:301)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:167)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugUtils.enableDebugMode(OpenShiftDebugUtils.java:88)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startDebugging(OpenShiftLaunchController.java:181)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.toggleDebugging(OpenShiftLaunchController.java:104)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:91)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22431) Rename CDK Server Adapter and other CDK ui enities
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22431?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22431.
---------------------------------
I created a follow up JIRA here: JBIDE-22548
Closing this one.
> 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.Final
>
>
> 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, 10 months
[JBoss JIRA] (JBIDE-22548) Fix remaining CDK names inconsistencies
by Martin Malina (JIRA)
Martin Malina created JBIDE-22548:
-------------------------------------
Summary: Fix remaining CDK names inconsistencies
Key: JBIDE-22548
URL: https://issues.jboss.org/browse/JBIDE-22548
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.0.Final
Reporter: Martin Malina
Assignee: Rob Stryker
This is a follow up of JBIDE-22431 . There are some remaining things to be fixed.
1. Alexey asked for the server adapter to be renamed to "Red Hat Container Development Kit" but it's now "Red Hat Container Development Kit Support". While it makes sense to have "Support" in the feature/plugin name, I don't think it makes sense for the server adapter type or the server name once it's created. So please drop the Support.
2. Runtime detection now uses the name of "Container Development Environment". This is inconsistent with creating the server adapter manually. Some time ago we tried to unify this - EAP now has the same names both when created via runtime detection or manually (default name). So if we really want to use the CDE thing (which I'm not a fan of, but whatever), I suggest we use this as the default name when creating a CDK adapter manually. But the adapter type should probably still be "Red Hat Container Development Kit" (no Support)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-244) NullPointerException in ContainerDataVolumeDialog.setOkButtonEnabled [EBZ#495517]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-244?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon resolved ERT-244.
-------------------------------
Resolution: Done
> NullPointerException in ContainerDataVolumeDialog.setOkButtonEnabled [EBZ#495517]
> ---------------------------------------------------------------------------------
>
> Key: ERT-244
> URL: https://issues.jboss.org/browse/ERT-244
> Project: Eclipse Release Train
> Issue Type: Bug
> Components: Linux Tools
> Affects Versions: Neon (4.6)
> Reporter: Friendly Jira Robot
> Assignee: Xavier Coulon
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.databinding.observable".
> java.lang.NullPointerException: null
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog.setOkButtonEnabled(ContainerDataVolumeDialog.java:483)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog.access$2(ContainerDataVolumeDialog.java:482)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog$7$1.run(ContainerDataVolumeDialog.java:438)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4761)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog$7.handleChange(ContainerDataVolumeDialog.java:413)
> at org.eclipse.core.databinding.observable.ChangeEvent.dispatch(ChangeEvent.java:42)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.AbstractObservable.fireChange(AbstractObservable.java:71)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:56)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65)
> at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65)
> at org.eclipse.core.internal.databinding.beans.BeanPropertyListener.propertyChange(BeanPropertyListener.java:50)
> at java.beans.PropertyChangeSupport.fire(null:-1)
> at java.beans.PropertyChangeSupport.firePropertyChange(null:-1)
> at java.beans.PropertyChangeSupport.firePropertyChange(null:-1)
> at org.eclipse.linuxtools.internal.docker.ui.databinding.BaseDatabindingModel.firePropertyChange(BaseDatabindingModel.java:42)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.DataVolumeModel.setMountType(DataVolumeModel.java:208)
> at org.eclipse.linuxtools.internal.docker.ui.launch.RunImageVolumesTab$4.widgetSelected(RunImageVolumesTab.java:294)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> Bundles:
> | org.eclipse.core.databinding.beans | 1.3.0.v20150422-0725 | 1.3.0.v20150422-0725 |
> | org.eclipse.core.databinding.observable | 1.5.0.v20150422-0725 | 1.5.0.v20150422-0725 |
> | org.eclipse.core.databinding.property | 1.5.0.v20150422-0725 | 1.5.0.v20150422-0725 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.linuxtools.docker.ui | 1.2.0.201512112123 | 1.2.0.201512112123 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/574ee... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (ERT-244) NullPointerException in ContainerDataVolumeDialog.setOkButtonEnabled [EBZ#495517]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/ERT-244?page=com.atlassian.jira.plugin.sy... ]
Xavier Coulon updated ERT-244:
------------------------------
Sprint: devex #115 May 2016
> NullPointerException in ContainerDataVolumeDialog.setOkButtonEnabled [EBZ#495517]
> ---------------------------------------------------------------------------------
>
> Key: ERT-244
> URL: https://issues.jboss.org/browse/ERT-244
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Affects Versions: Neon (4.6)
> Reporter: Friendly Jira Robot
> Labels: 5.0.0, Docker, bzira
> Fix For: Neon (4.6)
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.databinding.observable".
> java.lang.NullPointerException: null
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog.setOkButtonEnabled(ContainerDataVolumeDialog.java:483)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog.access$2(ContainerDataVolumeDialog.java:482)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog$7$1.run(ContainerDataVolumeDialog.java:438)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4761)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ContainerDataVolumeDialog$7.handleChange(ContainerDataVolumeDialog.java:413)
> at org.eclipse.core.databinding.observable.ChangeEvent.dispatch(ChangeEvent.java:42)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.AbstractObservable.fireChange(AbstractObservable.java:71)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:56)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65)
> at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65)
> at org.eclipse.core.internal.databinding.beans.BeanPropertyListener.propertyChange(BeanPropertyListener.java:50)
> at java.beans.PropertyChangeSupport.fire(null:-1)
> at java.beans.PropertyChangeSupport.firePropertyChange(null:-1)
> at java.beans.PropertyChangeSupport.firePropertyChange(null:-1)
> at org.eclipse.linuxtools.internal.docker.ui.databinding.BaseDatabindingModel.firePropertyChange(BaseDatabindingModel.java:42)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.DataVolumeModel.setMountType(DataVolumeModel.java:208)
> at org.eclipse.linuxtools.internal.docker.ui.launch.RunImageVolumesTab$4.widgetSelected(RunImageVolumesTab.java:294)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> Bundles:
> | org.eclipse.core.databinding.beans | 1.3.0.v20150422-0725 | 1.3.0.v20150422-0725 |
> | org.eclipse.core.databinding.observable | 1.5.0.v20150422-0725 | 1.5.0.v20150422-0725 |
> | org.eclipse.core.databinding.property | 1.5.0.v20150422-0725 | 1.5.0.v20150422-0725 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.11.1.v20150903-1804 |
> | org.eclipse.linuxtools.docker.ui | 1.2.0.201512112123 | 1.2.0.201512112123 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.104.2.v20160212-1350 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.107.0.v20150507-1945 |
> Operating Systems:
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit https://dev.eclipse.org/recommenders/committers/aeri/v2/#!/problems/574ee... for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months