[JBoss JIRA] (JBIDE-21483) Creating artifact for non-batch project results in NPE
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-21483:
----------------------------------------
Summary: Creating artifact for non-batch project results in NPE
Key: JBIDE-21483
URL: https://issues.jboss.org/browse/JBIDE-21483
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: batch
Affects Versions: 4.3.1.Beta1
Reporter: Rastislav Wagner
Assignee: Viacheslav Kabanovich
Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
{code}
java.lang.NullPointerException
at org.jboss.tools.batch.internal.core.impl.PreferredPackageManager.savePreferredPackage(PreferredPackageManager.java:95)
at org.jboss.tools.batch.ui.internal.wizard.NewBatchArtifactWizard.performFinish(NewBatchArtifactWizard.java:116)
at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
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:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
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:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21483) Creating artifact for non-batch project results in NPE
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21483?page=com.atlassian.jira.plugi... ]
Rastislav Wagner updated JBIDE-21483:
-------------------------------------
Fix Version/s: (was: 4.3.1.Beta2)
> Creating artifact for non-batch project results in NPE
> ------------------------------------------------------
>
> Key: JBIDE-21483
> URL: https://issues.jboss.org/browse/JBIDE-21483
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.1.Beta1
> Reporter: Rastislav Wagner
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha1
>
>
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.batch.internal.core.impl.PreferredPackageManager.savePreferredPackage(PreferredPackageManager.java:95)
> at org.jboss.tools.batch.ui.internal.wizard.NewBatchArtifactWizard.performFinish(NewBatchArtifactWizard.java:116)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:799)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:429)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:160)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21475) Use vagrant.bat to start vagrant
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21475?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21475:
-------------------------------------
When I tested it in windows, just 'vagrant' worked 100% as expected.
Are you opening bugs after experiencing an error, Denis? Or are you just opening bugs for things that look wrong? Just curious so I know whether this is actually erroring for you?
> Use vagrant.bat to start vagrant
> --------------------------------
>
> Key: JBIDE-21475
> URL: https://issues.jboss.org/browse/JBIDE-21475
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Environment: Windows
> Reporter: Denis Golovin
> Priority: Blocker
>
> CDK adapter uses %VRGANT_PATH%\bin\vagrant to start vagrant on windows, but vargant file is a shell script. vagrant.bat should be used instead.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21464) Explorer: Delete context menu of OpenShift elements is incorrect
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21464?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-21464.
-----------------------------------
Resolution: Rejected
Ok, you convinced me ;) if there is required further action with input/decision different then yes/no then there should be ellipsis. So Delete can and should be without ellipsis as you pointed. Resolving this one as rejected.
> Explorer: Delete context menu of OpenShift elements is incorrect
> ----------------------------------------------------------------
>
> Key: JBIDE-21464
> URL: https://issues.jboss.org/browse/JBIDE-21464
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v2, openshift_v3
> Fix For: 4.3.1.Beta2
>
>
> Currently OpenShift tree items in OpenShift Explorer view have "Delete" context menu item. Previously it was more natural, because we had "Delete connection(s)..." "Delete domain..." etc., not it is all "Delete".
> If just plain "Delete" is considered as a good way to go, at least there should be three dots as suffix, because after click on the context menu Delete there is required user confirmation of deletion. So it should be at least "Delete...".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21463) Port Forwarding: No error message pop up when attempt to port-forward to a port in use
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21463?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21463:
-------------------------------------
Summary: Port Forwarding: No error message pop up when attempt to port-forward to a port in use (was: No error message pop up when attempt to port-forward to a port in use)
> Port Forwarding: No error message pop up when attempt to port-forward to a port in use
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-21463
> URL: https://issues.jboss.org/browse/JBIDE-21463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
> OS: Fedora 17 & MAC OS 10
> Reporter: Xia Zhao
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.CR1
>
>
> No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21464) Explorer: Delete context menu of OpenShift elements is incorrect
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21464?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21464:
-------------------------------------
Summary: Explorer: Delete context menu of OpenShift elements is incorrect (was: Delete context menu of OpenShift elements is incorrect)
> Explorer: Delete context menu of OpenShift elements is incorrect
> ----------------------------------------------------------------
>
> Key: JBIDE-21464
> URL: https://issues.jboss.org/browse/JBIDE-21464
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: explorer, openshift_v2, openshift_v3
> Fix For: 4.3.1.Beta2
>
>
> Currently OpenShift tree items in OpenShift Explorer view have "Delete" context menu item. Previously it was more natural, because we had "Delete connection(s)..." "Delete domain..." etc., not it is all "Delete".
> If just plain "Delete" is considered as a good way to go, at least there should be three dots as suffix, because after click on the context menu Delete there is required user confirmation of deletion. So it should be at least "Delete...".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21463) No error message pop up when attempt to port-forward to a port in use
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21463?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21463:
-------------------------------------
Steps to Reproduce:
1. Prepare 2 applications which will deliver different HTML outputs on a same port 8080. Say pod1 in project1 will reurn string "I'm A" if you curl http://127.0.0.1/8080 after a successful port-forward operation, and pod2 in project2 will reutrn string "I'm B" if you curl http://127.0.0.1/8080 after a successful port-forward operation. (Let me know if you need the detailed application json files for these 2 projects)
2. Deploy these 2 applications sepereately into project1 and project2 of openshift
3. Login openshift with JBT (I used Jboss Developer Studio on Mac OS)
4. Inside JBT, go to project1, right click on pod1 (when this pod is running healty), port-forward it to local port 8080 --> This is used to make local 8080 port is now in use
5. curl http://127.0.0.1/8080, should return string "I'm A" in the result HTML file
6. If you go back to JBT, close the port-forward window in step #4, and revisit it , should still see from UI that port forwarding is in process
7. Now go to project2, right click on pod2 (when this pod is running healty), port-forward it to local port 8080 --> This should not be success since port 8080 is already in use, but no error message is popped up, and the Port Forward wizard pretended to be succeeded.
8. Close the port-forward window in step7, and revisit it for the 2nd time now, we can see from the UI that port forwarding is ended.
9. curl http://127.0.0.1/8080, still return string "I'm A" in the result HTML file, this means the port forward in step4 is still taking effect, and the attempt in step 6 had failed, this is the expected result here.
was:
Steps to Reproduce:
0. Install latest version of Jboss Developer Studio from https://devstudio.redhat.com/9.0/stable/updates/
1. Login openshift with Jboss Developer Studio, attempt to port-forward a pod to a port in use
Actual Result:
Application Port Forward wizard pretended to be succeeded until you visit it for the 2nd time, and no error message pop up when attempt to port-forward to a port in use
Expected Result:
Port forwarding should fail, but should pop up friendly error message when attempt to port-forward to a port in use
> No error message pop up when attempt to port-forward to a port in use
> ---------------------------------------------------------------------
>
> Key: JBIDE-21463
> URL: https://issues.jboss.org/browse/JBIDE-21463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
> OS: Fedora 17 & MAC OS 10
> Reporter: Xia Zhao
> Assignee: Andre Dietisheim
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.CR1
>
>
> No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months