id
int64 1
6.5k
| bug_id
int64 2.03k
426k
| summary
stringlengths 9
251
| description
stringlengths 1
32.8k
⌀ | report_time
stringlengths 19
19
| report_timestamp
int64 1B
1.39B
| status
stringclasses 6
values | commit
stringlengths 7
9
| commit_timestamp
int64 1B
1.39B
| files
stringlengths 25
32.8k
| project_name
stringclasses 6
values |
|---|---|---|---|---|---|---|---|---|---|---|
1,830 | 278,659 |
Bug 278659 [CSS] Border PaintListener leaks one Color instance whenever it's drawn
| null |
2009-06-01 15:13:10
| 1,243,880,000 |
resolved fixed
|
3c57661
| 1,243,890,000 |
bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/helpers/CSSSWTHelpers.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/CSSPropertyBorderSWTHandler.java bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/css2/lazy/border/AbstractCSSPropertyBorderSWTHandler.java
|
Eclipse_Platform_UI
|
1,831 | 278,479 |
Bug 278479 [CSS] SWT unit tests failing "This isn't an RGBColor type"
| null |
2009-05-29 17:48:15
| 1,243,630,000 |
resolved fixed
|
672190f
| 1,243,640,000 |
tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/ButtonTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/CssSwtTestSuite.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/LabelTest.java
|
Eclipse_Platform_UI
|
1,832 | 278,375 |
Bug 278375 [ui] NPE on photo demo shutdown
|
NPE because the restore location is not set. PW
|
2009-05-29 07:56:38
| 1,243,600,000 |
resolved fixed
|
dd2ef68
| 1,243,600,000 |
bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Workbench.java
|
Eclipse_Platform_UI
|
1,833 | 278,369 |
Bug 278369 [ui] ExitHandler fails on dependency injection
|
Simple Example: Until yesterday, I could specify a Handler (that was bound to a command using the workbench model) like this: public class ExitHandler { public void execute(IWorkbench workbench) { workbench.close(); } } Today, I get the exception: java.lang.RuntimeException: could not find satisfiable method execute in class class org.eclipse.e4.demo.contacts.handlers.ExitHandler PW
|
2009-05-29 07:25:10
| 1,243,600,000 |
resolved fixed
|
196d8e0
| 1,243,600,000 |
bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Workbench.java
|
Eclipse_Platform_UI
|
1,834 | 277,966 |
Bug 277966 [Databinding] regression: ObservablesManager throws NPE on dispose if one of the observables is already disposed
| null |
2009-05-26 19:16:03
| 1,243,380,000 |
verified fixed
|
822cb4c
| 1,243,550,000 |
bundles/org.eclipse.core.databinding/src/org/eclipse/core/databinding/ObservablesManager.java tests/org.eclipse.jface.tests.databinding/src/org/eclipse/core/tests/databinding/ObservablesManagerTest.java
|
Eclipse_Platform_UI
|
1,835 | 278,091 |
Bug 278091 [CSS] Measure.getCssText() with float value results in IllegalStateException
|
In theory we should be able to provide percentages as part of the gradients, e.g. CTabFolder:selected { background-color: #FF0000 #0000FF 30% } But this generates IllegalStateException calling getCSSText() on org.apache.batik.css.parser.CSSLexicalUnit$FloatLexicalUnit from Measure.getCSSText().
|
2009-05-27 13:29:55
| 1,243,450,000 |
resolved fixed
|
1e34aed
| 1,243,550,000 |
bundles/org.eclipse.e4.ui.css.core/src/org/eclipse/e4/ui/css/core/impl/dom/Measure.java tests/org.eclipse.e4.ui.tests.css.core/src/org/eclipse/e4/ui/tests/css/core/CssCoreTestSuite.java tests/org.eclipse.e4.ui.tests.css.core/src/org/eclipse/e4/ui/tests/css/core/parser/ValueTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/GradientTest.java
|
Eclipse_Platform_UI
|
1,836 | 278,243 |
Bug 278243 [CSS] Measure missing match for LexicalUnit type 36
|
(appeared in the console running the e4 compat demo)
|
2009-05-28 11:45:05
| 1,243,530,000 |
resolved fixed
|
ff4d8a8
| 1,243,530,000 |
bundles/org.eclipse.e4.ui.css.core/src/org/eclipse/e4/ui/css/core/impl/dom/Measure.java
|
Eclipse_Platform_UI
|
1,837 | 270,797 |
Bug 270797 [EditorMgmt] [perfs] Regression on all OpenMultipleEditorTest.* tests
|
Verifying results for build I20090331-0901, it appears that there's a regression on all OpenMultipleEditorTest.* tests. All those tests are currently commented but for a regression between 3.2 and 3.3. So, this comment must either be removed and the regression investigated again or updated to explain the difference between 3.4 and 3.5...
|
2009-04-01 10:26:01
| 1,238,600,000 |
resolved fixed
|
f4932f7
| 1,243,460,000 |
tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/OpenMultipleEditorTest.java
|
Eclipse_Platform_UI
|
1,838 | 278,065 |
Bug 278065 [GlobalActions] regression: command link to go to preference page broken
|
I20090526-2000, works in R3.4.2. The help command to open a preference page no longer works (opens on last opened page instead of correct one) unless it is clicked/used inside the preference dialog itself.
|
2009-05-27 11:27:07
| 1,243,440,000 |
verified fixed
|
56fc1c1
| 1,243,450,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/actions/ActionFactory.java
|
Eclipse_Platform_UI
|
1,839 | 277,873 |
Bug 277873 [CSS] Exception handling for illegal color name
| null |
2009-05-26 11:23:03
| 1,243,350,000 |
resolved fixed
|
29f6fc9
| 1,243,350,000 |
bundles/org.eclipse.e4.ui.css.swt/src/org/eclipse/e4/ui/css/swt/properties/converters/CSSValueSWTColorConverterImpl.java examples/org.eclipse.e4.ui.examples.css/src/org/eclipse/e4/ui/examples/css/editor/AbstractCSSEditor.java
|
Eclipse_Platform_UI
|
1,840 | 277,676 |
Bug 277676 [UI] The workbench should create the contexts
|
The workbench should create contexts for the model elements, MApplication and MParts (windows, sashes, contributed parts, etc). This is not really the responsibility of the renderers. PW
|
2009-05-25 08:11:42
| 1,243,250,000 |
resolved fixed
|
f338813
| 1,243,260,000 |
bundles/org.eclipse.e4.ui.model.workbench/src/org/eclipse/e4/ui/model/application/ApplicationPackage.java bundles/org.eclipse.e4.ui.model.workbench/src/org/eclipse/e4/ui/model/application/MApplication.java bundles/org.eclipse.e4.ui.model.workbench/src/org/eclipse/e4/ui/model/internal/application/ApplicationPackageImpl.java bundles/org.eclipse.e4.ui.model.workbench/src/org/eclipse/e4/ui/model/internal/application/MApplicationImpl.java bundles/org.eclipse.e4.ui.model.workbench/src/org/eclipse/e4/ui/model/internal/workbench/WorkbenchPackageImpl.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/ContributedPartFactory.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/StackModelFactory.java bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/WBPartFactory.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Workbench.java tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/workbench/MWindowTest.java
|
Eclipse_Platform_UI
|
1,841 | 74,337 |
Bug 74337 FieldEditor should document that doFillIntoGrid() is called from the superclass constructor.
|
The doFillIntoGrid() method is called from the constructor of the FieldEditor class. This should REALLY be documented. It cost me 3 hours of work on a nasty bug. Consider the following addition to the documentation: --------------------------------------------------------------------------- <p> Developers should be aware that FieldEditor calls the doFillIntoGrid() method in its constructor. The significance of this can be demonstrated by the following snippet. </p> <pre> public class RegexPatternSetFieldEditor extends FieldEditor implements SelectionListener,IDoubleClickListener { // .... snip /** The sorted set of patterns. */ private final SortedSet patterns = new TreeSet(new RegexSortingComparator()); // .... snip public RegexPatternSetFieldEditor(final String preferenceName, final String labelText, final Composite parent) { super(preferenceName, labelText, parent); } // .... snip protected void doFillIntoGrid(final Composite parent, final int numColumns) { // .... snip this.tbvPatternList = new TableViewer(table); this.tbvPatternList.setLabelProvider(new RegexPatternLabelProvider()); this.tbvPatternList.setContentProvider( new RegexPatternsContentProvider()); this.tbvPatternList.setInput(this.patterns); // .... snip } } </pre> <p> In this case the user just set <b><code>null</code></b> as input to the table viewer, <code>tbvPatternList</code>. Once you know that this method is called from the superclass constructor, it is self-evident why. Constructors are run before initializers and therefore at the time that the constructor is calling super, <code>this.patterns</code> is <code>null<code>. However, microseconds later when the call to the <code>doFillIntoGrid()</code> is done, the initializers are run. The result is that the viewer is looking at <code>null</code> and yet this.patterns is not null. </p> ---------------------------------------------------------------------------
|
2004-09-20 14:10:59
| 1,095,700,000 |
resolved fixed
|
8a66845
| 1,243,020,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/preference/FieldEditor.java
|
Eclipse_Platform_UI
|
1,842 | 277,513 |
Bug 277513 [Compatibility] Remove WorkbenchFactory
|
The factory is currently used to call the e4 Workbench constructor, but it adds another layer of indirection that we don't need at this point in time. PW
|
2009-05-22 14:14:41
| 1,243,020,000 |
resolved fixed
|
fd9fa1a
| 1,243,020,000 |
bundles/org.eclipse.e4.ui.workbench.swt/src/org/eclipse/e4/ui/workbench/swt/internal/WorkbenchApplication.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/WorkbenchFactory.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Workbench.java tests/org.eclipse.e4.ui.tests/src/org/eclipse/e4/ui/tests/workbench/RunApplicationTest.java
|
Eclipse_Platform_UI
|
1,843 | 276,869 |
Bug 276869 [releng] Add e4 Contact demo to PSF and build
|
org.eclipse.e4.demo.contacts in the directory e4/org.eclipse.e4.ui/examples needs to be added to the PSF and included in the build. PW
|
2009-05-19 07:48:21
| 1,242,730,000 |
resolved fixed
|
d05752d
| 1,242,930,000 |
examples/org.eclipse.e4.demo.contacts/src/org/eclipse/e4/demo/contacts/views/ListView.java
|
Eclipse_Platform_UI
|
1,844 | 277,213 |
Bug 277213 JFace does not run stand-alone
| null |
2009-05-20 16:30:34
| 1,242,850,000 |
verified fixed
|
71876fc
| 1,242,860,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/internal/InternalPolicy.java bundles/org.eclipse.jface/src/org/eclipse/jface/internal/JFaceActivator.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/FileImageDescriptor.java bundles/org.eclipse.jface/src/org/eclipse/jface/resource/URLImageDescriptor.java
|
Eclipse_Platform_UI
|
1,845 | 277,230 |
Bug 277230 [CSS] CSSTestCase should be CSSSWTTestCase
|
Because it's in the SWT test package and references the SWT engine.
|
2009-05-20 17:47:36
| 1,242,860,000 |
resolved fixed
|
44c4c44
| 1,242,860,000 |
tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/ButtonTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/CSSSWTTestCase.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/CSSTestCase.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/CTabFolderTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/IdClassLabelColorTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/LabelTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/ShellActiveTest.java tests/org.eclipse.e4.ui.tests.css.swt/src/org/eclipse/e4/ui/tests/css/swt/ShellTest.java
|
Eclipse_Platform_UI
|
1,846 | 275,932 |
Bug 275932 [CommonNavigator] Window close throws exception in ObservableCollectionTreeContentProvider
|
Build ID: I20090313-0100 Steps To Reproduce: 1. Build an RCP app with a CommonViewer. 2. The CommonViewer uses an ObservableListTreeContentProvider. 3. Close the app workbench window. More information: Below are TWO stack traces. The first is when the ObservableCollectionTreeContentProvider is disposed. The second is when it throws the exception. The window close causes the provider to be disposed. Later, the closure causes a viewer input change, which in turn causes the disposed provider to be used. Since it is already disposed it of course throws an exception. (BTW: Of course there is the immediate problem with the provider, but there is a bigger question: Why is the system trying to change input on a viewer that is in the midst of disposal? I've had to deal with this unexpected behavior before.) ====== Close window -> dispose content provider ====== Thread [main] (Suspended (breakpoint at line 277 in org.eclipse.jface.internal.databinding.viewers.ObservableCollectionTreeContentProvider)) org.eclipse.jface.databinding.viewers.ObservableListTreeContentProvider$Impl(org.eclipse.jface.internal.databinding.viewers.ObservableCollectionTreeContentProvider).dispose() line: 277 com.msli.jme.rcp.provider.JmeModelContentProvider(org.eclipse.jface.databinding.viewers.ObservableListTreeContentProvider).dispose() line: 223 org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider$1.run() line: 69 org.eclipse.core.runtime.SafeRunner.run(org.eclipse.core.runtime.ISafeRunnable) line: 37 org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.dispose() line: 60 org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension$1.run() line: 225 org.eclipse.core.runtime.SafeRunner.run(org.eclipse.core.runtime.ISafeRunnable) line: 37 org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension.dispose() line: 214 org.eclipse.ui.internal.navigator.NavigatorContentService.dispose() line: 343 org.eclipse.ui.navigator.CommonViewer.dispose() line: 251 org.eclipse.ui.navigator.CommonViewer.handleDispose(org.eclipse.swt.events.DisposeEvent) line: 239 org.eclipse.jface.viewers.ContentViewer$2.widgetDisposed(org.eclipse.swt.events.DisposeEvent) line: 214 org.eclipse.swt.widgets.TypedListener.handleEvent(org.eclipse.swt.widgets.Event) line: 117 org.eclipse.swt.widgets.EventTable.sendEvent(org.eclipse.swt.widgets.Event) line: 84 org.eclipse.swt.widgets.Tree(org.eclipse.swt.widgets.Widget).sendEvent(org.eclipse.swt.widgets.Event) line: 1003 org.eclipse.swt.widgets.Tree(org.eclipse.swt.widgets.Widget).sendEvent(int, org.eclipse.swt.widgets.Event, boolean) line: 1027 org.eclipse.swt.widgets.Tree(org.eclipse.swt.widgets.Widget).sendEvent(int) line: 1008 org.eclipse.swt.widgets.Tree(org.eclipse.swt.widgets.Widget).release(boolean) line: 804 org.eclipse.swt.widgets.Composite.releaseChildren(boolean) line: 754 org.eclipse.swt.widgets.Composite(org.eclipse.swt.widgets.Widget).release(boolean) line: 807 org.eclipse.swt.widgets.Composite.releaseChildren(boolean) line: 754 org.eclipse.swt.widgets.Composite(org.eclipse.swt.widgets.Widget).release(boolean) line: 807 org.eclipse.swt.widgets.Composite(org.eclipse.swt.widgets.Widget).dispose() line: 441 org.eclipse.ui.internal.ViewPane(org.eclipse.ui.internal.PartPane).dispose() line: 180 org.eclipse.ui.internal.ViewPane.dispose() line: 192 org.eclipse.ui.internal.ViewReference(org.eclipse.ui.internal.WorkbenchPartReference).dispose() line: 681 org.eclipse.ui.internal.WorkbenchPage.disposePart(org.eclipse.ui.internal.WorkbenchPartReference) line: 1715 org.eclipse.ui.internal.WorkbenchPage.partRemoved(org.eclipse.ui.internal.WorkbenchPartReference) line: 1707 org.eclipse.ui.internal.ViewFactory.releaseView(org.eclipse.ui.IViewReference) line: 256 org.eclipse.ui.internal.Perspective.dispose() line: 289 org.eclipse.ui.internal.WorkbenchPage.dispose() line: 1786 org.eclipse.ui.internal.WorkbenchWindow.closeAllPages() line: 850 org.eclipse.ui.internal.WorkbenchWindow.hardClose() line: 1675 org.eclipse.ui.internal.WorkbenchWindow.busyClose() line: 723 org.eclipse.ui.internal.WorkbenchWindow.access$0(org.eclipse.ui.internal.WorkbenchWindow) line: 699 org.eclipse.ui.internal.WorkbenchWindow$5.run() line: 815 org.eclipse.swt.custom.BusyIndicator.showWhile(org.eclipse.swt.widgets.Display, java.lang.Runnable) line: 70 org.eclipse.ui.internal.WorkbenchWindow.close() line: 813 org.eclipse.jface.window.WindowManager.close() line: 109 org.eclipse.ui.internal.Workbench$16.run() line: 918 org.eclipse.core.runtime.SafeRunner.run(org.eclipse.core.runtime.ISafeRunnable) line: 37 org.eclipse.ui.internal.Workbench.busyClose(boolean) line: 915 org.eclipse.ui.internal.Workbench.access$15(org.eclipse.ui.internal.Workbench, boolean) line: 844 org.eclipse.ui.internal.Workbench$23.run() line: 1088 org.eclipse.swt.custom.BusyIndicator.showWhile(org.eclipse.swt.widgets.Display, java.lang.Runnable) line: 70 org.eclipse.ui.internal.Workbench.close(int, boolean) line: 1086 org.eclipse.ui.internal.Workbench.close() line: 1058 org.eclipse.ui.internal.WorkbenchWindow.busyClose() line: 720 org.eclipse.ui.internal.WorkbenchWindow.access$0(org.eclipse.ui.internal.WorkbenchWindow) line: 699 org.eclipse.ui.internal.WorkbenchWindow$5.run() line: 815 org.eclipse.swt.custom.BusyIndicator.showWhile(org.eclipse.swt.widgets.Display, java.lang.Runnable) line: 70 org.eclipse.ui.internal.WorkbenchWindow.close() line: 813 org.eclipse.ui.internal.WorkbenchWindow(org.eclipse.jface.window.Window).handleShellCloseEvent() line: 741 org.eclipse.jface.window.Window$3.shellClosed(org.eclipse.swt.events.ShellEvent) line: 687 org.eclipse.swt.widgets.TypedListener.handleEvent(org.eclipse.swt.widgets.Event) line: 92 org.eclipse.swt.widgets.EventTable.sendEvent(org.eclipse.swt.widgets.Event) line: 84 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Widget).sendEvent(org.eclipse.swt.widgets.Event) line: 1003 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Widget).sendEvent(int, org.eclipse.swt.widgets.Event, boolean) line: 1027 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Widget).sendEvent(int, org.eclipse.swt.widgets.Event) line: 1012 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).closeWidget() line: 308 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).WM_CLOSE(int, int) line: 1645 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Control).windowProc(int, int, int, int) line: 3919 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Canvas).windowProc(int, int, int, int) line: 342 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).windowProc(int, int, int, int) line: 1578 org.eclipse.swt.widgets.Shell.windowProc(int, int, int, int) line: 1973 org.eclipse.swt.widgets.Display.windowProc(int, int, int, int) line: 4589 org.eclipse.swt.internal.win32.OS.DefWindowProcW(int, int, int, int) line: not available [native method] org.eclipse.swt.internal.win32.OS.DefWindowProc(int, int, int, int) line: 2389 org.eclipse.swt.widgets.Shell.callWindowProc(int, int, int, int) line: 479 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Control).windowProc(int, int, int, int) line: 4007 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Canvas).windowProc(int, int, int, int) line: 342 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).windowProc(int, int, int, int) line: 1578 org.eclipse.swt.widgets.Shell.windowProc(int, int, int, int) line: 1973 org.eclipse.swt.widgets.Display.windowProc(int, int, int, int) line: 4589 org.eclipse.swt.internal.win32.OS.DefWindowProcW(int, int, int, int) line: not available [native method] org.eclipse.swt.internal.win32.OS.DefWindowProc(int, int, int, int) line: 2389 org.eclipse.swt.widgets.Shell.callWindowProc(int, int, int, int) line: 479 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Control).windowProc(int, int, int, int) line: 4007 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Canvas).windowProc(int, int, int, int) line: 342 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).windowProc(int, int, int, int) line: 1578 org.eclipse.swt.widgets.Shell.windowProc(int, int, int, int) line: 1973 org.eclipse.swt.widgets.Display.windowProc(int, int, int, int) line: 4589 org.eclipse.swt.internal.win32.OS.DispatchMessageW(org.eclipse.swt.internal.win32.MSG) line: not available [native method] org.eclipse.swt.internal.win32.OS.DispatchMessage(org.eclipse.swt.internal.win32.MSG) line: 2394 org.eclipse.swt.widgets.Display.readAndDispatch() line: 3471 org.eclipse.ui.internal.Workbench.runEventLoop(org.eclipse.jface.window.Window$IExceptionHandler, org.eclipse.swt.widgets.Display) line: 2393 org.eclipse.ui.internal.Workbench.runUI() line: 2357 org.eclipse.ui.internal.Workbench.access$4(org.eclipse.ui.internal.Workbench) line: 2209 org.eclipse.ui.internal.Workbench$5.run() line: 499 org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 332 org.eclipse.ui.internal.Workbench.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 492 org.eclipse.ui.PlatformUI.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 149 com.msli.mapp3d.client.rcp.app.Application.start(org.eclipse.equinox.app.IApplicationContext) line: 87 org.eclipse.equinox.internal.app.EclipseAppHandle.run(java.lang.Object) line: 194 org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(java.lang.Object) line: 110 org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(java.lang.Object) line: 79 org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.Object) line: 368 org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.String[], java.lang.Runnable) line: 179 sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) line: not available [native method] sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 39 sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 25 java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line: 597 org.eclipse.equinox.launcher.Main.invokeFramework(java.lang.String[], java.net.URL[]) line: 556 org.eclipse.equinox.launcher.Main.basicRun(java.lang.String[]) line: 511 org.eclipse.equinox.launcher.Main.run(java.lang.String[]) line: 1284 org.eclipse.equinox.launcher.Main.main(java.lang.String[]) line: 1260 ============ input changed -> exception throw =========== Thread [main] (Suspended (exception java.lang.NullPointerException)) org.eclipse.jface.databinding.viewers.ObservableListTreeContentProvider$Impl(org.eclipse.jface.internal.databinding.viewers.ObservableCollectionTreeContentProvider).setViewer(org.eclipse.jface.viewers.Viewer) line: 152 org.eclipse.jface.databinding.viewers.ObservableListTreeContentProvider$Impl(org.eclipse.jface.internal.databinding.viewers.ObservableCollectionTreeContentProvider).inputChanged(org.eclipse.jface.viewers.Viewer, java.lang.Object, java.lang.Object) line: 141 org.eclipse.jface.databinding.viewers.ObservableListTreeContentProvider$Impl.inputChanged(org.eclipse.jface.viewers.Viewer, java.lang.Object, java.lang.Object) line: 55 com.msli.jme.rcp.provider.JmeModelContentProvider(org.eclipse.jface.databinding.viewers.ObservableListTreeContentProvider).inputChanged(org.eclipse.jface.viewers.Viewer, java.lang.Object, java.lang.Object) line: 203 org.eclipse.ui.internal.navigator.extensions.StructuredViewerManager.initialize(org.eclipse.jface.viewers.IStructuredContentProvider) line: 139 org.eclipse.ui.internal.navigator.NavigatorContentService.updateService(org.eclipse.jface.viewers.Viewer, java.lang.Object, java.lang.Object) line: 369 org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.inputChanged(org.eclipse.jface.viewers.Viewer, java.lang.Object, java.lang.Object) line: 591 org.eclipse.ui.navigator.CommonViewer(org.eclipse.jface.viewers.ContentViewer).handleDispose(org.eclipse.swt.events.DisposeEvent) line: 171 org.eclipse.ui.navigator.CommonViewer(org.eclipse.jface.viewers.StructuredViewer).handleDispose(org.eclipse.swt.events.DisposeEvent) line: 2272 org.eclipse.ui.navigator.CommonViewer.handleDispose(org.eclipse.swt.events.DisposeEvent) line: 240 org.eclipse.jface.viewers.ContentViewer$2.widgetDisposed(org.eclipse.swt.events.DisposeEvent) line: 214 org.eclipse.swt.widgets.TypedListener.handleEvent(org.eclipse.swt.widgets.Event) line: 117 org.eclipse.swt.widgets.EventTable.sendEvent(org.eclipse.swt.widgets.Event) line: 84 org.eclipse.swt.widgets.Tree(org.eclipse.swt.widgets.Widget).sendEvent(org.eclipse.swt.widgets.Event) line: 1003 org.eclipse.swt.widgets.Tree(org.eclipse.swt.widgets.Widget).sendEvent(int, org.eclipse.swt.widgets.Event, boolean) line: 1027 org.eclipse.swt.widgets.Tree(org.eclipse.swt.widgets.Widget).sendEvent(int) line: 1008 org.eclipse.swt.widgets.Tree(org.eclipse.swt.widgets.Widget).release(boolean) line: 804 org.eclipse.swt.widgets.Composite.releaseChildren(boolean) line: 754 org.eclipse.swt.widgets.Composite(org.eclipse.swt.widgets.Widget).release(boolean) line: 807 org.eclipse.swt.widgets.Composite.releaseChildren(boolean) line: 754 org.eclipse.swt.widgets.Composite(org.eclipse.swt.widgets.Widget).release(boolean) line: 807 org.eclipse.swt.widgets.Composite(org.eclipse.swt.widgets.Widget).dispose() line: 441 org.eclipse.ui.internal.ViewPane(org.eclipse.ui.internal.PartPane).dispose() line: 180 org.eclipse.ui.internal.ViewPane.dispose() line: 192 org.eclipse.ui.internal.ViewReference(org.eclipse.ui.internal.WorkbenchPartReference).dispose() line: 681 org.eclipse.ui.internal.WorkbenchPage.disposePart(org.eclipse.ui.internal.WorkbenchPartReference) line: 1715 org.eclipse.ui.internal.WorkbenchPage.partRemoved(org.eclipse.ui.internal.WorkbenchPartReference) line: 1707 org.eclipse.ui.internal.ViewFactory.releaseView(org.eclipse.ui.IViewReference) line: 256 org.eclipse.ui.internal.Perspective.dispose() line: 289 org.eclipse.ui.internal.WorkbenchPage.dispose() line: 1786 org.eclipse.ui.internal.WorkbenchWindow.closeAllPages() line: 850 org.eclipse.ui.internal.WorkbenchWindow.hardClose() line: 1675 org.eclipse.ui.internal.WorkbenchWindow.busyClose() line: 723 org.eclipse.ui.internal.WorkbenchWindow.access$0(org.eclipse.ui.internal.WorkbenchWindow) line: 699 org.eclipse.ui.internal.WorkbenchWindow$5.run() line: 815 org.eclipse.swt.custom.BusyIndicator.showWhile(org.eclipse.swt.widgets.Display, java.lang.Runnable) line: 70 org.eclipse.ui.internal.WorkbenchWindow.close() line: 813 org.eclipse.jface.window.WindowManager.close() line: 109 org.eclipse.ui.internal.Workbench$16.run() line: 918 org.eclipse.core.runtime.SafeRunner.run(org.eclipse.core.runtime.ISafeRunnable) line: 37 org.eclipse.ui.internal.Workbench.busyClose(boolean) line: 915 org.eclipse.ui.internal.Workbench.access$15(org.eclipse.ui.internal.Workbench, boolean) line: 844 org.eclipse.ui.internal.Workbench$23.run() line: 1088 org.eclipse.swt.custom.BusyIndicator.showWhile(org.eclipse.swt.widgets.Display, java.lang.Runnable) line: 70 org.eclipse.ui.internal.Workbench.close(int, boolean) line: 1086 org.eclipse.ui.internal.Workbench.close() line: 1058 org.eclipse.ui.internal.WorkbenchWindow.busyClose() line: 720 org.eclipse.ui.internal.WorkbenchWindow.access$0(org.eclipse.ui.internal.WorkbenchWindow) line: 699 org.eclipse.ui.internal.WorkbenchWindow$5.run() line: 815 org.eclipse.swt.custom.BusyIndicator.showWhile(org.eclipse.swt.widgets.Display, java.lang.Runnable) line: 70 org.eclipse.ui.internal.WorkbenchWindow.close() line: 813 org.eclipse.ui.internal.WorkbenchWindow(org.eclipse.jface.window.Window).handleShellCloseEvent() line: 741 org.eclipse.jface.window.Window$3.shellClosed(org.eclipse.swt.events.ShellEvent) line: 687 org.eclipse.swt.widgets.TypedListener.handleEvent(org.eclipse.swt.widgets.Event) line: 92 org.eclipse.swt.widgets.EventTable.sendEvent(org.eclipse.swt.widgets.Event) line: 84 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Widget).sendEvent(org.eclipse.swt.widgets.Event) line: 1003 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Widget).sendEvent(int, org.eclipse.swt.widgets.Event, boolean) line: 1027 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Widget).sendEvent(int, org.eclipse.swt.widgets.Event) line: 1012 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).closeWidget() line: 308 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).WM_CLOSE(int, int) line: 1645 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Control).windowProc(int, int, int, int) line: 3919 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Canvas).windowProc(int, int, int, int) line: 342 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).windowProc(int, int, int, int) line: 1578 org.eclipse.swt.widgets.Shell.windowProc(int, int, int, int) line: 1973 org.eclipse.swt.widgets.Display.windowProc(int, int, int, int) line: 4589 org.eclipse.swt.internal.win32.OS.DefWindowProcW(int, int, int, int) line: not available [native method] org.eclipse.swt.internal.win32.OS.DefWindowProc(int, int, int, int) line: 2389 org.eclipse.swt.widgets.Shell.callWindowProc(int, int, int, int) line: 479 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Control).windowProc(int, int, int, int) line: 4007 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Canvas).windowProc(int, int, int, int) line: 342 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).windowProc(int, int, int, int) line: 1578 org.eclipse.swt.widgets.Shell.windowProc(int, int, int, int) line: 1973 org.eclipse.swt.widgets.Display.windowProc(int, int, int, int) line: 4589 org.eclipse.swt.internal.win32.OS.DefWindowProcW(int, int, int, int) line: not available [native method] org.eclipse.swt.internal.win32.OS.DefWindowProc(int, int, int, int) line: 2389 org.eclipse.swt.widgets.Shell.callWindowProc(int, int, int, int) line: 479 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Control).windowProc(int, int, int, int) line: 4007 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Canvas).windowProc(int, int, int, int) line: 342 org.eclipse.swt.widgets.Shell(org.eclipse.swt.widgets.Decorations).windowProc(int, int, int, int) line: 1578 org.eclipse.swt.widgets.Shell.windowProc(int, int, int, int) line: 1973 org.eclipse.swt.widgets.Display.windowProc(int, int, int, int) line: 4589 org.eclipse.swt.internal.win32.OS.DispatchMessageW(org.eclipse.swt.internal.win32.MSG) line: not available [native method] org.eclipse.swt.internal.win32.OS.DispatchMessage(org.eclipse.swt.internal.win32.MSG) line: 2394 org.eclipse.swt.widgets.Display.readAndDispatch() line: 3471 org.eclipse.ui.internal.Workbench.runEventLoop(org.eclipse.jface.window.Window$IExceptionHandler, org.eclipse.swt.widgets.Display) line: 2393 org.eclipse.ui.internal.Workbench.runUI() line: 2357 org.eclipse.ui.internal.Workbench.access$4(org.eclipse.ui.internal.Workbench) line: 2209 org.eclipse.ui.internal.Workbench$5.run() line: 499 org.eclipse.core.databinding.observable.Realm.runWithDefault(org.eclipse.core.databinding.observable.Realm, java.lang.Runnable) line: 332 org.eclipse.ui.internal.Workbench.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 492 org.eclipse.ui.PlatformUI.createAndRunWorkbench(org.eclipse.swt.widgets.Display, org.eclipse.ui.application.WorkbenchAdvisor) line: 149 com.msli.mapp3d.client.rcp.app.Application.start(org.eclipse.equinox.app.IApplicationContext) line: 87 org.eclipse.equinox.internal.app.EclipseAppHandle.run(java.lang.Object) line: 194 org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(java.lang.Object) line: 110 org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(java.lang.Object) line: 79 org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.Object) line: 368 org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.String[], java.lang.Runnable) line: 179 sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) line: not available [native method] sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 39 sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 25 java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line: 597 org.eclipse.equinox.launcher.Main.invokeFramework(java.lang.String[], java.net.URL[]) line: 556 org.eclipse.equinox.launcher.Main.basicRun(java.lang.String[]) line: 511 org.eclipse.equinox.launcher.Main.run(java.lang.String[]) line: 1284 org.eclipse.equinox.launcher.Main.main(java.lang.String[]) line: 1260
|
2009-05-12 14:13:04
| 1,242,150,000 |
resolved fixed
|
5a501e0
| 1,242,850,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentService.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/ViewerTest.java tests/org.eclipse.ui.tests.navigator/src/org/eclipse/ui/tests/navigator/extension/TestContentProvider.java
|
Eclipse_Platform_UI
|
1,847 | 276,520 |
Bug 276520 [PropertiesView] [Views] Properties Views interfere with each other
|
Found in I20090514-2000. Open two property views and put them in different stacks (both visible) Select a resource in the explorer, they both populate Click on one of them and the other goes blank Click on the blank one and now they're both blank Is the Property View itself acting as a property provider?
|
2009-05-15 11:26:36
| 1,242,400,000 |
verified fixed
|
ea9c62f
| 1,242,840,000 |
bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/PropertySheet.java
|
Eclipse_Platform_UI
|
1,848 | 276,525 |
Bug 276525 [Commands] Cascading menus clear before closing.
| null |
2009-05-15 12:05:27
| 1,242,400,000 |
verified fixed
|
e23052c
| 1,242,840,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/actions/CompoundContributionItem.java
|
Eclipse_Platform_UI
|
1,849 | 274,132 |
Bug 274132 [FastView] Artifacts when starting workspace that has open fast view
| null |
2009-04-28 14:00:50
| 1,240,940,000 |
verified fixed
|
bfa681e
| 1,242,320,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchPage.java
|
Eclipse_Platform_UI
|
1,850 | 248,908 |
Bug 248908 [Forms] BusyIndicator deadlocks UI thread
|
Build ID: 3.4.0 Steps To Reproduce: 1. Create a Form editor 2. Listen for PROP_DIRTY events 3. when form is dirty show the BusyIndicator by calling form.setBusy(true) 3. then when editor is not dirty anymore disable the BusyIndicator by calling form.setBusy(false) 4. the application will lock, UI thread is waiting on th synchronized setBusy() while the BusyIndicator thread is also waiting on syncExec(). More information: I have been debugging my RCP application during a whole day to find why the application was freezing. I like to have the BusyIndicator shown when the editor is dirty, and when i save it, the UI locked. Disabling the BusyIndicator solved my problem, i took time to test the BusyIndicator because i thought the problem can not come from the Eclipse Framework itself, but it seems it's a bug ! Thanks.
|
2008-09-29 05:42:27
| 1,222,680,000 |
resolved fixed
|
dfdff8e
| 1,242,320,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/internal/forms/widgets/BusyIndicator.java
|
Eclipse_Platform_UI
|
1,851 | 264,804 |
Bug 264804 [Contributions] extended popup menu item with <visibleWhen> attribute will disappear when right click multiple times.
| null |
2009-02-12 23:55:32
| 1,234,500,000 |
resolved fixed
|
6304f4c
| 1,242,310,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PopupMenuExtender.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/menus/Bug264804Test.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/menus/MenusTestSuite.java
|
Eclipse_Platform_UI
|
1,852 | 272,307 |
Bug 272307 [Mac] CocoaUIEnhancer crashes with NullPointer under Mac OS X Cocoa when running Riena example
|
When bringing up the Riena example app, we get a NullPointer Exception. The exception is logged and the app continues to run. I am unsure why that is happening. Same app runs without a problem with windows, linux, mac os x carbon. I will supply a screenshot of the debugger before the nullpointer happens and a screen shot of the actual app. Its a little tricky to set up the Riena example app yourself unless you like to download Riena and setup a target platform and all that. Then I am happy to post you a link with description. I will also attach the stacktrace with some error messages. Hope that helps to get to the cause of the problem.
|
2009-04-15 09:35:33
| 1,239,800,000 |
verified fixed
|
66e346e
| 1,242,230,000 |
bundles/org.eclipse.ui.cocoa/src/org/eclipse/ui/internal/cocoa/CocoaUIEnhancer.java
|
Eclipse_Platform_UI
|
1,853 | 275,929 |
Bug 275929 [CommonNavigator] IPipelinedTreeContentProvider.getPipelinedElements() not ever called
| null |
2009-05-12 13:58:04
| 1,242,150,000 |
resolved fixed
|
6694eaf
| 1,242,150,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentServiceContentProvider.java
|
Eclipse_Platform_UI
|
1,854 | 275,627 |
Bug 275627 [Forms] Leak: BusyIndicator must ensure to properly dispose created images on disposal
|
Build ID: M20090211-1700 Steps To Reproduce: 1. Use a SharedHeaderFormEditor and setBusy(true) when setting an input 2. Close the editor while busy is still set to true Actual results: The 8 progress images (spinning wheel) created by BusyIndicator are only disposed in clearImages() when the busyThread is NULL, however its only set to true if explicitly disposed or setBusy(false) is called. Proposed solution: Ensure to dispose alles images from the imageCache as soon as the canvas (BusyIndicator's parent class) is disposed. Is there anything we can do to work around this problem? I tried to call "getHeaderForm().getForm().setBusy(false)" from the dispose method of SharedHeaderFormEditor however this seems a little risky because it may trigger a layout of the header area and I am not sure what the impact is when this happens during dispose.
|
2009-05-11 05:54:46
| 1,242,040,000 |
resolved fixed
|
d53be3b
| 1,242,150,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/internal/forms/widgets/BusyIndicator.java
|
Eclipse_Platform_UI
|
1,855 | 275,197 |
Bug 275197 [CommonNavigator] NullPointerException - Working set actions don't appear in CNF client
|
Build ID: I20090430-2300 Steps To Reproduce: While restoring the selection with the CNF, the WorkingSetRootModeActionGroup tries to addActions(IMenuManager viewMenu) without having the actions created. The stack-trace shows more information on how that happens (and hopefully is enough to understand it). The point where this happens is when a client (pydev package explorer) tries to restore the selection right after starting eclipse. Also, this doesn't always happen (so, it seems like it's a racing condition). The actions are created at setShowTopLevelWorkingSets(), but it seems that this method is called only after the addActions() sometimes. More information: The stack trace for that bug is: java.lang.NullPointerException at org.eclipse.ui.internal.navigator.resources.actions.WorkingSetRootModeActionGroup.addActions(WorkingSetRootModeActionGroup.java:139) at org.eclipse.ui.internal.navigator.resources.actions.WorkingSetRootModeActionGroup.contributeToViewMenu(WorkingSetRootModeActionGroup.java:128) at org.eclipse.ui.internal.navigator.resources.actions.WorkingSetRootModeActionGroup.fillActionBars(WorkingSetRootModeActionGroup.java:118) at org.eclipse.ui.internal.navigator.resources.actions.WorkingSetActionProvider.fillActionBars(WorkingSetActionProvider.java:368) at org.eclipse.ui.navigator.NavigatorActionService.fillActionBars(NavigatorActionService.java:255) at org.eclipse.ui.navigator.CommonNavigatorManager.selectionChanged(CommonNavigatorManager.java:239) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2132) at org.eclipse.jface.viewers.StructuredViewer.handleInvalidSelection(StructuredViewer.java:1124) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1405) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:402) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1353) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1482) at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:548) at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:358) at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:515) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1414) at org.eclipse.jface.viewers.StructuredViewer.addFilter(StructuredViewer.java:582) at org.eclipse.ui.internal.navigator.resources.actions.WorkingSetActionProvider.setWorkingSet(WorkingSetActionProvider.java:280) at org.eclipse.ui.internal.navigator.resources.actions.WorkingSetActionProvider$3.propertyChange(WorkingSetActionProvider.java:226) at org.eclipse.ui.internal.navigator.extensions.ExtensionStateModel.firePropertyChangeEvent(ExtensionStateModel.java:135) at org.eclipse.ui.internal.navigator.extensions.ExtensionStateModel.setBooleanProperty(ExtensionStateModel.java:90) at org.eclipse.ui.internal.navigator.resources.actions.WorkingSetActionProvider.restoreState(WorkingSetActionProvider.java:318) at org.eclipse.ui.navigator.NavigatorActionService.initialize(NavigatorActionService.java:372) at org.eclipse.ui.navigator.NavigatorActionService.getActionProviderInstance(NavigatorActionService.java:355) at org.eclipse.ui.navigator.NavigatorActionService.fillActionBars(NavigatorActionService.java:253) at org.eclipse.ui.navigator.CommonNavigatorManager.selectionChanged(CommonNavigatorManager.java:239) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2132) at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1669) at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1109) at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:382) at org.python.pydev.navigator.PyPackageStateSaver.restoreState(PyPackageStateSaver.java:95) at org.python.pydev.navigator.PythonModelProvider.restoreState(PythonModelProvider.java:245) at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.restoreState(SafeDelegateTreeContentProvider.java:155) at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension.applyMemento(NavigatorContentExtension.java:330) at org.eclipse.ui.internal.navigator.extensions.NavigatorContentExtension.restoreState(NavigatorContentExtension.java:311) at org.eclipse.ui.internal.navigator.NavigatorContentService$1.run(NavigatorContentService.java:933) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.navigator.NavigatorContentService.restoreState(NavigatorContentService.java:948) at org.python.pydev.navigator.ui.PydevPackageExplorer.createPartControl(PydevPackageExplorer.java:171) at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:367) at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:226) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313) at org.eclipse.ui.internal.ViewPane.setVisible(ViewPane.java:529) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1256) at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:668) at org.eclipse.ui.internal.PartStack.createControl(PartStack.java:576) at org.eclipse.ui.internal.PartSashContainer.createControl(PartSashContainer.java:568) at org.eclipse.ui.internal.PerspectiveHelper.activate(PerspectiveHelper.java:272) at org.eclipse.ui.internal.Perspective.onActivate(Perspective.java:978) at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:2626) at org.eclipse.ui.internal.WorkbenchWindow$27.run(WorkbenchWindow.java:2962) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchWindow.setActivePage(WorkbenchWindow.java:2943) at org.eclipse.ui.internal.WorkbenchWindow$21.runWithException(WorkbenchWindow.java:2260) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
|
2009-05-06 14:25:26
| 1,241,630,000 |
resolved fixed
|
7dd8e76
| 1,242,090,000 |
bundles/org.eclipse.ui.navigator.resources/src/org/eclipse/ui/internal/navigator/resources/actions/WorkingSetRootModeActionGroup.java
|
Eclipse_Platform_UI
|
1,856 | 275,691 |
Bug 275691 [DataBinding] 2 NPEs when running tests on linux
|
Just running the databinding AllTests on linux with I20090508-2000 and platform-ui from HEAD JFace-Data Binding Test Suite org.eclipse.jface.tests.databinding.BindingTestSetup org.eclipse.jface.tests.databinding.BindingTestSuite org.eclipse.jface.tests.databinding.wizard.WizardPageSupportTest testPageComplete(org.eclipse.jface.tests.databinding.wizard.WizardPageSupportTest) java.lang.NullPointerException at org.eclipse.core.internal.databinding.observable.EmptyObservableList.checkRealm(EmptyObservableList.java:85) at org.eclipse.core.internal.databinding.observable.EmptyObservableList.iterator(EmptyObservableList.java:100) at org.eclipse.jface.databinding.dialog.DialogPageSupport.dispose(DialogPageSupport.java:317) at org.eclipse.jface.databinding.dialog.DialogPageSupport$5.handleEvent(DialogPageSupport.java:160) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1200) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1181) at org.eclipse.swt.widgets.Widget.release(Widget.java:1044) at org.eclipse.swt.widgets.Control.release(Control.java:3286) at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:2044) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3286) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446) at org.eclipse.swt.widgets.Shell.dispose(Shell.java:1992) at org.eclipse.jface.tests.databinding.AbstractSWTTestCase.tearDown(AbstractSWTTestCase.java:43) at junit.framework.TestCase.runBare(TestCase.java:136) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.CoreTestApplication.run(CoreTestApplication.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) testPageCompleteOnValidationStaleness(org.eclipse.jface.tests.databinding.wizard.WizardPageSupportTest) java.lang.NullPointerException at org.eclipse.core.internal.databinding.observable.EmptyObservableList.checkRealm(EmptyObservableList.java:85) at org.eclipse.core.internal.databinding.observable.EmptyObservableList.iterator(EmptyObservableList.java:100) at org.eclipse.jface.databinding.dialog.DialogPageSupport.dispose(DialogPageSupport.java:317) at org.eclipse.jface.databinding.dialog.DialogPageSupport$5.handleEvent(DialogPageSupport.java:160) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1200) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1181) at org.eclipse.swt.widgets.Widget.release(Widget.java:1044) at org.eclipse.swt.widgets.Control.release(Control.java:3286) at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:2044) at org.eclipse.swt.widgets.Widget.release(Widget.java:1047) at org.eclipse.swt.widgets.Control.release(Control.java:3286) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446) at org.eclipse.swt.widgets.Shell.dispose(Shell.java:1992) at org.eclipse.jface.tests.databinding.AbstractSWTTestCase.tearDown(AbstractSWTTestCase.java:43) at junit.framework.TestCase.runBare(TestCase.java:136) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) at org.eclipse.pde.internal.junit.runtime.CoreTestApplication.run(CoreTestApplication.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
|
2009-05-11 13:22:38
| 1,242,060,000 |
resolved fixed
|
e289b8e
| 1,242,080,000 |
tests/org.eclipse.jface.tests.databinding/src/org/eclipse/jface/tests/databinding/AbstractSWTTestCase.java
|
Eclipse_Platform_UI
|
1,857 | 275,298 |
Bug 275298 [About] IInstallationPageContainer and InstallationPage still claims to be experimental
|
Both types are from org.eclipse.ui.about and claims to be experimental and may change before 3.5. I suggest tagging as @noreference if the claim is valid or removing the claim if it is no longer valid.
|
2009-05-07 09:21:01
| 1,241,700,000 |
verified fixed
|
14e6b93
| 1,242,080,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/about/IInstallationPageContainer.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/about/InstallationPage.java
|
Eclipse_Platform_UI
|
1,858 | 275,678 |
Bug 275678 [Dialogs][EditorMgmt] Revert usage of new openEditors API
| null |
2009-05-11 11:38:02
| 1,242,060,000 |
verified fixed
|
5e032cc
| 1,242,070,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/handlers/OpenResourceHandler.java
|
Eclipse_Platform_UI
|
1,859 | 275,170 |
Bug 275170 [ICU] Degradation comment for performance regression in CollatorPerformanceTest#testCollator
| null |
2009-05-06 11:33:09
| 1,241,620,000 |
verified fixed
|
254d9d5
| 1,242,070,000 |
tests/org.eclipse.ui.tests.performance/src/org/eclipse/jface/tests/performance/CollatorPerformanceTest.java
|
Eclipse_Platform_UI
|
1,860 | 270,795 |
Bug 270795 [Contributions] [perfs] Regression on ObjectContributionsPerformance#testObjectContributions test
|
Verifying results for build I20090331-0901, it appears that there's a regression on 'ObjectContributionsPerformance#testObjectContributions:limited selection, limited contributors()' test. This test is currently commented but for a regression between 3.1 and 3.2. So, this comment must either be removed and the regression investigated or updated to explain the difference between 3.4 and 3.5... Looking at history, it seems that the regression got introduce with build I20090120-0920...
|
2009-04-01 10:21:14
| 1,238,600,000 |
verified fixed
|
94bfaf0
| 1,242,060,000 |
tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/ObjectContributionsPerformance.java
|
Eclipse_Platform_UI
|
1,861 | 262,636 |
Bug 262636 Hidden menu items are not updated on perspective switches
|
Found when checking the new Customize Perspective Dialog behavior... If you have both the Java and Debug perspective open and hide a menu or toolbar item that is visible in both (i.e. the Search->Search tb item) then it won't get hidden/shown when you switch perspectives.
|
2009-01-27 14:18:10
| 1,233,080,000 |
verified fixed
|
80769f5
| 1,242,050,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Perspective.java
|
Eclipse_Platform_UI
|
1,862 | 273,828 |
Bug 273828 [Contributions] Regression (Widget is disposed) in CommandContributionItem
| null |
2009-04-27 09:12:56
| 1,240,840,000 |
verified fixed
|
ad6de63
| 1,242,050,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/menus/CommandContributionItem.java
|
Eclipse_Platform_UI
|
1,863 | 275,171 |
Bug 275171 [Contributions] Customize Perspective action breaks editor pinning action
|
Using M7, I enabled editor pinning (i.e. Reuse editor) and pinned an editor using an action in the toolbar. I then disabled editor pinning ad then opened the customized perspective dialog. After this, enabling/disabling editor pinning does not make the Pin Editor action reappear.
|
2009-05-06 11:34:16
| 1,241,620,000 |
verified fixed
|
b83b648
| 1,242,050,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/WorkbenchActionBuilder.java
|
Eclipse_Platform_UI
|
1,864 | 268,533 |
Bug 268533 [Viewers] Weird painting when using MOUSE_CLICK_ACTIVATION
| null |
2009-03-13 10:17:36
| 1,236,950,000 |
verified fixed
|
db1e196
| 1,242,050,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/FocusCellHighlighter.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/SWTFocusCellManager.java
|
Eclipse_Platform_UI
|
1,865 | 271,744 |
Bug 271744 [Viewers] [JFace] TreeViewer not closing CellEditors on Collapse
| null |
2009-04-09 05:02:45
| 1,239,270,000 |
verified fixed
|
16e2860
| 1,242,030,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TreeViewer.java
|
Eclipse_Platform_UI
|
1,866 | 275,509 |
Bug 275509 [Viewers] Tree/TableViewer with cell navigation is not accessible
| null |
2009-05-08 15:58:42
| 1,241,810,000 |
resolved fixed
|
771a4e9
| 1,241,950,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/SWTFocusCellManager.java
|
Eclipse_Platform_UI
|
1,867 | 274,618 |
Bug 274618 [EditorMgmt] StackOverflowError for an editor with a NullEditorInput
|
Even if I don't have exact steps to reproduce, I ran into this StackOverflowError with a very clear stack trace indicating an infinite recursion... java.lang.StackOverflowError at org.eclipse.ui.internal.EditorReference.getPart(EditorReference.java:821) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:283) at org.eclipse.ui.internal.EditorReference.getName(EditorReference.java:277) at org.eclipse.ui.internal.part.NullEditorInput.getName(NullEditorInput.java:66) at org.eclipse.ui.internal.EditorReference.getName(EditorReference.java:277) at org.eclipse.ui.internal.part.NullEditorInput.getName(NullEditorInput.java:66) at org.eclipse.ui.internal.EditorReference.getName(EditorReference.java:277) at org.eclipse.ui.internal.part.NullEditorInput.getName(NullEditorInput.java:66) at org.eclipse.ui.internal.EditorReference.getName(EditorReference.java:277) at org.eclipse.ui.internal.part.NullEditorInput.getName(NullEditorInput.java:66) at org.eclipse.ui.internal.EditorReference.getName(EditorReference.java:277) [...]
|
2009-04-30 19:47:34
| 1,241,140,000 |
resolved fixed
|
ec54e5e
| 1,241,810,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorReference.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/part/NullEditorInput.java
|
Eclipse_Platform_UI
|
1,868 | 130,043 |
Bug 130043 [Forms] Content is not allowed in prolog.
|
When specifying non-"HTML" text to FormText.setText() where parseTags is true "[Fatal Error] :1:1: Content is not allowed in prolog." will be output to stderr. The cause is FormTextModel.parseInputStream() is not setting an error handler on the parser (by default errors are reported to stderr). There are a number of bug reports against Eclipse in general where this type of error is seen (and most of them have been marked as "can't reproduce"). Could someone push out a general announcement to the dev team stating that whenever an XML parser is used, an error handler needs to be set so that these messages don't default to the console?
|
2006-03-01 17:48:33
| 1,141,250,000 |
resolved fixed
|
409cb2f
| 1,241,810,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/internal/forms/widgets/FormTextModel.java
|
Eclipse_Platform_UI
|
1,869 | 270,465 |
Bug 270465 [ErrorHandling] SafeRunnableDialog layout needs polish
|
I20090313-0100 I ran a JFace snippet and the error dialog popped up. Looks ugly.
|
2009-03-30 11:04:09
| 1,238,430,000 |
resolved fixed
|
c2687b8
| 1,241,810,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/util/SafeRunnableDialog.java
|
Eclipse_Platform_UI
|
1,870 | 260,061 |
Bug 260061 [Snippets] Example Snippet how to implement native checkboxes
| null |
2009-01-06 11:31:05
| 1,231,260,000 |
verified fixed
|
0316fdc
| 1,241,800,000 |
examples/org.eclipse.jface.snippets/Eclipse JFace Snippets/org/eclipse/jface/snippets/viewers/BooleanCellEditor.java examples/org.eclipse.jface.snippets/Eclipse JFace Snippets/org/eclipse/jface/snippets/viewers/Snippet061FakedNativeCellEditor.java
|
Eclipse_Platform_UI
|
1,871 | 272,528 |
Bug 272528 [WorkingSets] AIOOBE when trying to remove breakpoint by doubleclick on nearby line
|
I20090415-1348 - have: public class Try { String s= "Hello" + "World"; static { String foo= "bar"; System.out.println(foo); } } - doubleclick in vertical ruler on line ' + "World";' - doubleclick again - ... and on the third doubleclick, I get the AIOOBE below. My Breakpoints view is visible and grouped by Breakpoint Working Sets. When I do the same on the empty line before 'String foo= "bar";', I get a similar exception. !ENTRY org.eclipse.debug.core 4 2 2009-04-16 18:43:15.127 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.debug.core". !STACK 0 java.lang.ArrayIndexOutOfBoundsException: -1 at com.ibm.icu.text.RuleBasedCollator.append(RuleBasedCollator.java:3492) at com.ibm.icu.text.RuleBasedCollator.doPrimaryCompare(RuleBasedCollator.java:3280) at com.ibm.icu.text.RuleBasedCollator.compareRegular(RuleBasedCollator.java:2299) at com.ibm.icu.text.RuleBasedCollator.compare(RuleBasedCollator.java:1292) at org.eclipse.ui.internal.WorkingSetComparator.compare(WorkingSetComparator.java:48) at java.util.TreeMap.put(TreeMap.java:530) at java.util.TreeSet.add(TreeSet.java:238) at org.eclipse.ui.internal.AbstractWorkingSetManager.getWorkingSets(AbstractWorkingSetManager.java:265) at org.eclipse.debug.internal.ui.views.breakpoints.BreakpointSetOrganizer.breakpointsRemoved(BreakpointSetOrganizer.java:242) at org.eclipse.debug.internal.core.BreakpointManager$BreakpointsNotifier.run(BreakpointManager.java:992) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.debug.internal.core.BreakpointManager$BreakpointsNotifier.notify(BreakpointManager.java:1014) at org.eclipse.debug.internal.core.BreakpointManager.fireUpdate(BreakpointManager.java:868) at org.eclipse.debug.internal.core.BreakpointManager.removeBreakpoints(BreakpointManager.java:476) at org.eclipse.debug.internal.core.BreakpointManager.removeBreakpoint(BreakpointManager.java:455) at org.eclipse.jdt.internal.debug.ui.actions.BreakpointLocationVerifierJob.manageLineBreakpoint(BreakpointLocationVerifierJob.java:234) at org.eclipse.jdt.internal.debug.ui.actions.BreakpointLocationVerifierJob.run(BreakpointLocationVerifierJob.java:176) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
|
2009-04-16 12:50:48
| 1,239,900,000 |
verified fixed
|
537a79b
| 1,241,800,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/AbstractWorkingSetManager.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkingSetComparator.java
|
Eclipse_Platform_UI
|
1,872 | 116,284 |
Bug 116284 [RCP] Performance Tests Failing: RCP rcp.performance.EmptyWorkbenchPerfTest#testRestore() [close]
|
3.2 M3 rcp.performance.EmptyWorkbenchPerfTest#testRestore() [close] This test is running too fast and failing on most test machines
|
2005-11-14 12:48:04
| 1,131,990,000 |
verified fixed
|
dfcfb18
| 1,241,790,000 |
tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/performance/EmptyWorkbenchPerfTest.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/util/IPerformanceMeterArray.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/util/IntervalMeters.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/util/NullMeters.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/util/OpenWorkbenchIntervalMonitor.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/util/RestoreWorkbenchIntervalMonitor.java
|
Eclipse_Platform_UI
|
1,873 | 271,339 |
Bug 271339 [FieldAssist] Add CC text field content assist doesn't work as expected when narrowing suggestions
|
Continued typing in the text field should narrow the list of results displayed in the suggest list. On Carbon, this is how it works: # Open any Bugzilla bug in the Mylyn task editor # position the caret in the 'Add CC' field # press CTRL+Space # observe suggested values # start typing (slowly) 'dg' # notice that with each successive character the list is narrowed to fewer matching results # start typing backspace (slowly) to delete the characters in the text field # notice that the list is expanded to show additional matching results as the characters are deleted On Cocoa, typing in the text field after the suggest list is displayed causes the suggest list to go away.
|
2009-04-06 11:53:18
| 1,239,030,000 |
verified fixed
|
e640a91
| 1,241,740,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/fieldassist/ContentProposalAdapter.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/fieldassist/FieldAssistAPITest.java
|
Eclipse_Platform_UI
|
1,874 | 231,505 |
Bug 231505 [Forms] Invalid comment for TableWrapData
|
Build ID: I20080502-0100 Steps To Reproduce: 1. TableWrapData speaks about some unknown HTMLTableLayout. 2. For FILL comment speaks only about column, but FILL can be used also for vertical layout. More information:
|
2008-05-12 05:14:36
| 1,210,580,000 |
resolved fixed
|
8dcfb90
| 1,241,730,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/forms/widgets/TableWrapData.java bundles/org.eclipse.ui.forms/src/org/eclipse/ui/internal/forms/widgets/FormTextModel.java
|
Eclipse_Platform_UI
|
1,875 | 102,885 |
Bug 102885 [RCP] [PerspectiveBar] A large empty area on the top with a perspectivebar on the left
|
We define a new RCP Application using the hello RCP wizard. We define the method ApplicationWorkbenchWindowAdvisor>>preWindowOpen as follows: configurer.setShowCoolBar(false); configurer.setShowMenuBar(false); configurer.setShowPerspectiveBar(true); PlatformUI.getPreferenceStore().putValue(IWorkbenchPreferenceConstants.DOCK_PERSPECTIVE_BAR,IWorkbenchPreferenceConstants.LEFT); As result we have a large empty area on the top.
|
2005-07-06 12:33:56
| 1,120,670,000 |
verified fixed
|
1d0a9d7
| 1,241,730,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java
|
Eclipse_Platform_UI
|
1,876 | 265,157 |
Bug 265157 [EditorMgmt] Ctrl+PageDown in editor area should select next editor also when menu is open
| null |
2009-02-17 08:59:43
| 1,234,880,000 |
verified fixed
|
07b1d91
| 1,241,730,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/presentations/AbstractTableInformationControl.java
|
Eclipse_Platform_UI
|
1,877 | 237,124 |
Bug 237124 [Forms] Document how '&' is interpreted in Form Text
| null |
2008-06-13 13:47:40
| 1,213,380,000 |
resolved fixed
|
73fbd5b
| 1,241,720,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/forms/widgets/FormText.java
|
Eclipse_Platform_UI
|
1,878 | 269,210 |
Bug 269210 [About] High Contrast mode: "Installation Details" dialog improperly sized for tab sizes
|
In the high contrast mode on the "Installation Details" dialog tab selection arrows "<- ->" are outside of the default dialog size for some tabs. Tabs seem to occupy more space then expected by the dialog. To enable high contrast mode: - Open Control pannel - Open Accessibility Options - On the "Display" tab select "Use High Contrast" checkbox
|
2009-03-18 11:15:55
| 1,237,390,000 |
verified fixed
|
6d21acc
| 1,241,650,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/InstallationDialog.java
|
Eclipse_Platform_UI
|
1,879 | 264,152 |
Bug 264152 [EditorMgmt] missing tooltips in editor dropdown
|
Hello, I am working on very big C++ project (~20k files). In this project there are many files with the same name but in different locations. These file relate to classes which have the same name but different namespaces. This is very common in this project. For example: Namespace1::Module - src/Namespace1/Module.++ Namespace2::Module - src/Namespace2/Module.++ When opening many files in editor their names are shown if ">>" button is pressed (please see attached screenshot). There is no way to differentiate between files which have the same name, without pressing (choosing) them. Possible solution, if file is focused by cursor its location will be shown as well. This is very important feature for all colleagues in this project. I don't think it is relevant only for C++ but for Java as well (classes with the same name but different packages). I opened it on C++ component but it is probably not correct component. Could you please dispatch it to correct component. Best regards, Yevgeny
|
2009-02-09 06:16:28
| 1,234,180,000 |
resolved fixed
|
9ab8548
| 1,241,630,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/presentations/BasicPartList.java
|
Eclipse_Platform_UI
|
1,880 | 99,493 |
Bug 99493 [Preferences] Colors and Fonts preference page opens extremely wide due to Java properties file compare text font
|
I20050610-1757, GTK+ 2.6.4. Window > Preferences > General > Appearance > Colors and Fonts This preference page opens with all of the top-level items in the tree expanded. The width of the tree when it opens seems to be sized to be large enough to show the full text of the longest entry, namely the ridiculously long string: "Java properties file compare text font (defaults to Properties File Editor Text Font)" This makes the Preferences dialog resize to almost the entire width of my screen.
|
2005-06-11 00:11:51
| 1,118,460,000 |
verified fixed
|
27195b1
| 1,241,630,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/themes/ColorsAndFontsPreferencePage.java
|
Eclipse_Platform_UI
|
1,881 | 255,703 |
Bug 255703 [Forms] JavaDoc of SharedHeaderFormEditor broken
|
HEAD of today SharedHeaderFormEditor#createPageContainer javadoc is broken. Current doc: Overrides <code>super</code> to create a form in which to host the tab folder. This form will be responsible for managing
|
2008-11-18 14:55:15
| 1,227,040,000 |
resolved fixed
|
ea4715f
| 1,241,570,000 |
bundles/org.eclipse.ui.forms/src/org/eclipse/ui/forms/editor/SharedHeaderFormEditor.java
|
Eclipse_Platform_UI
|
1,882 | 275,075 |
Bug 275075 junit test failure for testInputIfHiddenBug69953
|
3.5 M7 + HEAD 05/05 The junit test testInputIfHiddenBug69953 fails. Top of trace is as follows: UI Test Suite org.eclipse.ui.tests.UiTestSuite org.eclipse.ui.tests.propertysheet.PropertySheetTestSuite org.eclipse.ui.tests.propertysheet.PropertySheetAuto testInputIfHiddenBug69953(org.eclipse.ui.tests.propertysheet.PropertySheetAuto) junit.framework.AssertionFailedError: Initial selection should be null in properties view at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNull(Assert.java:230) at org.eclipse.ui.tests.propertysheet.PropertySheetAuto.testInputIfHiddenBug69953(PropertySheetAuto.java:304) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
|
2009-05-05 17:47:48
| 1,241,560,000 |
verified fixed
|
e97c0b1
| 1,241,570,000 |
tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/propertysheet/PropertySheetAuto.java
|
Eclipse_Platform_UI
|
1,883 | 267,425 |
Bug 267425 [Perspectives] problem with outline view and min/max
| null |
2009-03-06 14:19:16
| 1,236,370,000 |
verified fixed
|
c74207f
| 1,241,550,000 |
bundles/org.eclipse.ui.views/src/org/eclipse/ui/views/properties/PropertySheet.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/part/PageBookView.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/api/IWorkbenchPageTest.java
|
Eclipse_Platform_UI
|
1,884 | 274,486 |
Bug 274486 [PerspectiveBar] [Perspectives] Perspective Bar - Dock On Left throws IndexOutOfBoundsException
|
Build ID: M20090211-1700 Steps To Reproduce: 1. Create a new Plug-in Project (Rich Client Application -> RCP Mail Template). 2. Add the following lines to ApplicationWorkbenchWindowAdvisor#preWindowOpen(): PlatformUI.getPreferenceStore().setValue(IWorkbenchPreferenceConstants.SHOW_OPEN_ON_PERSPECTIVE_BAR, false); configurer.setShowPerspectiveBar(true); 3. Run the application. 4. Right click on the perspective bar and choose Dock On Left => empty perspective bar and "java.lang.IndexOutOfBoundsException: inserting Test.perspective at 1" in stacktrace.
|
2009-04-30 05:54:14
| 1,241,090,000 |
verified fixed
|
e4a5aad
| 1,241,540,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PerspectiveSwitcher.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/internal/InternalTestSuite.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/internal/PerspectiveSwitcherTest.java
|
Eclipse_Platform_UI
|
1,885 | 181,836 |
Bug 181836 [Commands] CommandContributionException should use the StatusManager
|
20070407 CommandContributionException logs to the workbench log directly. I have an example that throws an InvocationTargetException that I catch and roll into an ExecutionException. It gets logged as such: catch (ExecutionException e) { WorkbenchPlugin.log("Failed to execute item " //$NON-NLS-1$ + getId(), e); Which made it hard for me to find. We should use the StatusManager here.
|
2007-04-10 16:25:08
| 1,176,240,000 |
verified fixed
|
18cb658
| 1,241,530,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/menus/CommandContributionItem.java
|
Eclipse_Platform_UI
|
1,886 | 274,862 |
Bug 274862 [Preferences] Cannot perform scrolling via keyboard in preference dialog
| null |
2009-05-04 13:42:06
| 1,241,460,000 |
verified fixed
|
898f052
| 1,241,530,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchMessages.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/FilteredPreferenceDialog.java
|
Eclipse_Platform_UI
|
1,887 | 271,326 |
Bug 271326 [BiDi] [Markers] BIDI3.5:HCG_Incorrect file path display in Problems view
| null |
2009-04-06 10:52:05
| 1,239,030,000 |
closed fixed
|
18fcdc0
| 1,241,470,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/MarkerPathField.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/views/markers/MarkerResourceField.java
|
Eclipse_Platform_UI
|
1,888 | 273,738 |
Bug 273738 [EditorMgmt] [BiDi] BIDI3.5:HCG_Incorrect text orientation of "Path" column of list view on "Swithch To Editor" page.
| null |
2009-04-26 15:03:41
| 1,240,770,000 |
closed fixed
|
91b4d80
| 1,241,460,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/WorkbenchEditorsDialog.java
|
Eclipse_Platform_UI
|
1,889 | 274,699 |
Bug 274699 [KeyBindings] Bug43597Test's testFontReset() leaks a font
| null |
2009-05-01 17:14:05
| 1,241,210,000 |
verified fixed
|
8c1abd8
| 1,241,450,000 |
tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/keys/Bug43597Test.java
|
Eclipse_Platform_UI
|
1,890 | 236,628 |
Bug 236628 [Viewers] [JFace] Excessive Memory Usage by Project Explorer because of styles
|
Build ID: I20080516-1333 Steps To Reproduce: Project Explorer creates duplicate identical strings for every entry in it and wastes few Megabytes of memory depending on the scenario. In the update method of NavigatorDecoratingLabelProvider extending DelegatingStyledCellLabelProvider the call to cell.setStyleRanges(newStyleRanges) results in duplicate strings for the same column. The duplicate strings are created in ViewerRow.setStyleRanges public void setStyleRanges(int columnIndex, StyleRange[] styleRanges) { getItem().setData(KEY_TEXT_LAYOUT + columnIndex, styleRanges); } More information:
|
2008-06-11 09:56:31
| 1,213,190,000 |
verified fixed
|
9d72537
| 1,241,040,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/ViewerRow.java
|
Eclipse_Platform_UI
|
1,891 | 270,822 |
Bug 270822 [Navigator] IPageLayout.ID_RES_NAV deprecated w/o an explanation
|
/** * The view id for the workbench's Resource Navigator standard component. * @deprecated */ public static String ID_RES_NAV = "org.eclipse.ui.views.ResourceNavigator"; //$NON-NLS-1$ Can we at least say why and what the alternative is? I assume this is because of the common navigator stuff?
|
2009-04-01 11:49:43
| 1,238,600,000 |
resolved fixed
|
ad54813
| 1,241,040,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IPageLayout.java
|
Eclipse_Platform_UI
|
1,892 | 270,457 |
Bug 270457 [Viewers] [regression] CheckBoxTreeViewer clears check state after collapseAll
|
Hi there :) In my RCP I've a CheckBoxTreeViewer that looses check states for invisible items. Turns out if a disable the collapseAll() call things go back to normal. So, in a tree like this: [x] root [x] sub a collapseAll expandAll will create this: [x] root [] sub Could still be my fault, feel free to have me try some workarounds or other tests that help you find the cause...
|
2009-03-30 10:25:34
| 1,238,420,000 |
verified fixed
|
437d45d
| 1,241,040,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/AbstractTreeViewer.java bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/CheckboxTreeViewer.java
|
Eclipse_Platform_UI
|
1,893 | 246,131 |
Bug 246131 [ViewMgmt] PagePartSelectionTracker does not call setPart() for View opend in another Perspective
|
Build ID: M20080221-1800 Steps To Reproduce: 1. Perspective1 has View1 opened. 2. We switched to Perspective2 that does not have View1 opened. 3. We add Postselection Listener to View1 using getSite().getPage().addPostSelectionListener(View1.VIEW_ID, m_selectionListenerForView1); 4. Our listener m_selectionListenerForView1 is not notified. More information: The Problem explanation. View1 is already opened but not in Perspective2. So constructor PagePartSelectionTracker could not find this Part with page.findView(partId); This causes that setPart() is not called. The second chance to call setPart() is in the IPartListener.partOpened(IWorkbenchPart). But this callback is never called because this View1 has been already created. (Our analysis shows that partOpened event is actually partCreated event. is it correct?) A possible solution could be to use partActivated(IWorkbenchPart part) callback and call setPart() (the same way as partOpened() does) if part has not been set yet.
|
2008-09-03 14:39:34
| 1,220,470,000 |
verified fixed
|
633eb92
| 1,241,040,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/PagePartSelectionTracker.java
|
Eclipse_Platform_UI
|
1,894 | 273,489 |
Bug 273489 [Mac] We should not nest sheets
| null |
2009-04-23 14:12:00
| 1,240,510,000 |
verified fixed
|
428064f
| 1,241,040,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/dialogs/PathVariableDialog.java
|
Eclipse_Platform_UI
|
1,895 | 274,075 |
Bug 274075 [Progress] ProgressDialog should not use SWT.SHEET
|
The progress dialog comes up as a SHEET right now and looks funny. Suggest it be a normal dialog instead.
|
2009-04-28 10:58:34
| 1,240,930,000 |
verified fixed
|
dbe239f
| 1,241,040,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/progress/BlockedJobsDialog.java
|
Eclipse_Platform_UI
|
1,896 | 270,769 |
Bug 270769 [JFace] [perfs] 1 failure while running Platform/UI performance tests
|
Verifying results for build I20090331-0901, I see one failure in Platform/UI performance tests: Policy.getComparatorTest Failure Method "Policy.getComparatorTest" not found junit.framework.AssertionFailedError: Method "Policy.getComparatorTest" not found at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:21) at junit.extensions.TestSetup.run(TestSetup.java:25) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3457) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3104) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2393) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2357) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2209) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:499) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:492) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138) at org.eclipse.test.UITestApplication.run(UITestApplication.java:60) at org.eclipse.test.UITestApplication.start(UITestApplication.java:210) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:556) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:511) at org.eclipse.equinox.launcher.Main.run(Main.java:1284) at org.eclipse.equinox.launcher.Main.main(Main.java:1260) at org.eclipse.core.launcher.Main.main(Main.java:30)
|
2009-04-01 09:44:13
| 1,238,590,000 |
verified fixed
|
a81fe0f
| 1,241,030,000 |
tests/org.eclipse.ui.tests.performance/src/org/eclipse/jface/tests/performance/CollatorPerformanceTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/jface/tests/performance/JFacePerformanceSuite.java
|
Eclipse_Platform_UI
|
1,897 | 273,697 |
Bug 273697 [WorkingSets] WorkbenchPage's setWorkingSets(IWorkingSet[]) has an impossible null conditional check
|
There is a null check in the beginning of the method that proceeds to make it non-null by assigning it to an empty array. Then on line 4984-5 it assigns it to another non-null result. On line 4996 there's a null check and add a listener to it or remove a listener. It seems that the null check shouldn't be necessary. Also, could it be possible that we are leaking the workingSetPropertyChangeListener listener?
|
2009-04-25 18:02:23
| 1,240,700,000 |
verified fixed
|
6d5bba5
| 1,241,010,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchPage.java
|
Eclipse_Platform_UI
|
1,898 | 273,706 |
Bug 273706 [WorkingSets] Changing workingset membership broken
| null |
2009-04-26 02:32:58
| 1,240,730,000 |
verified fixed
|
57e2846
| 1,241,010,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/AbstractWorkingSet.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/api/IWorkingSetTest.java
|
Eclipse_Platform_UI
|
1,899 | 274,236 |
Bug 274236 [CommonNavigator] Incorrect check for existence of item in contribution memory
|
The check in the NavigatorContentService.rememberContribution() should be containsKey(), not containsValue()
|
2009-04-29 02:24:25
| 1,240,990,000 |
resolved fixed
|
a43903e
| 1,241,010,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentService.java
|
Eclipse_Platform_UI
|
1,900 | 269,020 |
Bug 269020 [Viewers] ClassCastException in org.eclipse.ui.dialogs.PatternFilter
| null |
2009-03-17 11:57:13
| 1,237,310,000 |
verified fixed
|
1431c14
| 1,240,890,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/dialogs/PatternFilter.java
|
Eclipse_Platform_UI
|
1,901 | 244,284 |
Bug 244284 [Preferences] Preference page help is not shown when tree is selected
|
In the Preferences dialog, some pages don't have a help context associated with them. On these pages, the behavior of the help button/F1 key is inconsistent: the help tray is shown if a widget on the respective page is shown, but _not_ if the tree item is selected. Steps to reproduce the problem: 1. Open the Preferences dialog 2. Select the tree item "Tasks" 3. Press F1 (or press the help button in the lower left corner) -> no help is shown 4. Select any widget on the Tasks page 5. Press F1 -> the help tray is shown Root cause analysis: As far as I could find out, the reason for this inconsistent behavior lies in the method org.eclipse.jface.preference.PreferencePage.performHelp(), which is triggered in step 3. This method assumes, that the preference page's top level control has a help listener attached to it. This is true for many other preference pages [see for example org.eclipse.jdt.internal.ui.preferences.JavaBasePreferencePage.createControl(Composite)], but not for the Task preference page [sorry, couldn't find its source code]. So why does step 5 still show the help tray? That step triggers org.eclipse.jface.dialogs.TrayDialog.helpPressed() which searches the widget hierarchy for a help listener, and will always find one on the dialog level. I suggest to chage PreferencePage.performHelp() so that it behaves like TrayDialog.helpPressed(), for example by copying the recursive search for help handlers.
|
2008-08-15 08:04:30
| 1,218,800,000 |
verified fixed
|
491760d
| 1,240,890,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/preference/PreferenceDialog.java
|
Eclipse_Platform_UI
|
1,902 | 249,502 |
Bug 249502 [Coolbar] init is called during dispose of a IWorkbenchWindowPulldownDelegate2
|
Build ID: M20080911-1700 Steps To Reproduce: 1. contribute a IWorkbenchWindowPulldownDelegate2 with some options 2. Open the workbench, and open a new workbench window (Window -> new Window) 3. You will now hit a break point in the init method of the IWorkbenchWindowPulldownDelegate2. 4. Select the pulldown, and select some option (This seems to be important, if I don't drop the menu and use something, it doesn't happen ... causes the menu to be created maybe?) 5. close the window -> dispose is called -> init is called again! This is bad since we have code for registering listeners etc during the init method. In this case we have removed our listeners in the dispose, but then re-register them before the window is actually closed. More information: Here's a trace of the shut down leading to the re-initialization of the delegate. Thread [main] (Suspended (breakpoint at line 67 in ChangeLanguageToolbarAction)) ChangeLanguageToolbarAction.init(IWorkbenchWindow) line: 67 WWinPluginPulldown(WWinPluginAction).initDelegate() line: 189 WWinPluginPulldown(PluginAction).createDelegate() line: 125 WWinPluginPulldown(PluginAction).getMenuCreator() line: 380 PluginActionCoolBarContributionItem(ActionContributionItem).handleWidgetDispose(Event) line: 471 ActionContributionItem.access$1(ActionContributionItem, Event) line: 465 ActionContributionItem$6.handleEvent(Event) line: 446 EventTable.sendEvent(Event) line: 84 ToolItem(Widget).sendEvent(Event) line: 1003 ToolItem(Widget).sendEvent(int, Event, boolean) line: 1027 ToolItem(Widget).sendEvent(int) line: 1008 ToolItem(Widget).release(boolean) line: 804 ToolBar.releaseChildren(boolean) line: 710 ToolBar(Widget).release(boolean) line: 807 CoolBar(Composite).releaseChildren(boolean) line: 755 CoolBar.releaseChildren(boolean) line: 713 CoolBar(Widget).release(boolean) line: 807 Composite.releaseChildren(boolean) line: 755 Composite(Widget).release(boolean) line: 807 CBanner(Composite).releaseChildren(boolean) line: 755 CBanner(Widget).release(boolean) line: 807 Shell(Composite).releaseChildren(boolean) line: 755 Shell(Canvas).releaseChildren(boolean) line: 174 Shell(Decorations).releaseChildren(boolean) line: 771 Shell.releaseChildren(boolean) line: 1211 Shell(Widget).release(boolean) line: 807 Shell(Widget).dispose() line: 441 Shell(Decorations).dispose() line: 446 Shell.dispose() line: 674 WorkbenchWindow(Window).close() line: 335 WorkbenchWindow(ApplicationWindow).close() line: 306 WorkbenchWindow.hardClose() line: 1624 WorkbenchWindow.busyClose() line: 722 WorkbenchWindow.access$0(WorkbenchWindow) line: 698 WorkbenchWindow$3.run() line: 814 BusyIndicator.showWhile(Display, Runnable) line: 70 WorkbenchWindow.close() line: 812 WorkbenchWindow(Window).handleShellCloseEvent() line: 741 Window$3.shellClosed(ShellEvent) line: 687 TypedListener.handleEvent(Event) line: 92 EventTable.sendEvent(Event) line: 84 Shell(Widget).sendEvent(Event) line: 1003 Shell(Widget).sendEvent(int, Event, boolean) line: 1027 Shell(Widget).sendEvent(int, Event) line: 1012 Shell(Decorations).closeWidget() line: 307 Shell(Decorations).WM_CLOSE(int, int) line: 1643 Shell(Control).windowProc(int, int, int, int) line: 3789 Shell(Canvas).windowProc(int, int, int, int) line: 337 Shell(Decorations).windowProc(int, int, int, int) line: 1576 Shell.windowProc(int, int, int, int) line: 1937 Display.windowProc(int, int, int, int) line: 4528 OS.DefWindowProcW(int, int, int, int) line: not available [native method] OS.DefWindowProc(int, int, int, int) line: 2366 Shell.callWindowProc(int, int, int, int) line: 477 Shell(Control).windowProc(int, int, int, int) line: 3877 Shell(Canvas).windowProc(int, int, int, int) line: 337 Shell(Decorations).windowProc(int, int, int, int) line: 1576 Shell.windowProc(int, int, int, int) line: 1937 Display.windowProc(int, int, int, int) line: 4528 OS.DefWindowProcW(int, int, int, int) line: not available [native method] OS.DefWindowProc(int, int, int, int) line: 2366 Shell.callWindowProc(int, int, int, int) line: 477 Shell(Control).windowProc(int, int, int, int) line: 3877 Shell(Canvas).windowProc(int, int, int, int) line: 337 Shell(Decorations).windowProc(int, int, int, int) line: 1576 Shell.windowProc(int, int, int, int) line: 1937 Display.windowProc(int, int, int, int) line: 4528 OS.DispatchMessageW(MSG) line: not available [native method] OS.DispatchMessage(MSG) line: 2371 Display.readAndDispatch() line: 3420 Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2382 Workbench.runUI() line: 2346 Workbench.access$4(Workbench) line: 2198 Workbench$5.run() line: 493 Realm.runWithDefault(Realm, Runnable) line: 288 Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 488 PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149 IDEApplication.start(IApplicationContext) line: 113 EclipseAppHandle.run(Object) line: 193 EclipseAppLauncher.runApplication(Object) line: 110 EclipseAppLauncher.start(Object) line: 79 EclipseStarter.run(Object) line: 386 EclipseStarter.run(String[], Runnable) line: 179 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 59 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 39 Method.invoke(Object, Object...) line: 612 Main.invokeFramework(String[], URL[]) line: 549 Main.basicRun(String[]) line: 504 Main.run(String[]) line: 1236 Main.main(String[]) line: 1212
|
2008-10-02 10:57:51
| 1,222,960,000 |
verified fixed
|
5960659
| 1,240,880,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/WorkbenchWindow.java
|
Eclipse_Platform_UI
|
1,903 | 224,341 |
Bug 224341 [ErrorHandling] SafeRunnnableDialog shows only "Reason" as message.
|
In case of an error the SafeRunner.class will open a SafeRunnnableDialg which (often) only prints String "Reason" and no further information. The reason are a failure in the dialog and and wrong properties-file entry. At end [Line 74] of constructor SafeRunnableDialog(IStatus status) of org.eclipse.jface.util.SafeRunnableDialog.class you will see following code: this.message = JFaceResources.format(JFaceResources .getString("SafeRunnableDialog_reason"), new Object[] { //$NON-NLS-1$ status.getMessage(), reason }); 1.) JFaceResources.format(String key, Object[] args) expects as first parameter a key in a resource bundle, but is already getting the localized value to this key --> leading to MissingResourceException 2.) the properties-value of key "SafeRunnableDialog_reason" in org.eclipse.jface.message.properties = "Reason", but should be "{0} Reason: {1}"
|
2008-03-27 07:57:41
| 1,206,620,000 |
resolved fixed
|
bb2a785
| 1,240,860,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/util/SafeRunnableDialog.java
|
Eclipse_Platform_UI
|
1,904 | 154,730 |
Bug 154730 [Presentations] Editor PresentationStack never gets disposed when IWorkbenchConfigurer.setSaveAndRestore(true)
|
Typically (with one workbench window,etc) a single stack is created for editors. But when you call IWorkbenchConfigurer.setSaveAndRestore(true), another editor stack is created (presumably to make it easier to restore the state). This new editor stack seems to become the current editor stack. The first editor stack that was created sticks around and is never disposed, even on shutdown. This can be easily demonstrated by simply putting some sysout statements in the creation and disposal of a presentation (two creations, one dispose).
|
2006-08-22 14:23:54
| 1,156,270,000 |
verified fixed
|
fded5c6
| 1,240,860,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/EditorSashContainer.java
|
Eclipse_Platform_UI
|
1,905 | 261,622 |
Bug 261622 [ActivityMgmt] View shortcut is displayed in the Show View's sub-menu if the activity was disabled
|
I used Eclipse 3.4.1 Build id: M20080911-1700 The activity was defined in the plug-in. <extension point="org.eclipse.ui.activities"> <category id="my.activity.ui.activities" name="Ant for test" description="Ant for test"/> <activity id="my.activity.ui.activity" name="Ant for test" wescription="Ant for test"/> <categoryActivityBinding activityId="my.activity.ui.activity" categoryId="my.activity.ui.activities"/> <activityPatternBinding activityId="my.activity.ui.activity" pattern="org\.eclipse\.ant\.ui/.*"/> </extension> View shortcut "Ant" is displayed in the Window > Show View's sub-menu if the activity was disabled. This case, "Ant" is not displayed in the Show View dialog.
|
2009-01-20 07:08:23
| 1,232,450,000 |
verified fixed
|
0ab7aa1
| 1,240,860,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/ShowViewMenu.java
|
Eclipse_Platform_UI
|
1,906 | 267,791 |
Bug 267791 [Import/Export] Layout issue on the Import Projects page
|
I20090309-1800 Just take a look at the screen shot. Sorry if this is a dupe, but I couldn't fine one.
|
2009-03-10 05:13:28
| 1,236,680,000 |
verified fixed
|
9c2add1
| 1,240,820,000 |
bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/wizards/datatransfer/WizardProjectsImportPage.java
|
Eclipse_Platform_UI
|
1,907 | 273,752 |
Bug 273752 syncExec in org.eclipse.ui.internal.navigator.NavigatorContentService.getSourceOfContribution(Object) causes deadlock in test suite
|
The Platform UI test suite does not complete anymore - it hangs in the org.eclipse.ui.tests.dynamicplugins.EditorTests.testEditorClosure() test case. The hang is in the following code: final boolean[] flag = new boolean[] { false }; FrameworkListener listener = new FrameworkListener() { public void frameworkEvent(FrameworkEvent event) { if (event.getType() == FrameworkEvent.PACKAGES_REFRESHED) synchronized (flag) { flag[0] = true; flag.notifyAll(); } } }; context.addFrameworkListener(listener); packageAdmin.refreshPackages(bundles); synchronized (flag) { while (!flag[0]) { try { flag.wait(); } catch (InterruptedException e) { } } } The flag[0] is never set to true, which probably means that the PACKAGES_REFRESHED event is not fired.
|
2009-04-26 19:12:02
| 1,240,790,000 |
resolved fixed
|
31ec5f3
| 1,240,790,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentService.java
|
Eclipse_Platform_UI
|
1,908 | 273,667 |
Bug 273667 [About] Installation Details dialog is not remembering size
| null |
2009-04-25 00:16:45
| 1,240,630,000 |
verified fixed
|
7bbf881
| 1,240,630,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/about/InstallationDialog.java
|
Eclipse_Platform_UI
|
1,909 | 257,167 |
Bug 257167 Shutdown takes too long
|
I20081127-0900 When I shut down my development workspace (most of the SDK from CVS) after working a few hours with it, I always get a progress dialog that reports "Saving Workspace." for a long time. After a day, it needs about a minute to finish. After working for more than a day, I sometimes have to wait for 3-5 minutes until Eclipse is finally closed. During the delay, I notice heavy disk activity. Stacktraces look like the one below (always in BucketTree.internalAccept(..) inside HistoryStore2.clean(..)). YourKit revealed that most of the time is burnt in - Bucket.load(String, File, boolean) > FileInputStream(File), and in - File.listFiles(). I don't know exactly why this cleanup takes so long, but I would expect that after the "Workspace save interval" from Preferences > General > Workspace (5min), nothing should have to be done any more on shutdown (otherwise, we would also lose that data when the workspace crashes). A problem could be this commented line from HistoryStore2.addState(..): // currentBucket.save(); "ModalContext" prio=6 tid=0x28ee2800 nid=0x964 runnable [0x2a0cf000..0x2a0cfb94] java.lang.Thread.State: RUNNABLE at java.io.WinNTFileSystem.$$YJP$$list(Native Method) at java.io.WinNTFileSystem.list(WinNTFileSystem.java) at java.io.File.list(File.java:973) at java.io.File.listFiles(File.java:1051) at org.eclipse.core.internal.localstore.BucketTree.internalAccept(BucketTree.java:102) at org.eclipse.core.internal.localstore.BucketTree.internalAccept(BucketTree.java:107) at org.eclipse.core.internal.localstore.BucketTree.internalAccept(BucketTree.java:107) at org.eclipse.core.internal.localstore.BucketTree.internalAccept(BucketTree.java:107) at org.eclipse.core.internal.localstore.BucketTree.internalAccept(BucketTree.java:107) at org.eclipse.core.internal.localstore.BucketTree.internalAccept(BucketTree.java:107) at org.eclipse.core.internal.localstore.BucketTree.accept(BucketTree.java:71) at org.eclipse.core.internal.localstore.HistoryStore2.clean(HistoryStore2.java:155) - locked <0x0eb9b000> (a org.eclipse.core.internal.localstore.HistoryStore2) at org.eclipse.core.internal.resources.SaveManager.save(SaveManager.java:1012) at org.eclipse.core.internal.resources.Workspace.save(Workspace.java:1827) at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor$3.run(IDEWorkbenchAdvisor.java:388) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
|
2008-12-02 05:11:54
| 1,228,210,000 |
resolved fixed
|
cda8930
| 1,240,610,000 |
bundles/org.eclipse.ui.ide.application/src/org/eclipse/ui/internal/ide/application/IDEWorkbenchAdvisor.java bundles/org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/IDEWorkbenchMessages.java
|
Eclipse_Platform_UI
|
1,910 | 270,952 |
Bug 270952 [CommonNavigator] Eclipse RCP raises nullPointerException in makeSmallString for Project Explorer
| null |
2009-04-02 08:18:55
| 1,238,670,000 |
resolved fixed
|
e1e81e6
| 1,240,600,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/internal/navigator/NavigatorContentServiceLabelProvider.java
|
Eclipse_Platform_UI
|
1,911 | 272,763 |
Bug 272763 [CommonNavigator] Can't drag objects from Data Source Explorer
|
Build ID: I20090313-0100 Steps To Reproduce: 1.Open the DSE View 2.connect a profile (such as one to Derby) 3.Click on an item in the database tree and attempt to drag it. In previous releases of Eclipse, the drag icon would appear and objects could be dropped onto another view with a dropListener. Now, nothing happens. More information: I am running with DTP 1.7(dtp-sdk-1.7.0M7-200904030500), Eclipse 3.5 (eclipse-SDK-3.5M6-win32), EMF 2.5 (emf-xsd-SDK-2.5.0M6), GEF 3.5 (GEF-runtime-3.5.0M6). There are changes in the CommonDragAdapter (bugzilla 264323) which may effect this.
|
2009-04-17 17:10:14
| 1,240,000,000 |
verified fixed
|
d36db75
| 1,240,600,000 |
bundles/org.eclipse.ui.navigator/src/org/eclipse/ui/navigator/CommonDragAdapter.java
|
Eclipse_Platform_UI
|
1,912 | 239,518 |
Bug 239518 [Contributions] Fix up TextActionHandler's handling of Delete to use Text.insert
| null |
2008-07-03 16:38:30
| 1,215,120,000 |
verified fixed
|
11e419a
| 1,240,600,000 |
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/actions/TextActionHandler.java
|
Eclipse_Platform_UI
|
1,913 | 219,536 |
Bug 219536 [Contributions] [Doc] update API docs re IMenuService.populateContributionManager doesn't populate child(nested) contribution items on form toolbar
|
Build ID: M20071023-1652 Steps To Reproduce: 1.Create RCP plugin (possibly any 3.3 plugin) 2.Create Editor (extends EditorPart) 3.Put there org.eclipse.ui.forms.widgets.Form 4.Make org.eclipse.ui.menu 5.Add to org.eclipse.ui.menu menuContribution with locationURI: toolbar:anything 6.Add on this menuContribution "toolbar" item 7.Add on the toolbar the commands (All commands are existed and all icons, labels etc are OK) 7.in your Editor's createPartControl do populating: IMenuService ms = (IMenuService) this.getSite().getService( IMenuService.class); ms.populateContributionManager((ToolBarManager)form.getToolBarManager(), "toolbar:anything"); 8.Run and see that actually only toolbar item was added is useless container toolbar item. More information: This issue can be workarounded by creating the toolbar buttons directly on the menuContribution avoiding using intermediate toolbar parent item.
|
2008-02-19 21:47:00
| 1,203,480,000 |
verified fixed
|
cdd57f3
| 1,240,600,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/menus/IMenuService.java
|
Eclipse_Platform_UI
|
1,914 | 196,691 |
Bug 196691 Inncorrect Class Name in Javadoc
|
The class comments for org.eclipse.ui.part.MultiPageEditorPart contains the following sentence: "The contributor must be a subclass of <code>AbstractMultiPageEditorActionBarContributor</code>." I was not able to find the class AbstractMultiPageEditorActionBarContributor, but I was able to find org.eclipse.ui.part.MultiPageEditorActionBarContributor which is an abstract class. Should the word "Abstract" be removed from the comments?
|
2007-07-16 13:42:45
| 1,184,610,000 |
verified fixed
|
cf5c924
| 1,240,600,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/part/MultiPageEditorPart.java
|
Eclipse_Platform_UI
|
1,915 | 155,008 |
Bug 155008 [Contributions] Improve Javadoc for IActionBars.updateActionBars
|
R3.2 The Javadoc for IActionBars.updateActionBars is not accurate: it says: * Clients who add or remove items from the menu, tool bar, or status line * managers should call this method to propagated the changes throughout * the workbench. However, the method must also be called if a global action (which is already in the menu) is retargeted using: IActionBars.setGlobalActionHandler
|
2006-08-24 05:22:35
| 1,156,410,000 |
verified fixed
|
ff15528
| 1,240,600,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/IActionBars.java
|
Eclipse_Platform_UI
|
1,916 | 268,819 |
Bug 268819 [WorkbenchLauncher] 'Workspaces' preference page's 'Remove' button should enable/disable itself more intelligently
|
1. Window > Preferences > General > Startup > Workspaces 2. Select a workspace. 3. Click 'Remove'. 4. There is now no selection, but the 'Remove' button is still enabled.
|
2009-03-16 11:45:50
| 1,237,220,000 |
verified fixed
|
fcb2740
| 1,240,590,000 |
bundles/org.eclipse.ui.ide.application/src/org/eclipse/ui/internal/ide/application/dialogs/RecentWorkspacesPreferencePage.java
|
Eclipse_Platform_UI
|
1,917 | 269,264 |
Bug 269264 [Viewers] TableViewer.remove doesn't post selection change
|
When using org.eclipse.jface.viewers.TableViewer.remove(Object[]) and the remove includes the current selection, the item is deleted and the selection goes away. But no selection change event is fired (where at the very least it should be an empty IStructuredSelection). PW
|
2009-03-18 15:03:48
| 1,237,400,000 |
verified fixed
|
74415bd
| 1,240,590,000 |
bundles/org.eclipse.jface/src/org/eclipse/jface/viewers/TableViewer.java
|
Eclipse_Platform_UI
|
1,918 | 258,253 |
Bug 258253 [Commands] [performance] Activate 30 text editor test is slower than 3.4
|
Looking at I20081209-0100 performance results, it looks like the scenario: org.eclipse.jdt.text.tests.performance.ActivateTextEditorTest#testActivateEditor() got a regression since 3.4. The numbers for this test are really stable for all test machines: Win XP Sun 1.5.0_10 (2 x 3.00GHz - 3GB RAM) Builds Activate 30 text editors I20081118-1720 -17.0% I20081119-1600 -17.0% N20081120-2000 -17.0% I20081125-0840 -17.0% N20081127-2000 -17.0% N20081129-2000 -17.0% I20081202-1812 -17.0% N20081204-2000 -18.0% N20081206-2000 -17.0% I20081209-0100 -17.0% SLED 10 Sun 1.5.0_10 (2 x 3.00GHz - 3GB RAM) Builds Activate 30 text editors I20081118-1720 -18.0% I20081119-1600 -19.0% N20081120-2000 -20.0% I20081125-0840 -18.0% N20081127-2000 -17.0% N20081129-2000 -17.0% I20081202-1812 -17.0% N20081204-2000 -20.0% N20081206-2000 -25.0% I20081208-0921 -20.0% I20081209-0100 -17.0% RHEL 5.0 Sun 6.0_04 (2 x 3.00GHz - 3GB RAM) Builds Activate 30 text editors I20081118-1720 -16.0% I20081119-1600 -15.0% N20081120-2000 -16.0% I20081125-0840 -13.0% N20081127-2000 -13.0% N20081129-2000 -14.0% I20081202-1812 -23.0% N20081204-2000 -27.0% N20081206-2000 -28.0% I20081208-0921 -27.0% I20081209-0100 -27.0%
|
2008-12-10 05:02:54
| 1,228,900,000 |
verified fixed
|
f9928f1
| 1,240,590,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/services/WorkbenchSourceProvider.java
|
Eclipse_Platform_UI
|
1,919 | 249,851 |
Bug 249851 [QuickAccess] Quick access doesn't open perspective if all perspectives are closed
|
I20080918-0100 1. Window > Close All Perspectives 2. Ctrl+3 > Resource 3. Hit 'Enter'. 4. Nothing happens. :( In QuickAccessDialog's handleElementSelected(String, Object) method, there's a null check for the active workbench page. Unfortunately, when there are no perspectives open, we have no active workbench page. Thus, the method just returns and nothing happens.
|
2008-10-06 14:28:52
| 1,223,320,000 |
verified fixed
|
f259e9a
| 1,240,590,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/quickaccess/PerspectiveElement.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/quickaccess/QuickAccessDialog.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/quickaccess/ViewProvider.java
|
Eclipse_Platform_UI
|
1,920 | 211,433 |
Bug 211433 [KeyBindings] Changing key binding broken (ends up in wrong context)
|
3.3 and I20071127-0800. 1. change the key binding of the 'Content Assist' 2. open a dialog that offers field assist, e.g. the Find/Replace dialog when in regex mode. 3. press the chosen key binding ==> does not work BUT: the hovering over the light bulb shows the correct key binding.
|
2007-11-29 05:53:13
| 1,196,330,000 |
verified fixed
|
8ffd765
| 1,240,590,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/NewKeysPreferencePage.java bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/model/KeyController.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/keys/BindingPersistenceTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/keys/KeysPreferenceModelTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/keys/KeysTestSuite.java
|
Eclipse_Platform_UI
|
1,921 | 202,057 |
Bug 202057 [RCP] [Workbench] NullPointerException if workbench.close() is called in preStartup of the WorkbenchAdvisor
|
Build ID: I20070621-1340 Steps To Reproduce: 1. Overwrite the preStartup() method in XXXWorkbenchAdvisor with public void preStartup() { getWorkbenchConfigurer().getWorkbench().close(); } 2. Start the application. 3. A NullPointerException occurs. It should be possible to close or restart the application even in the preStartup state without NPE's. More information: Exception in thread "Thread-2" java.lang.NullPointerException: The parent handler service cannot be null at org.eclipse.ui.internal.handlers.SlaveHandlerService.<init>(SlaveHandlerService.java:99) at org.eclipse.ui.internal.WorkbenchWindow.initializeDefaultServices(WorkbenchWindow.java:3825) at org.eclipse.ui.internal.WorkbenchWindow.<init>(WorkbenchWindow.java:360) at org.eclipse.ui.internal.Workbench.newWorkbenchWindow(Workbench.java:1725) at org.eclipse.ui.internal.Workbench.access$14(Workbench.java:1724) at org.eclipse.ui.internal.Workbench$18.runWithException(Workbench.java:1001) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3212) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2956) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:797) at org.eclipse.ui.internal.Workbench$25.runWithException(Workbench.java:1342) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3212) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2956) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2309) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.examples.rcp.mail.Application.start(Application.java:26) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:504) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:443) at org.eclipse.equinox.launcher.Main.run(Main.java:1169) at org.eclipse.equinox.launcher.Main.main(Main.java:1144)
|
2007-09-03 05:10:18
| 1,188,810,000 |
verified fixed
|
b2df11f
| 1,240,580,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/Workbench.java
|
Eclipse_Platform_UI
|
1,922 | 255,576 |
Bug 255576 [Model] No longer able to create a WorkbenchLabelProvider in a non-UI thread.
|
Build ID: M20080911-1700 Steps To Reproduce: 1. Create a WorkbenchLabelProvider in a non-UI thread. 2. Observe a NPE when JFaceResources.getResources() attempts to access the Display associated with the current thread. 3. Notice that Javadoc on JFaceResources.getResources() states that the method must be called from UI thread. More information: The following line was added to the WorkbenchLabelProvider constructor (line 77) in 3.4: this.resourceManager = new LocalResourceManager(JFaceResources.getResources()); The method JFaceResources.getResources() may only be called from a UI thread since it attempts to find the Display associated with the current thread.
|
2008-11-17 17:25:01
| 1,226,960,000 |
verified fixed
|
37c5578
| 1,240,580,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/model/WorkbenchLabelProvider.java
|
Eclipse_Platform_UI
|
1,923 | 258,177 |
Bug 258177 [Decorators] DecorationScheduler calling wakeUp()/schedule() on decorationJob too often
| null |
2008-12-09 15:43:54
| 1,228,860,000 |
verified fixed
|
04c373c
| 1,240,580,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/decorators/DecorationScheduler.java
|
Eclipse_Platform_UI
|
1,924 | 222,556 |
Bug 222556 Write a performance suite for DecoratingStyledCellLabelProvider
|
There is a suspicion that DecoratingStyledCellLabelProvider is much slower than DecoratingLabelProvider. We need a suite that tests scrolling a viewer with a DecoratingStyledCellLabelProvider both with and without colouring again one using a DecoratingLabelProvider.
|
2008-03-13 08:43:36
| 1,205,410,000 |
verified fixed
|
012534a
| 1,240,510,000 |
tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/LabelProviderTest.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/LabelProviderTestSuite.java tests/org.eclipse.ui.tests.performance/src/org/eclipse/ui/tests/performance/UIPerformanceTestSuite.java
|
Eclipse_Platform_UI
|
1,925 | 241,877 |
Bug 241877 [Preferences] PreferencesUtil.createPreferenceDialogOn should place focus on the preference page
|
Build ID: 3.4.0.I20080521-2000 Steps To Reproduce: Use PreferencesUtil.createPreferenceDialogOn to open a specific preference page. When the preferences dialog opens, focus is in the filter text control ("type filter text"). Issue: Focus should be on the preference page so a blind user using screen reader knows where they are and what to do next. More information:
|
2008-07-23 16:08:03
| 1,216,840,000 |
verified fixed
|
1e357e8
| 1,240,510,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/dialogs/WorkbenchPreferenceDialog.java
|
Eclipse_Platform_UI
|
1,926 | 248,943 |
Bug 248943 [KeyBindings] [RCP] NullpointerException when entering text after the rcp is restarted
|
Build ID: M20080911-1700 Steps To Reproduce: 1. Build an rcp and start the workbench in a loop. For instance, like this : public Object run(Object args) throws Exception { Display display = PlatformUI.createDisplay(); try { while (true) { int returnCode = PlatformUI.createAndRunWorkbench(display, new ApplicationWorkbenchAdvisor()); if (returnCode == PlatformUI.RETURN_RESTART) { return IPlatformRunnable.EXIT_RESTART; } //return IPlatformRunnable.EXIT_OK; } } finally { display.dispose(); } } 2. Create a dialog box with a Text field to be able to enter some text and attach it to an action (menu). 3. Start the rcp. 4. Enter text in the dialog and close it. 5. Stop the RCP with the close box. 6. When the rcp restarts for the second time (since the workbench is created and run in a loop), show the dialog again. 7. Try to enter text and a nullPointerException occurs in class WorkbenchKeyboard(Workbench) on the last line of the following method : private boolean isPartialMatch(KeySequence keySequence) { if (bindingService == null) { bindingService = (IBindingService) workbench .getService(IBindingService.class); } return bindingService.isPartialMatch(keySequence); } More information: The bug does not occur if you don't open the dialog box the first time. The bug does not occur if the display is disposed and created again every time the workbench is created and run. But in this case, I lose the Image Registry.
|
2008-09-29 10:18:24
| 1,222,700,000 |
verified fixed
|
96e0e21
| 1,240,510,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/BindingService.java
|
Eclipse_Platform_UI
|
1,927 | 230,449 |
Bug 230449 [KeyBindings] NPE in KPP when deleting conflicting keybinding
|
Reproduced with I20080502-0100 and I20080502-0100 base + HEAD code in runtime workspace. 1. Window > Preferences > General > Keys 2. 'Activate Editor' should be bound to F12 (this should be the second entry). 3. Select 'About' (this should be the first entry). 4. Click the 'Binding' text field, hit 'F12'. 5. The conflict table is updated showing a conflict between 'About' and 'Activate Editor'. 6. Hit Ctrl+C, the keybinding is now > F12, Ctrl+C 7. Use the backspace to clear the keybinding. 8. 'About' has no keybinding, but so does 'Activate Editor' (!). 9. NPE is logged in .log. java.lang.NullPointerException at org.eclipse.ui.internal.keys.model.KeyController.updateTrigger(KeyController.java:352) at org.eclipse.ui.internal.keys.model.KeyController$4.propertyChange(KeyController.java:228) at org.eclipse.ui.internal.keys.model.KeyController.firePropertyChange(KeyController.java:100) at org.eclipse.ui.internal.keys.model.BindingElement.setTrigger(BindingElement.java:113) at org.eclipse.ui.internal.keys.NewKeysPreferencePage$5.propertyChange(NewKeysPreferencePage.java:698) at org.eclipse.jface.bindings.keys.KeySequenceText.firePropertyChangeEvent(KeySequenceText.java:736) at org.eclipse.jface.bindings.keys.KeySequenceText.setKeySequence(KeySequenceText.java:929) at org.eclipse.jface.bindings.keys.KeySequenceText$KeyTrapListener.handleEvent(KeySequenceText.java:129) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
|
2008-05-06 14:09:20
| 1,210,100,000 |
verified fixed
|
0669ae0
| 1,240,510,000 |
bundles/org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/internal/keys/model/KeyController.java
|
Eclipse_Platform_UI
|
1,928 | 273,147 |
Bug 273147 [Build] Report build problems as ERROR severity
|
Currently the BuildManager reports problems with severity of WARNING. Warnings are no longer surfaced in the UI, so we should increase this severity to ERROR.
|
2009-04-21 18:08:37
| 1,240,350,000 |
resolved fixed
|
a0bfb92
| 1,240,510,000 |
bundles/org.eclipse.ui.ide/extensions/org/eclipse/ui/actions/GlobalBuildAction.java
|
Eclipse_Platform_UI
|
1,929 | 223,843 |
Bug 223843 [RCP] Session tests to confirm Advisor threading
|
We have tests in our RCP suite that verify that all advisor methods are being called from the UI thread. This only checks the clean startup case, however. Restoration should be confirmed as well. We need a session test suite that verifies everything our RCP test does with an existing workspace.
|
2008-03-25 10:52:34
| 1,206,460,000 |
verified fixed
|
7dfc047
| 1,240,500,000 |
tests/org.eclipse.ui.tests.harness/src/org/eclipse/ui/tests/harness/util/RCPTestWorkbenchAdvisor.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/PlatformUITest.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/WorkbenchConfigurerTest.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/WorkbenchWindowConfigurerTest.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/util/OpenWorkbenchIntervalMonitor.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/util/RCPTestWorkbenchAdvisor.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/util/RestoreWorkbenchIntervalMonitor.java tests/org.eclipse.ui.tests.rcp/Eclipse RCP Tests/org/eclipse/ui/tests/rcp/util/WorkbenchAdvisorObserver.java tests/org.eclipse.ui.tests/Eclipse JFace Tests/org/eclipse/ui/tests/RCPSessionApplication.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/session/RestoreSessionTest.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/session/SessionTests.java tests/org.eclipse.ui.tests/Eclipse UI Tests/org/eclipse/ui/tests/session/WorkbenchSessionTest.java
|
Eclipse_Platform_UI
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.