Community
Participate
Working Groups
With build 2004-05-11, IBM J9SE VM (build 2.1, J2RE 1.4.1 IBM J9 build 20040121 (JIT enabled)) 1) I changed two files in the org.eclipse.search project. 2) Used team-synchronize from the package explorer (selection on the project). 3) Selected the folder the two changed files are in 4) Selected "commit" from the context menu. 5) observe: I get an exception: !ENTRY org.eclipse.ui 4 0 May 11, 2004 10:24:26.70 !MESSAGE java.lang.NullPointerException !STACK 0 java.lang.NullPointerException at java.lang.Throwable.<init>(Throwable.java) at java.lang.Throwable.<init>(Throwable.java) at java.lang.NullPointerException.<init>(NullPointerException.java:60) at org.eclipse.jface.resource.ImageRegistry.get(ImageRegistry.java) at org.eclipse.team.internal.ui.dialogs.DetailsDialog.createDialogArea(D etailsDialog.java:140) at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:631) at org.eclipse.jface.window.Window.create(Window.java:348) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:924) at org.eclipse.jface.window.Window.open(Window.java:637) at org.eclipse.team.internal.ccvs.ui.repo.RepositoryManager$2.run(Reposi toryManager.java:552) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:135) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java) at org.eclipse.swt.widgets.Display.syncExec(Display.java) at org.eclipse.team.internal.ccvs.ui.repo.RepositoryManager.promptForCom ment(RepositoryManager.java:550) at org.eclipse.team.internal.ccvs.ui.subscriber.WorkspaceCommitOperation .promptForComment(WorkspaceCommitOperation.java:267) at org.eclipse.team.internal.ccvs.ui.subscriber.WorkspaceCommitOperation .promptForUnaddedHandling(WorkspaceCommitOperation.java:284) at org.eclipse.team.internal.ccvs.ui.subscriber.WorkspaceCommitOperation .getSyncInfoSet(WorkspaceCommitOperation.java:87) at org.eclipse.team.internal.ccvs.ui.subscriber.WorkspaceCommitOperation .shouldRun(WorkspaceCommitOperation.java:72) at org.eclipse.team.ui.TeamOperation.run(TeamOperation.java:92) at org.eclipse.team.ui.synchronize.SynchronizeModelAction.run(Synchroniz eModelAction.java:110) at org.eclipse.jface.action.Action.runWithEvent(Action.java:881) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection (ActionContributionItem.java:891) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContri butionItem.java:842) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionC ontributionItem.java:761) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1353) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1324) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.jav a:243) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:90 ) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformAct ivator.java:298) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.ja va:249) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.ja va:126) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:41) at java.lang.reflect.Method.invoke(Method.java:386) at org.eclipse.core.launcher.Main.basicRun(Main.java:269) at org.eclipse.core.launcher.Main.run(Main.java:722) at org.eclipse.core.launcher.Main.main(Main.java:706) java.lang.NullPointerException I consider this a blocker, because it indeed "blocks development or testing".
Nobody sets the imageKey on the ReleaseCommentDialog.
Created attachment 10495 [details] Fixed jar for org.eclipse.team.ui plugin
There was a change in behavior of the image registry which surfaced this bug. I have attached the fixed jar, released the changes to HEAD and tagged the map for the next rebuild.