Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359605 - Navigator label not updated when Progressing the state of an anomaly
Summary: Navigator label not updated when Progressing the state of an anomaly
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: 0.9   Edit
Assignee: Sebastien Dubois CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-30 15:21 EDT by Alvaro Sanchez-Leon CLA
Modified: 2012-01-24 15:35 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alvaro Sanchez-Leon CLA 2011-09-30 15:21:07 EDT 
When using the progress element arrow in the tool bar, it is very visible that the state of the anomaly is not refreshed in the Navigator.
Howver the properties reflect the correct value.

work around is to reload the review.
Comment 1 Sebastien Dubois CLA 2011-09-30 16:23:46 EDT 
Also an exception is generated when using the progress/regress arrows on either anomaly or review.

java.lang.NullPointerException
	at org.eclipse.ui.views.properties.tabbed.TabbedPropertySheetPage.refresh(TabbedPropertySheetPage.java:749)
	at org.eclipse.mylyn.reviews.r4e.ui.internal.commands.PreviousStateHandler$1.runInUIThread(PreviousStateHandler.java:102)
	at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
Comment 2 Sebastien Dubois CLA 2011-09-30 17:22:11 EDT 
Opened a new bug 359624, as this is a separate issue.
Comment 3 Sebastien Dubois CLA 2011-10-04 10:03:29 EDT 
Fixed with bug 359624
Comment 4 Sebastien Dubois CLA 2011-10-04 10:09:44 EDT 
Fixed with bug 359624
Comment 5 Sebastien Dubois CLA 2011-10-04 12:17:42 EDT 
Fixed with bug 359624