[JBoss JIRA] (JBIDE-18572) NPE while calling a diff between 2 versions of a JS file
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18572?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18572:
------------------------------------------------
Please give me info about your OS and java version, maybe this issue is OS-specific.
> NPE while calling a diff between 2 versions of a JS file
> --------------------------------------------------------
>
> Key: JBIDE-18572
> URL: https://issues.jboss.org/browse/JBIDE-18572
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Priority: Critical
> Fix For: 4.3.0.Alpha1
>
>
> Not sure if the error is related {{summarry}}, but here's the stacktrace:
> I did compare my current JS file with the first version in my history, which was an empty file, then I called the diff with the next version and I got this error. I kept having this error when comparing the current version with any other version of the file (if that can help to reproduce/identify the problem)
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:572)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.access$0(VpvEditor.java:551)
> at org.jboss.tools.vpe.preview.editor.VpvEditor$EditorListener.partInputChanged(VpvEditor.java:674)
> at org.eclipse.ui.internal.WorkbenchPage$28.run(WorkbenchPage.java:5151)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartInputChanged(WorkbenchPage.java:5148)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$4.propertyChanged(CompatibilityPart.java:369)
> at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:132)
> at org.eclipse.compare.internal.CompareEditor.doSetInput(CompareEditor.java:313)
> at org.eclipse.compare.internal.CompareEditor.setInput(CompareEditor.java:254)
> at org.eclipse.compare.internal.CompareUIPlugin$1.run(CompareUIPlugin.java:546)
> at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1413)
> at org.eclipse.compare.internal.CompareUIPlugin.internalOpenEditor(CompareUIPlugin.java:567)
> at org.eclipse.compare.internal.CompareUIPlugin.openEditorInBackground(CompareUIPlugin.java:537)
> at org.eclipse.compare.internal.CompareUIPlugin.openCompareEditor(CompareUIPlugin.java:526)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:199)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:180)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.openInCompare(CompareRevisionAction.java:139)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.run(CompareRevisionAction.java:102)
> at org.eclipse.team.internal.ui.history.LocalHistoryPage$9.open(LocalHistoryPage.java:414)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:853)
> 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:178)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:850)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1142)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1249)
> 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:4188)
> 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:4031)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:484)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18572) NPE while calling a diff between 2 versions of a JS file
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18572?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-18572:
-------------------------------------------
Fix Version/s: 4.3.0.Alpha1
> NPE while calling a diff between 2 versions of a JS file
> --------------------------------------------------------
>
> Key: JBIDE-18572
> URL: https://issues.jboss.org/browse/JBIDE-18572
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Priority: Critical
> Fix For: 4.3.0.Alpha1
>
>
> Not sure if the error is related {{summarry}}, but here's the stacktrace:
> I did compare my current JS file with the first version in my history, which was an empty file, then I called the diff with the next version and I got this error. I kept having this error when comparing the current version with any other version of the file (if that can help to reproduce/identify the problem)
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:572)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.access$0(VpvEditor.java:551)
> at org.jboss.tools.vpe.preview.editor.VpvEditor$EditorListener.partInputChanged(VpvEditor.java:674)
> at org.eclipse.ui.internal.WorkbenchPage$28.run(WorkbenchPage.java:5151)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartInputChanged(WorkbenchPage.java:5148)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$4.propertyChanged(CompatibilityPart.java:369)
> at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:132)
> at org.eclipse.compare.internal.CompareEditor.doSetInput(CompareEditor.java:313)
> at org.eclipse.compare.internal.CompareEditor.setInput(CompareEditor.java:254)
> at org.eclipse.compare.internal.CompareUIPlugin$1.run(CompareUIPlugin.java:546)
> at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1413)
> at org.eclipse.compare.internal.CompareUIPlugin.internalOpenEditor(CompareUIPlugin.java:567)
> at org.eclipse.compare.internal.CompareUIPlugin.openEditorInBackground(CompareUIPlugin.java:537)
> at org.eclipse.compare.internal.CompareUIPlugin.openCompareEditor(CompareUIPlugin.java:526)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:199)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:180)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.openInCompare(CompareRevisionAction.java:139)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.run(CompareRevisionAction.java:102)
> at org.eclipse.team.internal.ui.history.LocalHistoryPage$9.open(LocalHistoryPage.java:414)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:853)
> 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:178)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:850)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1142)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1249)
> 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:4188)
> 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:4031)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:484)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18696:
------------------------------------------
So the only time you have the quickstarts listed is when you restart Eclipse and try to create an application? In every following attempt you dont have them listed?
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-18696 at 10/24/14 6:15 AM:
--------------------------------------------------------------------
I see you creating a new domain in the first log. So this only happens when you launch the application wizard but dont have a domain yet? Is the Quickstarts cathegory also empty when you try to create an aplication while you already have a domain?
This is rather super-weird, I'm very much puzzled. I tried it here in a freshly started Eclipse/fresh JBDS8 (no caching could have happen) using openshift online account where I had no domain. I was prompted to create a domain and had the Quickstarts listed as expected.
Can you replicate this in OpenShift Online?
Can you replicate this in a different OS (ex. Linux, Mac)?
was (Author: adietish):
I see you creating a new domain in the first log. So this only happens when you launch the application wizard but dont have a domain yet? Is the Quickstarts cathegory also empty when you try to create an aplication while you already have a domain?
This is rather super-weird, I'm very much puzzled. I tried it here in a freshly started Eclipse (no caching could have happen) using openshift online account where I had no domain. I was prompted to create a domain and had the Quickstarts listed as expected.
Can you replicate this in OpenShift Online?
Can you replicate this in a different OS (ex. Linux, Mac)?
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-18696 at 10/24/14 6:15 AM:
--------------------------------------------------------------------
I see you creating a new domain in the first log. So this only happens when you launch the application wizard but dont have a domain yet? Is the Quickstarts cathegory also empty when you try to create an aplication while you already have a domain?
This is rather super-weird, I'm very much puzzled. I tried it here in a freshly started Eclipse (no caching could have happen) using openshift online account where I had no domain. I was prompted to create a domain and had the Quickstarts listed as expected.
Can you replicate this in OpenShift Online?
Can you replicate this in a different OS (ex. Linux, Mac)?
was (Author: adietish):
I see you creating a new domain in the first log. So this only happens when you launch the application wizard but dont have a domain yet? Is the Quickstarts cathegory also empty when you try to create an aplication while you already have a domain?
This is rather super-weird, I'm very much puzzled. I tried it here in a freshly started Eclipse (no caching could have happen) using openshift online account where I had no domain. I was prompted to create a domain and had the Quickstarts listed as expected.
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18696:
-------------------------------------
Steps to Reproduce:
1. ASSERT: make sure you're using JBoss Tools 4.2.0.Final
2. EXEC: Open OpenShift New Application Wizard: File -> New -> Other... -> OpenShift Application
3. EXEC: Provide your access credentials
4. EXEC: Click the "Quickstarts" cathegory
Result:
there are no quickstarts listed.
was:
1. ASSERT: make sure you're using JBoss Tools 4.2.0.Final
2. EXEC: Open OpenShift New Application Wizard: File -> New -> Other... -> OpenShift Application
3. EXEC: Provide your access credentials
4. EXEC: Click the "Quickstarts" labal
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-18696 at 10/24/14 6:11 AM:
--------------------------------------------------------------------
I see you creating a new domain in the first log. So this only happens when you launch the application wizard but dont have a domain yet? Is the Quickstarts cathegory also empty when you try to create an aplication while you already have a domain?
This is rather super-weird, I'm very much puzzled. I tried it here in a freshly started Eclipse (no caching could have happen) using openshift online account where I had no domain. I was prompted to create a domain and had the Quickstarts listed as expected.
was (Author: adietish):
I see you creating a new domain in the first log. So this only happens when you launch the application wizard but dont have a domain yet? Is the Quickstarts cathegory also empty when you try to create an aplication while you already have a domain?
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months