[JBoss JIRA] (JBIDE-19934) NPE when opening a HTML file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19934?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-19934:
--------------------------------------
Assignee: Daniel Azarov
> NPE when opening a HTML file
> ----------------------------
>
> Key: JBIDE-19934
> URL: https://issues.jboss.org/browse/JBIDE-19934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Reporter: Gorkem Ercan
> Assignee: Daniel Azarov
> Fix For: 4.3.0.Beta2
>
>
> Got the following NPE when opening a view on an angular/hybrid mobile project. I do not think it is related to angular though.
> eclipse.buildId=unknown
> java.version=1.8.0_25
> java.vendor=Oracle Corporation
> org.eclipse.ui.workbench
> Error
> Thu Jun 04 11:10:36 EDT 2015
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> java.lang.NullPointerException
> at org.jboss.tools.jst.web.ui.palette.internal.html.impl.PaletteModelImpl.getPreferredExpandedCategory(PaletteModelImpl.java:214)
> at org.jboss.tools.jst.web.ui.palette.model.PaletteModel$PL.partActivated(PaletteModel.java:140)
> at org.eclipse.ui.internal.PartService$1.run(PartService.java:84)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.PartService.partActivated(PartService.java:81)
> at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3056)
> at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.java:4813)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4810)
> at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4798)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:242)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:239)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:702)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:630)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:625)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3195)
> at org.eclipse.ui.internal.WorkbenchPage.access$24(WorkbenchPage.java:3102)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3084)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3079)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3043)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3033)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:541)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:500)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:360)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:167)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:268)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:233)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251)
> at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:50)
> at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:229)
> at org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:854)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:851)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1168)
> at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:449)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1275)
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278)
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> 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: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: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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19934) NPE when opening a HTML file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19934?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19934:
-----------------------------------
Priority: Critical (was: Major)
> NPE when opening a HTML file
> ----------------------------
>
> Key: JBIDE-19934
> URL: https://issues.jboss.org/browse/JBIDE-19934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Reporter: Gorkem Ercan
> Assignee: Daniel Azarov
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> Got the following NPE when opening a view on an angular/hybrid mobile project. I do not think it is related to angular though.
> eclipse.buildId=unknown
> java.version=1.8.0_25
> java.vendor=Oracle Corporation
> org.eclipse.ui.workbench
> Error
> Thu Jun 04 11:10:36 EDT 2015
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> java.lang.NullPointerException
> at org.jboss.tools.jst.web.ui.palette.internal.html.impl.PaletteModelImpl.getPreferredExpandedCategory(PaletteModelImpl.java:214)
> at org.jboss.tools.jst.web.ui.palette.model.PaletteModel$PL.partActivated(PaletteModel.java:140)
> at org.eclipse.ui.internal.PartService$1.run(PartService.java:84)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.PartService.partActivated(PartService.java:81)
> at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3056)
> at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.java:4813)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4810)
> at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4798)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:242)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:239)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:702)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:630)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:625)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3195)
> at org.eclipse.ui.internal.WorkbenchPage.access$24(WorkbenchPage.java:3102)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3084)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3079)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3043)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3033)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:541)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:500)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:360)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:167)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:268)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:233)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251)
> at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:50)
> at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:229)
> at org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:854)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:851)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1168)
> at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:449)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1275)
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278)
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> 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: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: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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19934) NPE when opening a HTML file
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19934?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19934:
-----------------------------------
Fix Version/s: 4.3.0.Beta2
> NPE when opening a HTML file
> ----------------------------
>
> Key: JBIDE-19934
> URL: https://issues.jboss.org/browse/JBIDE-19934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Reporter: Gorkem Ercan
> Fix For: 4.3.0.Beta2
>
>
> Got the following NPE when opening a view on an angular/hybrid mobile project. I do not think it is related to angular though.
> eclipse.buildId=unknown
> java.version=1.8.0_25
> java.vendor=Oracle Corporation
> org.eclipse.ui.workbench
> Error
> Thu Jun 04 11:10:36 EDT 2015
> Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
> java.lang.NullPointerException
> at org.jboss.tools.jst.web.ui.palette.internal.html.impl.PaletteModelImpl.getPreferredExpandedCategory(PaletteModelImpl.java:214)
> at org.jboss.tools.jst.web.ui.palette.model.PaletteModel$PL.partActivated(PaletteModel.java:140)
> at org.eclipse.ui.internal.PartService$1.run(PartService.java:84)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.PartService.partActivated(PartService.java:81)
> at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3056)
> at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.java:4813)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4810)
> at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4798)
> at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:242)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:239)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:702)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:630)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:625)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3195)
> at org.eclipse.ui.internal.WorkbenchPage.access$24(WorkbenchPage.java:3102)
> at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3084)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3079)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3043)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3033)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:541)
> at org.eclipse.ui.ide.IDE.openEditor(IDE.java:500)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:360)
> at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:167)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:268)
> at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:233)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275)
> at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251)
> at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:50)
> at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:229)
> at org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:854)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:851)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1168)
> at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:449)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1275)
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278)
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
> 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: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: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:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19933:
------------------------------------
There are two workarounds:
a) perform a branch operation as documented here: https://issues.jboss.org/browse/JBIDE-19912, including updating your root pom AFTER the branch (in master) to use the Beta2 parent pom.
b) build locally using `-Djbosstools_site_stream=master` to build against upstream master bits [1] instead of the not-yet-built Beta2 ones in the 4.3.mars folder [2].
[1] http://download.jboss.org/jbosstools/builds/nightly/core/master/
[2] http://download.jboss.org/jbosstools/builds/nightly/core/4.3.mars/ (today, contains Alpha2 bits; by Friday EOD will hopefully have Beta1 bits)
> Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-19933
> URL: https://issues.jboss.org/browse/JBIDE-19933
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
>
> When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master).
> Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch.
> It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point.
> For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19933:
-------------------------------
Description:
When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master).
Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch.
It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point.
For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time.
was:
When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master).
Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch.
It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point.
For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=mars until the Beta1x branch is built for the first time.
> Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-19933
> URL: https://issues.jboss.org/browse/JBIDE-19933
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
>
> When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master).
> Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch.
> It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point.
> For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19934) NPE when opening a HTML file
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBIDE-19934:
------------------------------------
Summary: NPE when opening a HTML file
Key: JBIDE-19934
URL: https://issues.jboss.org/browse/JBIDE-19934
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.3.0.Alpha2
Reporter: Gorkem Ercan
Got the following NPE when opening a view on an angular/hybrid mobile project. I do not think it is related to angular though.
eclipse.buildId=unknown
java.version=1.8.0_25
java.vendor=Oracle Corporation
org.eclipse.ui.workbench
Error
Thu Jun 04 11:10:36 EDT 2015
Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".
java.lang.NullPointerException
at org.jboss.tools.jst.web.ui.palette.internal.html.impl.PaletteModelImpl.getPreferredExpandedCategory(PaletteModelImpl.java:214)
at org.jboss.tools.jst.web.ui.palette.model.PaletteModel$PL.partActivated(PaletteModel.java:140)
at org.eclipse.ui.internal.PartService$1.run(PartService.java:84)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.PartService.partActivated(PartService.java:81)
at org.eclipse.ui.internal.WorkbenchWindow$WWinPartService.partActivated(WorkbenchWindow.java:3056)
at org.eclipse.ui.internal.WorkbenchPage$13.run(WorkbenchPage.java:4813)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4810)
at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4798)
at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:202)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:242)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:239)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:702)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:630)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:625)
at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3195)
at org.eclipse.ui.internal.WorkbenchPage.access$24(WorkbenchPage.java:3102)
at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:3084)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3079)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3043)
at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3033)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:541)
at org.eclipse.ui.ide.IDE.openEditor(IDE.java:500)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:360)
at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:167)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:268)
at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:233)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275)
at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251)
at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:50)
at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:229)
at org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191)
at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:854)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:851)
at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1168)
at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:449)
at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1275)
at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278)
at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4203)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4045)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3672)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993)
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: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: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:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19879) Add o.e.remote and o.e.launchbar to TP
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19879?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19879:
------------------------------------
FYI, there's new stuff on eclipse.org.
{code}
cd /home/data/httpd/download.eclipse.org
for d in launchbar remote; do
find tracecompass releases/staging releases/mars -mindepth 2 -maxdepth 5 -type f -name "org.eclipse.${d}.core_*.jar" -o -name "org.eclipse.${d}.ui_*.jar" | grep "201506" | sort | egrep "${d}|201506|core|ui"
echo ""
done
releases/staging/plugins/org.eclipse.launchbar.ui_1.0.0.201506011405.jar
tracecompass/master/rcp-repository/plugins/org.eclipse.remote.ui_2.0.0.201506031830.jar
{code}
We have that version of launchbar but we have remote from 2.0.0.201505271353, so 06/03 is definitely newer.
> Add o.e.remote and o.e.launchbar to TP
> --------------------------------------
>
> Key: JBIDE-19879
> URL: https://issues.jboss.org/browse/JBIDE-19879
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, target-platform
> Affects Versions: 4.3.0.Beta2
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> *Reason:* JBIDE-19711 - WTP servertools integration with CDT launchbar
> *Project page/sources:* ... Requires dependencies on CDT and Launchbar. Launchbar is in http://www.eclipse.org/cdt/ and o.e.remote is in http://www.eclipse.org/ptp/
> *Version:* - Required launchbar is 1.0.0 found in MASTER at their repository. There is no released version yet with the stable API required. Required o.e.remote version is 2.0.0 in MASTER at their repository. There is no released version yet with the stable API required.
> *License and owner:* ... Both are eclipse projects licensed under EPL
> *Original p2 repo:* I am unable to locate the original update sites / p2 repos. PTP does not seem to have an update site URL to the best of my searching (http://download.eclipse.org/tools/ptp/builds/9.0.0/ does not list an update site url, but does have a zip containing an update site). CDT does not list update sites for mars at https://eclipse.org/cdt/downloads.php
> *JBoss mirror:* - Not sure what's applicable here. http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... does have all plugins needed, but none are the API required, as we require the code from Master.
> *Include Sources: - It's always nice to include sources for devs who build tp locally with the fetch-sources flag ;)
> *Affected projects: - jbosstools-server
> *Include in JBDS:* - No, for now.
> *Type of dependency:* distribution
> *List of bundles added/removed:* - At this time, I expect to require org.eclipse.launchbar.core, org.eclipse.launchbar.ui, org.eclipse.remote.core, org.eclipse.remote.ui.
> Unfortunately I'm unable to test if this is sufficient, at the moment. There may be other plugins that are transient deps somehow that I'm not seeing since I don't have a TP to build against that works.
> If applicable:
> *non-p2 repository:* ???
> *non-p2 ids:* ???
> Suggested Patch for TP: - At this point, I have no suggested patch. I do not know how to add a dependency on nightly builds for these two blocks of code. Also, I'm a bit confused why http://download.jboss.org/jbosstools/updates/requirements/mars/2015050810... will list a plugin (for example org.eclipse.cdt.core.native_5.8.0.201505050312.jar) but the .target file references a feature group (?) which is not present in the requirements/mars folder, such as <unit id="org.eclipse.cdt.native.feature.group" version="8.7.0.201505050312"/>
> I'm also a bit confused where you're pulling the feature group name / id from, or its version, as the version of the feature group does not seem to match the version of the plugin. Furthermore, the mars repo mentioned above does not seem to include any file matching the string org.eclipse.cdt.native.feature.group
> So I'm not sure how you're converting a required plugin id to a feature group. The devdoc also provides no assistance in this matter.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
by Martin Malina (JIRA)
Martin Malina created JBIDE-19933:
-------------------------------------
Summary: Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
Key: JBIDE-19933
URL: https://issues.jboss.org/browse/JBIDE-19933
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: build
Affects Versions: 4.3.0.Beta1
Reporter: Martin Malina
When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master).
Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch.
It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point.
For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=mars until the Beta1x branch is built for the first time.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBDS-3345) Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBDS-3345?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on JBDS-3345:
-----------------------------------------------
Gomathi Anandan <ganandan(a)redhat.com> changed the Status of [bug 1215031|https://bugzilla.redhat.com/show_bug.cgi?id=1215031] from NEW to CLOSED
> Errors when starting FSW 6.0.0.GA from JBDS 8.0.2.GA with JDK 1.8
> -----------------------------------------------------------------
>
> Key: JBDS-3345
> URL: https://issues.jboss.org/browse/JBDS-3345
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: server
> Affects Versions: 8.0.2.GA
> Environment: Fedora 21 x86_64
> JBDS 8.0.2.GA with Oracle JDK 1.8.0_25 and Oracle JDK 1.7.0_71
> Reporter: Andrej Podhradsky
> Priority: Optional
> Fix For: 9.0.0.Beta1
>
> Attachments: compiler.png, console.png, errors.txt, error_log.txt, installed_jre.png, run.sh, runtime_jre.png, server.log
>
>
> FSW 6.0.0.GA supports java 6 and 7, so if we want to run this server on JBDS 8 with jdk 8 we need to add another jdk to the JBDS, e.g. jdk 7. But this doesn't work, see errors in the attached file.
> Moreover, we are not able to stop the server from IDE, the process is still alive and we have to kill it manually.
> Note that this happens only when we install JBDS 8.0.2 with jdk 8, if we install it with jdk 7 the server works fine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months