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 |
|---|---|---|---|---|---|---|---|---|---|---|
935
| 260,362
|
Bug 260362 NPE when using content assist in compare
|
HEAD. I get an NPE when doing content assist in the Java compare viewer. It works if the input is the CU but if I narrow down to an element it breaks. When I do Ctrl+Space at the beginning of the file (when the CU is the !ENTRY org.eclipse.ui 4 4 2009-01-08 10:50:41.420 !MESSAGE "Content Assist" did not complete normally. Please see the log for more information. !ENTRY org.eclipse.ui 4 0 2009-01-08 10:50:41.420 !MESSAGE java.lang.NullPointerException !STACK 0 java.lang.NullPointerException at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:177) at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:471) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:823) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:879) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:570) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:511) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:126) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1190) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1358) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4019) at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:346) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3912) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4584) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2295) at org.eclipse.swt.internal.BidiUtil.windowProc(BidiUtil.java:639) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2392) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3468) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:333) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490) 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:193) 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:366) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:550) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:505) at org.eclipse.equinox.launcher.Main.run(Main.java:1237) at org.eclipse.equinox.launcher.Main.main(Main.java:1213)
|
2009-01-08 04:55:15
| 1,231,410,000
|
verified fixed
|
15de8db
| 1,231,500,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/compare/JavaMergeViewer.java
|
JDT
|
936
| 256,867
|
Bug 256867 [package explorer] Assign Working Sets dialog: checking a working set should show it
|
I20081126-000 When choosing to see all working sets in the 'Working Set Assignements' dialog and checking one of the yet hidden working sets it should make the working set(s) visible when clicking 'OK'.
|
2008-11-28 05:16:33
| 1,227,870,000
|
resolved fixed
|
45a66bf
| 1,231,340,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/ConfigureWorkingSetAssignementAction.java
|
JDT
|
937
| 233,559
|
Bug 233559 [implementation] NPE in DocumentAdapter
|
Closed an editor right after startup. Will try to reproduce... java.lang.NullPointerException at org.eclipse.jdt.int.ui.javaeditor.DocumentAdapter.getContents(DocumentAdapter.java:371) at org.eclipse.jdt.int.ui.javaeditor.DocumentAdapter.getCharacters(DocumentAdapter.java:363) at org.eclipse.jdt.int.core.CompilationUnit.getContents(CompilationUnit.java:649) at org.eclipse.jdt.int.core.CompilationUnit$1.getContents(CompilationUnit.java:221) at org.eclipse.jdt.int.compiler.parser.Parser.parse(Parser.java:9483) at org.eclipse.jdt.int.compiler.parser.Parser.parse(Parser.java:9455) at org.eclipse.jdt.int.compiler.parser.Parser.dietParse(Parser.java:8102) at org.eclipse.jdt.int.compiler.Compiler.internalBeginToCompile(Compiler.java:696) at org.eclipse.jdt.int.compiler.Compiler.beginToCompile(Compiler.java:376) at org.eclipse.jdt.int.compiler.Compiler.resolve(Compiler.java:838) at org.eclipse.jdt.int.compiler.Compiler.resolve(Compiler.java:904) at org.eclipse.jdt.int.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:182) at org.eclipse.jdt.int.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:243) at org.eclipse.jdt.int.core.ReconcileWorkingCopyOperation.makeConsistent(ReconcileWorkingCopyOperation.java:190) at org.eclipse.jdt.int.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:89) at org.eclipse.jdt.int.core.JavaModelOperation.run(JavaModelOperation.java:709) at org.eclipse.jdt.int.core.JavaModelOperation.runOperation(JavaModelOperation.java:769) at org.eclipse.jdt.int.core.CompilationUnit.reconcile(CompilationUnit.java:1224) at org.eclipse.jdt.int.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:124) at org.eclipse.jdt.int.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108) at org.eclipse.jdt.int.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.jdt.int.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87) at org.eclipse.jdt.int.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:176) at org.eclipse.jdt.int.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114) at org.eclipse.jdt.int.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:133) at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105) at org.eclipse.jdt.int.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:388) at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173)
|
2008-05-22 15:55:12
| 1,211,490,000
|
resolved fixed
|
e763e82
| 1,231,330,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/DocumentAdapter.java
|
JDT
|
938
| 169,386
|
Bug 169386 [Theme] More Java editor features in Compare Editor
|
When comparing java elements, the local side does not benefit from the fact that there is compilation context available. Specifically, there is no java search and no hyperlinking. Clearly this is tricky to do for the non-local part of the compare but for the local it should behave as an editor. Is this a problem with reusing the jdt editor part? (i.e. the compare can only provide a generic text editor)? This was initiated from compare of local vs. head.
|
2007-01-02 18:41:38
| 1,167,780,000
|
resolved fixed
|
97bf137
| 1,231,320,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/compare/JavaMergeViewer.java
|
JDT
|
939
| 258,792
|
Bug 258792 [package explorer] 'Working Set Assignments' dialog no longer sorted if new ws is created
|
3.5 M4. The 'Working Set Assignemnts' dialog is no longer sorted if a new working set is created.
|
2008-12-15 05:52:56
| 1,229,340,000
|
resolved fixed
|
741b0ba
| 1,231,320,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/ConfigureWorkingSetAssignementAction.java
|
JDT
|
940
| 259,095
|
Bug 259095 [introduce parameter] Error reported in dialog/preview but result is OK
|
I20081216-0800. 1. start fresh workspace 2. paste this source: package p; public class TestInlineRename { int x = foo(1, 2, 3); public int foo(int xg, int yg, int zg) { return xg + yg; } } class B extends TestInlineRename { public int foo(int x, int y, int z) { System.out.println(x); foo(x, y, z); foo(x, z, y); super.foo(x, z, y); return super.x; } } 3. select method declaration TestInlineRename.foo 4. Refactor > Introduce Parameter Object... 5. click 'OK' ==> unexpected dialog comes which shows errors 6. click 'Continue' ==> correct code is generated
|
2008-12-17 08:40:21
| 1,229,520,000
|
resolved fixed
|
0586c01
| 1,231,250,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testSubclassInCU/in/TestSubclassInCU.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testSubclassInCU/out/FooParameter.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testSubclassInCU/out/TestSubclassInCU.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/IntroduceParameterObjectTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/IntroduceParameterObjectProcessor.java
|
JDT
|
941
| 254,603
|
Bug 254603 [package explorer][working sets] Package Explorer should support "Show All" Working Sets
|
When top-level elements are set to working sets, the most obvious usage of this would be to show all of the working sets defined. This is currently not supported. The user can configure PE to show all *current* working sets, but as new working sets are created, for example, when checking out sets of projects code from an SCM system, the user must constantly reconfigure the view to show all working sets again. I propose that if all of the current sets are selected (in the configure dialog), and the user presses OK, then this should be persisted as the single choice "all" rather than as the list of the currently defined sets.
|
2008-11-07 10:28:43
| 1,226,070,000
|
verified fixed
|
46df211
| 1,231,230,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewJavaWorkingSetWizard.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/ConfigureWorkingSetAssignementAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/WorkingSetModel.java
|
JDT
|
942
| 33,737
|
Bug 33737 [refactoring] dialog lost function - going back from Preview
|
20030228 it used to be able to go back from the preview it's not possible now it was a very useful feature - i could type some stuff in the input page, see the preview, go back if i didn't like what i saw, fix and keep doing that until i was happy with the result. it is not possible now and all my effort i put into entering input for a refactoring is gone as soon as i press preview (unless i'm lucky and get an error, in which case i can go back <g>) major - messes up my workflow
|
2003-03-04 06:27:28
| 1,046,780,000
|
verified fixed
|
829beec
| 1,229,450,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/IntroduceParameterObjectProcessor.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/IntroduceParameterObjectWizard.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/MoveInstanceMethodWizard.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/RefactoringWizardDialog2.java
|
JDT
|
943
| 88,265
|
Bug 88265 Make SourceRange API
|
JDT/Core uses source ranges to indicate the range of elements in source. Since most of the JDT/UI can deal with source range from IJavaElements and DOM/AST we implemented our own source range with implements ISoureRange to not be forced to copy source ranges retrieved from JDT/Core. Would it be possible to allow implementation of ISourceRange ?
|
2005-03-16 18:18:07
| 1,111,020,000
|
verified fixed
|
7af9e7e
| 1,229,420,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/SourceRange.java
|
JDT
|
944
| 256,879
|
Bug 256879 [package explorer] Assign Working Sets dialog should preserve check box setting
|
N20081126-2000. The dialog to assign working sets has a check box (show only package explorer working sets). This setting is not preserved but it should be.
|
2008-11-28 07:08:36
| 1,227,870,000
|
verified fixed
|
5383376
| 1,229,340,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/ConfigureWorkingSetAssignementAction.java
|
JDT
|
945
| 252,331
|
Bug 252331 [quick fix] Generate hashCode() and equals() should not be proposed if no non-static fields
|
I20081027-1800. 1. enable the warning for missing hashCode() 2. paste: class C { public boolean equals(Object obj) { return true; } } ==> quick fix to generate hashCode() and equals() is proposed but I only get a dialog that this can't be done due to no non-static fields.
|
2008-10-28 07:17:07
| 1,225,190,000
|
resolved fixed
|
1ba3ad2
| 1,229,020,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java
|
JDT
|
946
| 258,059
|
Bug 258059 [quick fix] Quick fix suggests invalid List<Object> for "instanceof List"
|
I20081209-0100 1. Paste the following in Package Explorer import java.util.List; public class X { boolean foo() { return null instanceof List; } } 2. You should get a warning: "List is a raw type. References to generic type List<E> should be parameterized" 3. Bring up Quick Fix and choose "Add type arguments to 'List'" 4. You have to choices: - inserting '<?>' (valid suggestion) - inserting '<Object>' (invalid suggestion) If you choose the second suggestion, the resulting code has the following error: "Cannot perform instanceof check against parameterized type List<Object>. Use instead its raw form List since generic type information will be erased at runtime"
|
2008-12-09 07:37:52
| 1,228,830,000
|
resolved fixed
|
162c166
| 1,229,010,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/Java50Fix.java
|
JDT
|
947
| 239,347
|
Bug 239347 Drag and drop any none java file doesn't refactor
|
Build ID: I20080516-1333 Steps To Reproduce: 1-Create general project, file file.a , and folder X on the project 2-Select file.a drag and drop into folder X. in the code, you'll find that this is handled by JavaDropAdaptorAssistant (I thought this only should do java files, and any other will be done by the resource adaptor). And in ReorgPolicyFactory.getModifications, update reference will be set to false. means refactoring file.a will not happen. More information: JavaDropAdaptorAssistant is intercepting all the Drag and Drop for any resource. the move is done properly, in ReorgPolicyFactory.getModifications, it checks if canUodateReferences and if the file is not a java, updateReferences will not be enabled. So refactorying any file type rather than Java is broken. Icluding our part. Was expecting, either Java handle all resource move but leave the update reference enabled. or just not provide the none-java resources. so other providers will handle it and propably will set the updateReferences normally.
|
2008-07-02 16:21:22
| 1,215,030,000
|
verified fixed
|
724389a
| 1,229,000,000
|
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ccp/MoveTest.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/JDTRefactoringDescriptorComment.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringCoreMessages.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameCompilationUnitProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameFieldProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameJavaProjectProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameLocalVariableProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameMethodProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenamePackageProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameTypeParameterProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameTypeProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/IReorgPolicy.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/JavaMoveProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/ReorgPolicyFactory.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/tagging/IReferenceUpdating.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameInputWizardPage.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/ReorgMoveWizard.java
|
JDT
|
948
| 258,135
|
Bug 258135 Confirm Delete package dialog: 'Delete subpackages' should have focus
|
I20081209-0100. The 'Delete subpackages' check box in the 'Confirm Delete' package dialog should have focus otherwise hitting Space bar to toggle the check box starts the deletion.
|
2008-12-09 12:23:44
| 1,228,840,000
|
resolved fixed
|
89002fb
| 1,228,840,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/DeleteWizard.java
|
JDT
|
949
| 182,539
|
Bug 182539 [package explorer][working sets] Offer delete on a working set
|
If my working set has nothing contained within it, I should be allowed to delete it. Hitting 'Delete' prompts no confirmation dialog and right-clicking on it doesn't work since 'Delete' is greyed out. It is cumbersome to have to go and edit my working sets just for this. If it's completely empty, deleting it should be no loss, and prompting a confirmation dialog should suffice as a deterrent for misclicked deletions.
|
2007-04-16 08:34:25
| 1,176,730,000
|
verified fixed
|
f447f86
| 1,228,480,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringAvailabilityTester.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/ReorgUtils.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/DeleteAction.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/ReorgMessages.java
|
JDT
|
950
| 257,695
|
Bug 257695 [common navigator] action groups are not disposed
|
I20081202-1812. All Java action (groups) are leaked when the Project Explorer is closed.
|
2008-12-05 05:55:00
| 1,228,470,000
|
verified fixed
|
0ce8c43
| 1,228,480,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaNavigatorActionProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaNavigatorRefactorActionProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaNavigatorViewActionProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/PackageExplorerOpenActionProvider.java
|
JDT
|
951
| 257,490
|
Bug 257490 [compiler] Quick fix for dead code does not remove all the dead code
|
build I20081202-1812 1) enable dead code diagnosis 2) create Test.java public class Test { void foo() { if (true) { return; } System.out.println("1"); System.out.println("2"); System.out.println("3"); } } A dead code problem is reported on the line 'System.out.println("1");' 3) apply the proposed quickfix 'Remove' The line 'System.out.println("1");' is removed. The quickfix could also remove next lines which are also dead code.
|
2008-12-04 04:19:37
| 1,228,380,000
|
resolved fixed
|
88713cb
| 1,228,400,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java
|
JDT
|
952
| 175,733
|
Bug 175733 [refactoring] change execution should not happen in the UI thread
|
I20070209-1006 In a project that has a lot of packages, deleting them all from within the project explorer causes the UI to hang.
|
2007-02-27 14:20:54
| 1,172,600,000
|
verified fixed
|
e21dfbc
| 1,228,160,000
|
org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/Lock.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/MultiStateTextFileChange.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/TextChange.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/TextFileChange.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/UIPerformChangeOperation.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/RefactoringUI.java
|
JDT
|
953
| 256,991
|
Bug 256991 [syntax highlighting] No syntax highlighting for this/super constructor argument
| null |
2008-11-30 15:03:38
| 1,228,080,000
|
resolved fixed
|
c443e98
| 1,228,130,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/SemanticHighlightingReconciler.java
|
JDT
|
954
| 256,869
|
Bug 256869 [quick fix] Dead Code Analysis: there is no QuickFix for if/else with DEBUG
|
Build id: N20081126-2000 Dead Code Analysis found an issue in org.eclipse.core.internal.jobs.OrderedLock if (DEBUG && success) System.out.println("[" + Thread.currentThread() + "] Operation started... " + this); //$NON-NLS-1$ //$NON-NLS-2$ else if (DEBUG) System.out.println("[" + Thread.currentThread() + "] Operation timed out... " + this); //$NON-NLS-1$ //$NON-NLS-2$ The two quick fixes that are available for this case are either remove 'success' from 'if (DEBUG && success)' or remove 'System.out.println("[" + Thread.currentThread() + "] Operation started... " + this); //$NON-NLS-1$ //$NON-NLS-2$' It should rather suggest to create two if statements, one for 'DEBUG' another for 'success'.
|
2008-11-28 05:23:27
| 1,227,870,000
|
resolved fixed
|
a4fcc46
| 1,227,890,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java
|
JDT
|
955
| 75,794
|
Bug 75794 [quick assist] Split && condition not available with else branch
| null |
2004-10-07 09:43:36
| 1,097,160,000
|
resolved fixed
|
6a0b8fd
| 1,227,890,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java
|
JDT
|
956
| 256,571
|
Bug 256571 Possibly broken code in RenameInformationPopup.getPolygon(boolean)
|
I20081125-0840 While doing the dead-code analysis I found this code in org.eclipse.jdt.internal.ui.refactoring.reorg.RenameInformationPopup.getPolygon(boolean): The return at the end is dead code.
|
2008-11-26 04:20:57
| 1,227,690,000
|
resolved fixed
|
26d8b94
| 1,227,810,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameInformationPopup.java
|
JDT
|
957
| 256,463
|
Bug 256463 [compiler] Support common debug pattern in unreachable code detection
| null |
2008-11-25 11:59:23
| 1,227,630,000
|
verified fixed
|
0783d35
| 1,227,800,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/preferences/OptionsConfigurationBlockTest.java
|
JDT
|
958
| 256,759
|
Bug 256759 [implementation] Implementations of IContextInformation should also implement hashCode()
|
I20081125-0840 Implementations of IContextInformation should also implement hashCode().
|
2008-11-27 06:56:38
| 1,227,790,000
|
resolved fixed
|
27634f7
| 1,227,800,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaCompletionProposalComputer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/LazyGenericTypeProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ProposalContextInformation.java
|
JDT
|
959
| 256,578
|
Bug 256578 [implementation] Possibly broken code in LocalCorrectionsSubProcessor.addUnnecessaryInstanceofProposal(IInvocationContext, IProblemLocation, Collection)
|
I20081125-0840. While doing the dead-code analysis I found this code in org.eclipse.jdt.internal.ui.text.correction.LocalCorrectionsSubProcessor.addUnnecessaryInstanceofProposal(IInvocationContext, IProblemLocation, Collection): The code in the if (false/*ASTNodes.needsParentheses(expression)*/) is never executed.
|
2008-11-26 04:31:55
| 1,227,690,000
|
resolved fixed
|
b2dd92d
| 1,227,800,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java
|
JDT
|
960
| 256,577
|
Bug 256577 [implementation] Possibly broken code in JavadocLinkTypeCompletionProposal.computeReplacementString()
|
I20081125-0840. While doing the dead-code analysis I found this code in org.eclipse.jdt.internal.ui.text.javadoc.JavadocLinkTypeCompletionProposal.computeReplacementString(): The else-branch is never executed.
|
2008-11-26 04:30:43
| 1,227,690,000
|
resolved fixed
|
ba24da1
| 1,227,800,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavadocLinkTypeCompletionProposal.java
|
JDT
|
961
| 256,576
|
Bug 256576 [implementation] Possibly broken code in JavaIndenter
|
I20081125-0840. While doing the dead-code analysis I found this code in org.eclipse.jdt.internal.ui.text.JavaIndenter.CorePrefs.prefCaseBlockIndent() and org.eclipse.jdt.internal.ui.text.JavaIndenter.CorePrefs.prefParenthesisDeepIndent()
|
2008-11-26 04:29:53
| 1,227,690,000
|
resolved fixed
|
3e0362b
| 1,227,800,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaIndenter.java
|
JDT
|
962
| 256,574
|
Bug 256574 [package explorer] Possibly broken code in PackageExplorerContentProvider.findAddedElement(IJavaElementDelta)
|
I20081125-0840. While doing the dead-code analysis I found this code in org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.findAddedElement(IJavaElementDelta): for (int i= 0; i < affectedChildren.length; i++) return findAddedElement(affectedChildren[i]); Obviously the loop is either useless as it will at most handle affectedChildren[0] or it is broken.
|
2008-11-26 04:25:47
| 1,227,690,000
|
resolved fixed
|
c3b5b2b
| 1,227,770,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerContentProvider.java
|
JDT
|
963
| 256,532
|
Bug 256532 [templates] TemplateProposals has API that should be marked deprecated
| null |
2008-11-25 20:28:32
| 1,227,660,000
|
resolved fixed
|
d2b3468
| 1,227,710,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/template/contentassist/TemplateProposal.java
|
JDT
|
964
| 256,575
|
Bug 256575 [search] Possibly broken code in SearchLabelProvider.getParticipantImage(Object)
|
I20081125-0840. While doing the dead-code analysis I found this code in org.eclipse.jdt.internal.ui.search.SearchLabelProvider.getParticipantImage(Object): The lower part of the method is never executed.
|
2008-11-26 04:29:06
| 1,227,690,000
|
resolved fixed
|
3193318
| 1,227,710,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/SearchLabelProvider.java
|
JDT
|
965
| 256,087
|
Bug 256087 [typing] Automatically close brace does not work properly
|
Build I20081118-1720. I have the following simple line of code: if (condition) return false; I want to insert brace around the single statement of the if block. For this, I only type a brace just before the return and simply hit 'Enter': if (condition) {return false; As my Java editor preference 'Automatically close {braces}' is checked, I would expect to get the following code: if (condition) { return false; } But I get the following code instead: if (condition) { }return false; As this code does not compile, it's a little bit annoying...
|
2008-11-21 05:53:47
| 1,227,260,000
|
resolved fixed
|
2d3acca
| 1,227,530,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaAutoIndentStrategy.java
|
JDT
|
966
| 255,743
|
Bug 255743 [search] NPE searching for property key
|
Using eclipse.buildId=I20081111-0800 java.version=1.6.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_CA Command-line arguments: -os win32 -ws win32 -arch x86 -debug -consolelog -console, I got this when I was editing a properties file. I mistyped some characters and suddenly I got this error in an error dialog. I might have triggered a search by mistake. java.lang.NullPointerException at org.eclipse.jdt.internal.core.search.matching.MatchLocator.findIndexMatches(MatchLocator.java:269) at org.eclipse.jdt.internal.core.search.PatternSearchJob.search(PatternSearchJob.java:97) at org.eclipse.jdt.internal.core.search.PatternSearchJob.execute(PatternSearchJob.java:63) at org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:276) at org.eclipse.jdt.internal.core.search.BasicSearchEngine.findMatches(BasicSearchEngine.java:206) at org.eclipse.jdt.internal.core.search.BasicSearchEngine.search(BasicSearchEngine.java:506) at org.eclipse.jdt.core.search.SearchEngine.search(SearchEngine.java:551) at org.eclipse.jdt.internal.ui.propertiesfileeditor.PropertyKeyHyperlink$4.run(PropertyKeyHyperlink.java:458) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
|
2008-11-18 21:18:47
| 1,227,060,000
|
resolved fixed
|
6b80336
| 1,227,250,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertyKeyHyperlink.java
|
JDT
|
967
| 251,693
|
Bug 251693 NamingConventions.suggestXXXNames should call suggestVariableNames()
|
The old API NamingConventions.suggestXXXNames() should call the new API NamingConventions.suggestVariableNames().
|
2008-10-22 07:20:33
| 1,224,670,000
|
verified fixed
|
1e2876f
| 1,227,200,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/NameProposerTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractConstantRefactoring.java
|
JDT
|
968
| 230,189
|
Bug 230189 [api tooling] Extending an @noimplement interface should not be an error
|
Build ID: I20080502-0100 (Eclipse 3.4M7) Consider following rather common scenario: /** @noimplement Do not implement directly. Extend abstract base Foo instead. */ public interface IFoo { //... } public abstract class Foo implements IFoo { //... } With following client code: interface IFooBar extends IFoo { public void bar(); } class MyFooBar extends Foo implements IFooBar { public void bar(); } In this case, the client code legally implements IFoo, because it does so by extending abstract base Foo. This scenario should not be flagged as an error: Just extending an interface does not introduce any binary compatibility issues. But currently the API Tooling flags IFooBar extends IFoo as an error.
|
2008-05-05 08:02:49
| 1,209,990,000
|
verified fixed
|
8953d87
| 1,227,040,000
|
org.eclipse.jdt.core.manipulation/refactoring/org/eclipse/jdt/core/refactoring/IJavaRefactorings.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/junit/model/ITestCaseElement.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/junit/model/ITestElement.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/junit/model/ITestElementContainer.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/junit/model/ITestRunSession.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/junit/model/ITestSuiteElement.java org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/model/ITestCaseElement.java org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/model/ITestElement.java org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/model/ITestElementContainer.java org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/model/ITestRunSession.java org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/model/ITestSuiteElement.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/IContextMenuConstants.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/IJavaElementSearchConstants.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/IPackagesViewPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/ISharedImages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/ITypeHierarchyViewPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/IWorkingCopyManager.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/IWorkingCopyManagerExtension.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/IWorkingCopyProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/IJavaEditorActionDefinitionIds.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/dialogs/ITypeInfoRequestor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/dialogs/ITypeSelectionComponent.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/refactoring/IRefactoringProcessorIds.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/search/ISearchRequestor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/IJavaColorConstants.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/IInvocationContext.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/IProblemLocation.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/IRefactoringCoreStatusCodes.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/IUndoManager.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/history/IRefactoringHistoryService.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/IRefactoringUIStatusCodes.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/history/IRefactoringHistoryControl.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/history/ISortableRefactoringHistoryControl.java
|
JDT
|
969
| 252,415
|
Bug 252415 [build path] New Java Project dialog radios should have same parent
|
Build id: I20081027-1800 1) File->New->Java Project The "New Java Project" dialog opens, and focus is in the "Project name:" text field. 2) Type the Tab key twice to move the focus to the "JRE" group of radios. 3) Type Tab one more time. Focus moves to the next radio in the group? This is not supposed to happen. Also, the next radio in the group becomes selected? This is not supposed to happen either. It would be very confusing to a screen reader user, who would not be able to see the visual relationship of the radios. The problem is that the "Use default JRE" radio (the topmost one) does not have the same parent as the "Use a project specific JRE" or "Use an exception environment JRE" radios. They need to have the same parent in order to work the way the platform intended. (i.e. you will also note that you cannot use arrow keys to traverse from the top radio to the other two, but you should be able to). I suspect that this was done in order to do the layout. However, this layout can be achieved with just one Composite and 3 columns in a GridLayout.
|
2008-10-28 12:17:58
| 1,225,210,000
|
resolved fixed
|
f38f983
| 1,226,940,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPageOne.java
|
JDT
|
970
| 255,449
|
Bug 255449 CheckedListDialogField uses an unconventional method of setting the table's style
|
Its code looks like so... protected TableViewer createTableViewer(Composite parent) { Table table= new Table(parent, SWT.CHECK + getListStyle()); /* commented out */ return tableViewer; } ...notice how it uses a + instead of a | for OR'ing the bits. Is this intended or some lucky typo? If this is intentional, I strongly suggest inlining a comment.
|
2008-11-16 02:10:31
| 1,226,820,000
|
resolved fixed
|
f04b3f1
| 1,226,920,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/dialogfields/CheckedListDialogField.java
|
JDT
|
971
| 255,448
|
Bug 255448 [preferences] 'Code Style' preference page should have a single selection table
|
I20081112-1200 1. Window > Preferences > Java > Code Style 2. Click on an entry in the table, the 'Edit' button is enabled. 3. Ctrl+Click on another entry in the table, the 'Edit' button is disabled. 4. Look at the other preferences and see how they apply to the selection in the table. 5. Conclude that they have nothing to do with variable names. 6. Conclude that multiselection appears to serve no purpose in this table.
|
2008-11-16 02:06:02
| 1,226,820,000
|
resolved fixed
|
2a53691
| 1,226,910,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/NameConventionConfigurationBlock.java
|
JDT
|
972
| 251,197
|
Bug 251197 [breadcrumb] Dropdown for children of project should look like Package Explorer
|
I20081014-1600 The breadcrumb dropdown for children of a project should look like the Package Explorer: - show libary nodes 'JRE System Library', 'Plug-in Dependencies', .... - bonus points: show "Referenced Libraries" node
|
2008-10-17 05:51:18
| 1,224,240,000
|
resolved fixed
|
b03ef03
| 1,226,670,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorBreadcrumb.java
|
JDT
|
973
| 254,759
|
Bug 254759 Search declarations in working sets should not fail if no working set is specified
|
Using eclipse.buildId=I20081104-0916 java.version=1.6.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_CA Command-line arguments: -os win32 -ws win32 -arch x86 -debug -consolelog -console I got:java.lang.IllegalArgumentException: data must not be null at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.<init>(JavaSearchQuery.java:62) at org.eclipse.jdt.ui.actions.FindAction.performNewSearch(FindAction.java:276) at org.eclipse.jdt.ui.actions.FindAction.run(FindAction.java:267) at org.eclipse.jdt.ui.actions.FindAction.run(FindAction.java:230) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:278) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:412) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3848) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3446) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:333) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:370) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) Steps to reproduce: 1) select a method declaration 2) in the search menu, select Search>Declarations>Working sets 3) Select No working sets 4) Do the seach. It fails. Selecting Search>References> with no working sets seems to do something.
|
2008-11-10 11:40:03
| 1,226,340,000
|
resolved fixed
|
8a7f6fb
| 1,226,400,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FindDeclarationsInWorkingSetAction.java
|
JDT
|
974
| 254,721
|
Bug 254721 org.eclipse.jdt.ui.actions.MoveAction doesn't work with explicitly given selection
|
Build ID: M20080911-1700 Steps To Reproduce: 1. In your code instantiate the org.eclipse.jdt.ui.actions.MoveAction 2. Invoke run(IStructuredSelection selection) with a selection corresponding to certain java class Result: The command won't be invoked with the given selection. Instead of this the selection from the IWorkbenchSite object will be taken (if it's possible) More information: I've debugged the code and found out that (in that particular use case) the run(IStructuredSelection selection) method invokes the internal org.eclipse.jdt.internal.ui.refactoring.reorg.ReorgMoveAction. But it doesn't invoke it with the IStructuredSelection object given as parameter. Instead, it invokes its run() method without parameters and, as a result, ReorgMoveAction tries to get the selection from the IWorkbenchSite object with which it was initialized, instead of the given IStructuredSelection as parameter of the method. This way it makes impossible to use the MoveAction for moving java classes if we want to give selection directly to the run() method. As a workaround I use directly ReorgMoveAction which is not very clear, since it's an internal API. I would've think that this is an intended behavior, but, if it is so, why the run(IStructuredSelection selection) is exposed as a public API? Besides, the RenameAction, for example works well for the same use case!
|
2008-11-10 05:28:57
| 1,226,310,000
|
resolved fixed
|
147397c
| 1,226,320,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/MoveAction.java
|
JDT
|
975
| 254,601
|
Bug 254601 FatJarExportTests occasionally fail because ZipFile has not been closed
| null |
2008-11-07 10:00:08
| 1,226,070,000
|
resolved fixed
|
c7fb1ed
| 1,226,070,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/jarexport/FatJarExportTests.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/jarexport/PlainJarExportTests.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarFileExportOperation.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarPackagerUtil.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/FatJarManifestProvider.java
|
JDT
|
976
| 253,378
|
Bug 253378 Paste class source breaks static import.
|
Build ID: M20080911-1700 (3.4.1) Steps To Reproduce: 1. In package explorer, copy the Bug.java file. 2. In package explorer, paste it into the same package with a new class name. See that the static import statement is illegal. ---------------- bug/Bug.java ----------------- package bug; import static bug.Bug.X.z; class Bug { enum X{z} X y=z; }
|
2008-11-03 17:56:51
| 1,225,750,000
|
resolved fixed
|
0d94fc4
| 1,225,910,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/CreateCopyOfCompilationUnitChange.java
|
JDT
|
977
| 252,591
|
Bug 252591 [render] External chained jars are not correctly displayed
| null |
2008-10-29 10:33:03
| 1,225,290,000
|
resolved fixed
|
9011d1e
| 1,225,380,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementLabelComposer.java
|
JDT
|
978
| 252,643
|
Bug 252643 [compare] NPE trying to replace a static initializer with an old version from the local history
|
Using eclipse.buildId=I20081028-0100 java.version=1.6.0_10 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_CA Command-line arguments: -os win32 -ws win32 -arch x86 -debug -consolelog -console I got this exception trying to replace a static initializer in a test case with an old version. java.lang.NullPointerException at org.eclipse.jdt.internal.ui.compare.JavaReplaceWithEditionActionImpl.performReplace(JavaReplaceWithEditionActionImpl.java:191) at org.eclipse.jdt.internal.ui.compare.JavaReplaceWithEditionActionImpl.replace(JavaReplaceWithEditionActionImpl.java:148) at org.eclipse.jdt.internal.ui.compare.JavaReplaceWithEditionActionImpl$1.performReplace(JavaReplaceWithEditionActionImpl.java:122) at org.eclipse.team.ui.history.HistoryPageCompareEditorInput.okPressed(HistoryPageCompareEditorInput.java:216) at org.eclipse.compare.internal.CompareDialog.buttonPressed(CompareDialog.java:203) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:625) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3848) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3446) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.compare.internal.CompareDialog.open(CompareDialog.java:195) at org.eclipse.compare.internal.CompareUIPlugin$3.run(CompareUIPlugin.java:1209) at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1219) at org.eclipse.compare.internal.CompareUIPlugin.internalOpenDialog(CompareUIPlugin.java:1212) at org.eclipse.compare.internal.CompareUIPlugin.openCompareDialog(CompareUIPlugin.java:526) at org.eclipse.compare.CompareUI.openCompareDialog(CompareUI.java:211) at org.eclipse.jdt.internal.ui.compare.JavaReplaceWithEditionActionImpl.run(JavaReplaceWithEditionActionImpl.java:129) at org.eclipse.jdt.internal.ui.compare.JavaHistoryActionImpl.run(JavaHistoryActionImpl.java:327) at org.eclipse.jdt.internal.ui.compare.JavaHistoryAction.run(JavaHistoryAction.java:81) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:412) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3848) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3446) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:333) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:370) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
|
2008-10-29 15:34:32
| 1,225,310,000
|
verified fixed
|
6c1a075
| 1,225,350,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/compare/JavaReplaceWithEditionActionImpl.java
|
JDT
|
979
| 252,493
|
Bug 252493 [clean up] ICleanUpConfigurationUI let selected cleanups exceed limit
|
I20081028-0100 ICleanUpConfigurationUI#getSelectedCleanUpCount implementations can return values greater then #getCleanUpCount. This could indicate a programming fault and should be warned.
|
2008-10-28 16:15:52
| 1,225,220,000
|
resolved fixed
|
e408c91
| 1,225,270,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/CleanUpTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/ContributedCleanUpTabPage.java
|
JDT
|
980
| 252,383
|
Bug 252383 [browsing] NPE when switching to/from Welcome
|
I20081027-1800. 1. open Java Browsing perspective 2. open Welcome 3. close Welcome ==> NPE:
|
2008-10-28 11:04:13
| 1,225,210,000
|
verified fixed
|
7ae7547
| 1,225,210,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/browsing/JavaBrowsingPart.java
|
JDT
|
981
| 234,143
|
Bug 234143 [syntax coloring] Deprecation doesn't properly appear on keywords this and super for construction calls
|
Hello, Try this code: class foo { public foo(String a) { this(a, null); } /** * @deprecated */ @Deprecated public foo(String a, String b) { } } class bar extends foo { public bar(Object o) { this(o, "bar"); } public bar(Object o, String a) { this(o, a, null); } public bar(Object o, String a, String b) { super(a, b); new foo(a,b); } } You will observe none of the this(*) and super(*) constructor calls are stroke, whereas the declaration of foo(String, String) and its use with the new call are. Thanks Mathieu Sivade
|
2008-05-27 08:59:19
| 1,211,890,000
|
verified fixed
|
6b76251
| 1,225,120,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/SemanticHighlightingReconciler.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/SemanticHighlightings.java
|
JDT
|
982
| 251,629
|
Bug 251629 Adding JUnit by quick fix throws IAE
|
N20081005-2000 Paste the following into an empty project: ------------ package p; public class ATest extends TestCase { } ------------ Use quick fix to "Add Junit 3 to build path". This throws the following IAE: java.lang.IllegalArgumentException: Attempted to beginRule: MultiRule[P/tests,P/.org.eclipse.jdt.core.external.folders], does not match outer scope rule: P/tests at org.eclipse.core.runtime.Assert.isLegal(Assert.java:64) at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:122) at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:232) at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:58) at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:231) at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:117) at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1747) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1795) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786) at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:2855) at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:2871) at org.eclipse.jdt.internal.corext.refactoring.changes.ClasspathChange.perform(ClasspathChange.java:88) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:260) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:308) at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:110) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:225) at org.eclipse.jdt.internal.junit.ui.JUnitQuickFixProcessor$1.run(JUnitQuickFixProcessor.java:239) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:446) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:354) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2487) at org.eclipse.jdt.internal.junit.ui.JUnitQuickFixProcessor$JUnitClasspathFixCorrectionProposal.apply(JUnitQuickFixProcessor.java:231) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.insertProposal(CompletionProposalPopup.java:929) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.insertSelectedProposalWithMask(CompletionProposalPopup.java:875) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.verifyKey(CompletionProposalPopup.java:1302) at org.eclipse.jface.text.contentassist.ContentAssistant$InternalListener.verifyKey(ContentAssistant.java:806) <snip>
|
2008-10-21 17:44:51
| 1,224,630,000
|
verified fixed
|
c3b6066
| 1,224,840,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/JUnitQuickFixProcessor.java
|
JDT
|
983
| 251,758
|
Bug 251758 [ltk] Undoing a project delete has problems with encoding and markers
|
Created this clone bug of the IDE equivalent. Will attach a patch. ---------------- Steps To Reproduce: 1. Create a project, and add at least one file to it. Add some markers to the file (tasks, bookmarks, problem markers - it doesn't really matter, so long as they can be seen in a marker view). 2. Delete the project, selecting "Do not delete contents" when prompted. 3. Now go to the Edit menu, and choose "Undo Delete Resources". 4. Open up the appropriate marker view, and examine the markers on the newly restored project. You will see that, although all the markers have been restored, they are not on the file anymore; they appear to have all been moved to the project instead.
|
2008-10-22 14:55:02
| 1,224,700,000
|
verified fixed
|
44176c6
| 1,224,770,000
|
org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/internal/core/refactoring/resource/undostates/AbstractResourceUndoState.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/internal/core/refactoring/resource/undostates/ProjectUndoState.java
|
JDT
|
984
| 251,817
|
Bug 251817 [clean up] Fail to invoke "Clean Up" at project level
|
Could not invoke "Clean Up" feature either with keyboard shortcut or with context menu at project level. Same at package level. This is a plain Java Project, but I encountered the same issue with a Web Dynamic Project. -- Error Details -- Date: Thu Oct 23 11:21:07 CEST 2008 Message: Internal Error Severity: Error Plugin: org.eclipse.jdt.ui Session Data: eclipse.buildId=M20080911-1700 java.version=1.6.0_07 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=it_IT Command-line arguments: -os win32 -ws win32 -arch x86 Exception Stack Trace: java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:415) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507) at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper.perform(RefactoringExecutionHelper.java:194) at org.eclipse.jdt.internal.corext.refactoring.RefactoringExecutionStarter.startCleanupRefactoring(RefactoringExecutionStarter.java:243) at org.eclipse.jdt.internal.ui.actions.AllCleanUpsAction.performRefactoring(AllCleanUpsAction.java:76) at org.eclipse.jdt.internal.ui.actions.CleanUpAction.runOnMultiple(CleanUpAction.java:214) at org.eclipse.jdt.internal.ui.actions.CleanUpAction.run(CleanUpAction.java:117) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) Caused by: org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:86) at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:74) at org.eclipse.jdt.internal.ui.fix.AbstractCleanUp.isEnabled(AbstractCleanUp.java:100) at org.eclipse.jdt.internal.ui.fix.PotentialProgrammingProblemsCleanUp.checkPreConditions(PotentialProgrammingProblemsCleanUp.java:146) at org.eclipse.jdt.internal.corext.fix.CleanUpRefactoring.checkPreConditions(CleanUpRefactoring.java:735) at org.eclipse.jdt.internal.corext.fix.CleanUpRefactoring.checkFinalConditions(CleanUpRefactoring.java:650) at org.eclipse.ltk.core.refactoring.Refactoring.checkAllConditions(Refactoring.java:160) at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:77) at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:709) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4650) at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:92) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
|
2008-10-23 05:24:50
| 1,224,750,000
|
verified fixed
|
e78e1ec
| 1,224,770,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringExecutionStarter.java
|
JDT
|
985
| 251,771
|
Bug 251771 [clean up] Message dialog for every save
|
build I20081021-0905 For our projects, we have Save Actions turned on and since I updated to this build, every time I save a Java file I get a message dialog saying that the Organize Imports save action is very slow and I may want to turn it off. I don't mind hitting the "Do not show this message again" checkbox but I wonder if perhaps the tolerance should be modified... I would assume things like formatting and organize imports would be common save actions for users.
|
2008-10-22 16:03:04
| 1,224,710,000
|
resolved fixed
|
1a73296
| 1,224,760,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CleanUpRefactoring.java
|
JDT
|
986
| 251,572
|
Bug 251572 [encapsulate field] encapsulate field refactoring fails with splitted array type
| null |
2008-10-21 13:32:31
| 1,224,610,000
|
resolved fixed
|
3b90d38
| 1,224,690,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/sef/SelfEncapsulateFieldRefactoring.java
|
JDT
|
987
| 251,327
|
Bug 251327 [browsing] JavaBrowsingPart not clearing fPreveiousSelectionProvider
|
Build ID: M20080911-1700 Steps To Reproduce: 1. Open two editors - one must be an ITextEditor (any java file) and the other must not be (extend EditorPart directly and only implement ISelectionProvider) 2. Place a break point in JavaBrowsingPart.selectionChanged(IWorkbenchPart, ISelection) 2. Switch between the two editors in the java browsing perspective (so you can see the packages). 3. When you select the ITextEditor it shows the editor's package, when you select the non-ITextEditor it checks line 718 and determines that the same part last fired the selection event because when the ITextEditor's selection event is processed it doesn't set fPreviousSelectionProvider. More information: A simple fix would seem to be to set the fPreviousSelectionProvider in a finally block with the contents of selectionChanged inside the try portion. It would be nice if this could make it into the next release as it really makes custom displays a pain to integrate.
|
2008-10-19 17:04:35
| 1,224,450,000
|
resolved fixed
|
92a550f
| 1,224,580,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/browsing/JavaBrowsingPart.java
|
JDT
|
988
| 250,806
|
Bug 250806 Activating working set updaters for bundle org.eclipse.jdt.ui has encountered a problem.
|
Build ID: M20080911-1700 Steps To Reproduce: 1.Go to Problems View --> Configure Contents 2. Set Scope ON working set 3. create a working set that contain not all project, just some 4. restart eclipse 5 I got this error and stack trace with NPE bellow I guess that NullPointerException at JavaWorkingSetUpdater.checkElementExistence(JavaWorkingSetUpdater.java:223) is a real problem.... More information: org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:3777) at org.eclipse.swt.SWT.error(SWT.java:3695) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) Caused by: java.lang.NullPointerException at org.eclipse.jdt.internal.ui.workingsets.JavaWorkingSetUpdater.checkElementExistence(JavaWorkingSetUpdater.java:223) at org.eclipse.jdt.internal.ui.workingsets.JavaWorkingSetUpdater.add(JavaWorkingSetUpdater.java:78) at org.eclipse.ui.internal.AbstractWorkingSetManager$5.runInUIThread(AbstractWorkingSetManager.java:647) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) ... 22 more eclipse.buildId=M20080911-1700 java.version=1.6.0_07 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ru_RU Command-line arguments: -os win32 -ws win32 -arch x86
|
2008-10-14 12:19:59
| 1,224,000,000
|
verified fixed
|
5d356ff
| 1,224,520,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/JavaWorkingSetUpdater.java
|
JDT
|
989
| 251,362
|
Bug 251362 [package explorer] 'Configure...' looks strange on working set assignment dialog
| null |
2008-10-20 06:01:31
| 1,224,500,000
|
verified fixed
|
eb753d3
| 1,224,510,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/ConfigureWorkingSetAssignementAction.java
|
JDT
|
990
| 233,955
|
Bug 233955 [misc] Put ActivateJavaEditorTest back
|
3.4 RC3. During 3.5 we need to verify that the modified test is reliable and then put it pack to the local fingerprint/summary.
|
2008-05-26 09:11:39
| 1,211,810,000
|
resolved fixed
|
774b41e
| 1,224,170,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/PerformanceTestSuite.java
|
JDT
|
991
| 250,960
|
Bug 250960 [misc] Status line does not show problem message any more
|
I20081014-1600, was OK in 3.4.1 Status line does not show problem message any more when the caret is in a range with squiggly lines. Example: package xy; public class Try { unresolved m() { , } }
|
2008-10-15 10:58:25
| 1,224,080,000
|
resolved fixed
|
a6feb57
| 1,224,140,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java
|
JDT
|
992
| 250,961
|
Bug 250961 [build path] NPE attaching source JAR
|
build I20081007-1600 - create new Java project - go to the project properties via the context menu - edit the Java build path - add external JARs - navigate to your install dir and select org.eclipse.update* (not the source JARs) - OK - select first JAR and edit the source attachment - try and add the source JAR - hit OK - note that the dialog is not updated and nothing happens I checked my log and had the following message. Also got the same stack trace when opening a class file in an editor and trying to attach source to it there. !ENTRY org.eclipse.ui 4 0 2008-10-15 11:01:56.567 !MESSAGE Unhandled event loop exception !STACK 0 java.lang.NullPointerException at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListElement.createFromExisting(CPListElement.java:579) at org.eclipse.jdt.internal.ui.wizards.buildpaths.CPListElement.createFromExisting(CPListElement.java:544) at org.eclipse.jdt.internal.ui.wizards.buildpaths.SourceAttachmentBlock.getNewEntry(SourceAttachmentBlock.java:180) at org.eclipse.jdt.internal.ui.wizards.buildpaths.SourceAttachmentDialog.getResult(SourceAttachmentDialog.java:103) at org.eclipse.jdt.ui.wizards.BuildPathDialogAccess.configureSourceAttachment(BuildPathDialogAccess.java:108) at org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor$2.widgetSelected(ClassFileEditor.java:285) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3848) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3446) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:333) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:370) 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:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
|
2008-10-15 11:07:59
| 1,224,080,000
|
resolved fixed
|
8661c50
| 1,224,140,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/CPListElement.java
|
JDT
|
993
| 250,425
|
Bug 250425 [extract interface] Interface extraction terminates with an Internal Error
| null |
2008-10-10 08:04:35
| 1,223,640,000
|
resolved fixed
|
2042c25
| 1,224,090,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractInterface/test108/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractInterface/test108/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractInterface/test108/out/I.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ExtractInterfaceTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/constraints/SuperTypeConstraintsCreator.java
|
JDT
|
994
| 224,958
|
Bug 224958 [api] make CompilationUnitChange API
|
In order to pass RFRS by Instantiations WindowBuilder product it should not contain any internal API usage. The functionality of org.eclipse.jdt.internal.corext.refactoring.changes.CompilationUnitChange can't be implemented using public API, please move it into public scope.
|
2008-03-31 13:49:40
| 1,206,990,000
|
resolved fixed
|
870614a
| 1,224,060,000
|
org.eclipse.jdt.core.manipulation/common/org/eclipse/jdt/internal/core/manipulation/JavaManipulationMessages.java org.eclipse.jdt.core.manipulation/common/org/eclipse/jdt/internal/core/manipulation/Messages.java org.eclipse.jdt.core.manipulation/refactoring/org/eclipse/jdt/core/refactoring/CompilationUnitChange.java org.eclipse.jdt.core.manipulation/refactoring/org/eclipse/jdt/core/refactoring/UndoCompilationUnitChange.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/changes/CompilationUnitChange.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/changes/UndoCompilationUnitChange.java
|
JDT
|
995
| 250,663
|
Bug 250663 Fix for 249932 causes JDT Launching bundle to be activated
| null |
2008-10-13 11:55:57
| 1,223,910,000
|
resolved wontfix
|
361d3dd
| 1,224,000,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/PluginsNotLoadedTest.java
|
JDT
|
996
| 66,646
|
Bug 66646 [package explorer] Show in doesn't inform user about filters if name filter filters element to be shown
|
I20040611 - create project Test - create class A - open in editor - package explorer: set name filter for Test - give focus to editor - Show in Package exlorer observe: you don't get a hint that the element is filtered out.
|
2004-06-11 07:01:34
| 1,086,950,000
|
resolved fixed
|
d0678c4
| 1,224,000,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/CustomFiltersActionGroup.java
|
JDT
|
997
| 74,759
|
Bug 74759 [introduce factory] refactoring doesn't work with nested constructors
|
The nested constructor call in the following code is not refactored correctly: public class Test { public Test(Test tal) { return; } public static void main(String[] args) { Test test = new Test(new Test(null)); } }
|
2004-09-23 07:29:29
| 1,095,940,000
|
verified fixed
|
a30a3d5
| 1,223,990,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceFactory/Bugzilla/74759/Test.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceFactory/Bugzilla/74759/Test_out.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/IntroduceFactoryTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceFactoryRefactoring.java
|
JDT
|
998
| 250,621
|
Bug 250621 [hashcode/equals] Wizard should allow to specify that blocks should always be used
|
Build ID: I20080617-2000 Steps To Reproduce: Hi, The code convension tool checkstyle complains about missing curly braces in the generated Eclipse equals method. I suggest to use {} in your template. Example: Now @Override public boolean equals(Object obj) { if (this == obj) return true; if (obj == null) return false; if (getClass() != obj.getClass()) return false; Test other = (Test) obj; if (test == null) { if (other.test != null) return false; } else if (!test.equals(other.test)) return false; return true; } Example: Should be: @Override public boolean equals(Object obj) { if (this == obj) { return true; } if (obj == null) { return false; } if (getClass() != obj.getClass()) { return false; } Test other = (Test) obj; if (test == null) { if (other.test != null) { return false; } } else if (!test.equals(other.test)) { return false; } return true; } Best regards, Lars More information:
|
2008-10-13 05:54:47
| 1,223,890,000
|
verified fixed
|
6d5c190
| 1,223,980,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaUIMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/GenerateHashCodeEqualsDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/GenerateHashCodeEqualsAction.java
|
JDT
|
999
| 250,660
|
Bug 250660 [introduce factory] destroys anonymous inner classes
|
Build ID: M20080911-1700 Steps To Reproduce: On this example code public class Foo { public Foo() { } public void foo() { new Foo() { public void foo() { } }; } } apply the "introduce factory" refactoring to the Foo constructor. The result is a call to createFoo in the foo method - the overridden foo method is lost! More information: This behavior obviously is quite dangerous, as it can change the behavior of a system dramatically and doesn't even produce any kind of warning. Basically, with this bug this refactoring shouldn't be relied upon at all.
|
2008-10-13 11:35:17
| 1,223,910,000
|
verified fixed
|
97074fe
| 1,223,920,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceFactory/Bugzilla/250660/HasAnonymous.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceFactory/Bugzilla/250660/HasAnonymous_out.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/IntroduceFactoryTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceFactoryRefactoring.java
|
JDT
|
1,000
| 250,629
|
Bug 250629 [content assist] Selected proposal kinds not restored
|
I20081007-1600 + latest plug-in export - new workspace - select all Java content assist proposal kinds, except "Java Proposals" - restart Eclipse => all 3 Java categories disabled, content assist broken
|
2008-10-13 06:57:46
| 1,223,900,000
|
verified fixed
|
d369e14
| 1,223,910,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/CompletionProposalComputerRegistry.java
|
JDT
|
1,001
| 250,149
|
Bug 250149 [call hierarchy] should expand read references to fields
| null |
2008-10-08 14:12:04
| 1,223,490,000
|
resolved fixed
|
3fcfd8b
| 1,223,490,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/callhierarchy/CallerMethodWrapper.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/callhierarchy/MethodWrapper.java
|
JDT
|
1,002
| 249,620
|
Bug 249620 [preferences] Provide UI for 'no strictly compatible JRE available' problem severity
| null |
2008-10-03 12:00:31
| 1,223,050,000
|
resolved fixed
|
44f6661
| 1,223,310,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaBuildConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java
|
JDT
|
1,003
| 249,535
|
Bug 249535 [compiler] Consider disabling the syncOverride warning/error by default
| null |
2008-10-02 15:18:21
| 1,222,980,000
|
verified fixed
|
90caa28
| 1,223,300,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/ModifierCorrectionsQuickFixTest.java
|
JDT
|
1,004
| 249,155
|
Bug 249155 [common navigator] Potential StackOverflow in JavaNavigatorContentProvider
|
Build ID: org.eclipse.jdt.ui_3.4.0.v20080603-2000.jar Steps To Reproduce: We are using the common navigation framework in our product. In one instance of the navigator, we passed another project as input (the tree gets partially shaped by this project). However, we hit some problems with theJavaNavigatorContentProvider. This is the stack trace which overflows: .... org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).isParent(java.lang.Object, java.lang.Object) line: 922 org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).isParent(java.lang.Object, java.lang.Object) line: 927 org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).isParent(java.lang.Object, java.lang.Object) line: 927 org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).isParent(java.lang.Object, java.lang.Object) line: 927 org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).isParent(java.lang.Object, java.lang.Object) line: 927 org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).isParent(java.lang.Object, java.lang.Object) line: 927 org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).postRefresh(java.lang.Object, int, java.lang.Object, java.util.Collection) line: 903 org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).handleAffectedChildren(org.eclipse.jdt.core.IJavaElementDelta, org.eclipse.jdt.core.IJavaElement, java.util.Collection) line: 745 org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).processDelta(org.eclipse.jdt.core.IJavaElementDelta, java.util.Collection) line: 700 org.eclipse.jdt.internal.ui.navigator.JavaNavigatorContentProvider(org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider).elementChanged(org.eclipse.jdt.core.ElementChangedEvent) line: 126 org.eclipse.jdt.internal.core.DeltaProcessor$3.run() line: 1545 From what I can tell, this content provider does not like us using the project as input (the project does NOT have the java nature... it is a simple project with one proprietary nature). A project is being added to the workspace when the problem starts. Both "root" and "affectedElement" in the postRefresh() method are the JavaModel root. It then tries to determine if the input is a child, given the root. When getParent() is called for the input (the non-Java project), the code gets the parent for the project, which is the JavaModel root. It then assumes (I think) that the JavaModel relates to the viewer input's "real input". This assumption is not true for the input we are sending to the viewer. In the end, it thinks that the parent of the element is itself, which ends up causing the stack overflow. Perhaps more error checking should be done in here? If the element IS the input, then it shouldn't have any parent. Likewise, if the code determines that the parent of an object is the exact same object, then it must know that something is wrong. More information:
|
2008-09-30 13:55:26
| 1,222,800,000
|
verified fixed
|
bc1f55a
| 1,223,300,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaNavigatorContentProvider.java
|
JDT
|
1,005
| 249,549
|
Bug 249549 [quick fix] bad proposal for abstract modifier before constructors in abstract classes
|
Build ID: M20080911-1700 Steps To Reproduce: 1. Create a class like this: abstract class Test { public abstract Test(); } of course this code is wrong. But Eclipse proposes two quick fixes: "Add body", which is correct and "Add 'abstract' modifier", which does not make any sense. When using this one, the result is still wrong, but with two 'abstract' modifiers and the same quick fix proposals. More information: this bug is similar to #208655
|
2008-10-02 17:34:06
| 1,222,980,000
|
resolved fixed
|
4ade8bf
| 1,223,020,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/ModifierCorrectionSubProcessor.java
|
JDT
|
1,006
| 170,879
|
Bug 170879 [paste] paste patch from clipboard into package explorer
|
I20070109-1805 I would like to be able to past a patch which I have in the clipboard into the package explorer. Pasting would apply the patch. This would be a shortcut for Team>Apply Patch...>Clipboard>Finish. Thanks (Not sure if CVS is the correct component for this request)
|
2007-01-18 04:10:17
| 1,169,110,000
|
verified fixed
|
66b00c6
| 1,222,900,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/PasteAction.java
|
JDT
|
1,007
| 249,342
|
Bug 249342 [build path] IndexOutOfBoundsException attempting to remove last build path entry
| null |
2008-10-01 11:57:43
| 1,222,880,000
|
verified fixed
|
73b5ba6
| 1,222,880,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/buildpath/CPJavaProject.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/OutputLocationDialog.java
|
JDT
|
1,008
| 201,587
|
Bug 201587 [quick fix] change type does not fully qualify conflicting type
|
I20070828-0800 Given: package test2; public class E02 {} package test1; public class E01 { private class E02 {} private E02 e02; public E01() { e02= new test2.E02(); } } 1. Go to compile error 2. Ctrl-1 3. 'Change type of e02 to E02' Is: test2.E02 is imported Should: Field type should be fully qualified
|
2007-08-29 11:27:08
| 1,188,400,000
|
resolved fixed
|
296d4c7
| 1,222,840,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/TypeMismatchQuickFixTests.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/TypeChangeCorrectionProposal.java
|
JDT
|
1,009
| 243,179
|
Bug 243179 [quick fix] "Change type" uses "? extends Number" as variable type in generic enhanced for loop
|
Build ID: I20080617-2000 (3.4.0) Steps To Reproduce: Please apply the quickfix, and see the illegal result. ---------------------- Bug.java --------------------- import java.util.*; class Bug { { ArrayList<Number>list=new ArrayList(); HashSet<Short>set=new HashSet(); for(AbstractCollection<Number>bunch:Arrays.asList(list,set)); } }
|
2008-08-05 11:27:35
| 1,217,950,000
|
resolved fixed
|
6b470cd
| 1,222,820,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/TypeMismatchQuickFixTests.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/TypeMismatchSubProcessor.java
|
JDT
|
1,010
| 248,954
|
Bug 248954 NPE synchronizing an existing workspace
|
Using M20080827-2000, I got: Caused by: java.lang.NullPointerException at org.eclipse.jdt.internal.ui.model.JavaSynchronizationContentProvider.asJavaProject(JavaSynchronizationContentProvider.java:149) at org.eclipse.jdt.internal.ui.model.JavaSynchronizationContentProvider.convertToJavaElements(JavaSynchronizationContentProvider.java:168) at org.eclipse.jdt.internal.ui.model.JavaSynchronizationContentProvider.interceptAdd(JavaSynchronizationContentProvider.java:763) at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.interceptAdd(SafeDelegateTreeContentProvider.java:224) at org.eclipse.ui.internal.navigator.NavigatorPipelineService.pipelineInterceptAdd(NavigatorPipelineService.java:124) at org.eclipse.ui.internal.navigator.NavigatorPipelineService.interceptAdd(NavigatorPipelineService.java:81) at org.eclipse.ui.navigator.CommonViewer.add(CommonViewer.java:242) at org.eclipse.ui.model.WorkbenchContentProvider$2.run(WorkbenchContentProvider.java:265) at org.eclipse.ui.model.WorkbenchContentProvider.runUpdates(WorkbenchContentProvider.java:129) at org.eclipse.ui.model.WorkbenchContentProvider.access$1(WorkbenchContentProvider.java:126) at org.eclipse.ui.model.WorkbenchContentProvider$1.run(WorkbenchContentProvider.java:115) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) ... 43 more while I tried to synchronize an existing workspace. No steps to reproduce, but looking at the code, asJavaProject(..) can be called with null and null is not handled.
|
2008-09-29 11:22:35
| 1,222,700,000
|
verified fixed
|
a9ec42a
| 1,222,710,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/model/JavaSynchronizationContentProvider.java
|
JDT
|
1,011
| 248,899
|
Bug 248899 [jar exporter] Jar export doesn't include files under META-INF
|
In Eclipse 3.4 (and since at least 3.1), if I create a text file in META-INF/services, and export a jar file, it will get included in the jar file as would be expected. In Eclipse 3.5 M2, this is broken. Whether or not I check the file it does not get included in the jar. Maybe there is some different combination of options that would do it, but at least it has changed since 3.4 and I was not able to figure out how to make it work in 3.5. I'm coding severity as "major" because putting files into META-INF/services is the way that the Java declarative services API works, so this makes it impossible to generate jar files that contain, for instance, annotation processors. To repro: 1. Create a new workspace and add a new Java project. 2. Add a java class, say, p.P 3. Add a folder META-INF/services, under the src folder. 4. In that folder, create a text file named javax.annotation.processing.Processor, with some text contents. 5. File -> Export -> Java -> Jar file 6. Walk through the wizard, making sure that the file in META-INF/services is selected (it will be by default). Save the jar file to a workspace folder named "export". Save the .jardesc in the project root. Finish. 7. Open the newly-created jar file. Note that it contains p.P, but does NOT contain the file in META-INF/services. 8. Also, right-click the .jardesc. Note that there is no "Open the jar description wizard" item, as there used to be. There's still a "create jar file" item, and clicking the .jardesc does open the wizard, but there used to be a separate menu item. The change was confusing, although I don't necessarily disagree with it.
|
2008-09-29 03:57:13
| 1,222,680,000
|
verified fixed
|
fafd568
| 1,222,690,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarFileExportOperation.java
|
JDT
|
1,012
| 248,254
|
Bug 248254 [refactoring] 'Add final modifier' save action collides with 'rename' refactoring
|
I found a collision between the 'add final modifier to local variables' save action and the refactorings 'extract local variable' followed by 'rename'. To reproduce: 1. Activate 'Add final modifier to local variables' save action 2. In a method, write System.out.println("foo"); 3. Save the file 4. Select "foo" and apply 'extract local variable' refactoring. This yields String x = "foo"; System.out.println(x); 5. Select the x in the first line and hit ALT+SHIFT+R ('rename' refactoring) 6. Type something short as new variable name, e.g. xy, and hit ENTER -> Error message: A local variable declaration or reference must be selected to activate this refactoring
|
2008-09-23 07:25:09
| 1,222,170,000
|
verified fixed
|
2c17365
| 1,222,530,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameLinkedMode.java
|
JDT
|
1,013
| 170,431
|
Bug 170431 [typing] switch ... default not indented correctly
|
Build ID: 3.2.0 Steps To Reproduce: 1. Create a simple java class 2. Add a switch statement with a default case 3. In the default case add 3 lines of code. 4. Press Ctrl+A to select all the class 5. Press Ctrl+I to indent the class 6. The lines of the default statement, excepted the first, are not correctly indented. More information:
|
2007-01-15 03:13:50
| 1,168,850,000
|
resolved fixed
|
5147d51
| 1,222,420,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaIndenter.java
|
JDT
|
1,014
| 248,659
|
Bug 248659 [implementation] Deleting source folder leaks file handle
|
Current HEAD DeletePackageFragmentRootChange#getFileLength acquires an InputStream from IFile. JavaDoc explicitly says that the caller is responsible for closing the stream.
|
2008-09-25 17:16:47
| 1,222,380,000
|
resolved fixed
|
3bf88e4f
| 1,222,420,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/changes/DeletePackageFragmentRootChange.java
|
JDT
|
1,015
| 248,660
|
Bug 248660 [implementation] AbstractJavaCompletionProposal leaks file handle
|
Current HEAD AbstractJavaCompletitionProposal#getCSSStyles forgets to close the input stream while reading the css file.
|
2008-09-25 17:24:10
| 1,222,380,000
|
resolved fixed
|
e7f1120
| 1,222,420,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/AbstractJavaCompletionProposal.java
|
JDT
|
1,016
| 227,559
|
Bug 227559 Need API to process StyledString
|
I20080415-0800. In order to support BIDI we need to be able to run the string through the TextProcessor and adjust the styles. Simplest would be to get proccessText(*) methods that do the same as TextProcessor.process(*).
|
2008-04-17 10:30:46
| 1,208,440,000
|
verified fixed
|
0f9d295
| 1,222,330,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/util/Strings.java
|
JDT
|
1,017
| 29,379
|
Bug 29379 [typing] Auto-inserted bracket '}' crosses parentheses scope
|
Suppose there is a method void foo (String []); if in some place you want ivoke the method creating the array on fly, and suppose to type something like: foo (new String [] {"x"}) automatic parentheses and curved brackets insertion makes your code looking as foo (new String [] {<cursor here>) } i.e closing curved bracket goes out of the method parameter parentheses...
|
2003-01-13 08:46:00
| 1,042,470,000
|
resolved fixed
|
bd6b5b9
| 1,222,100,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaAutoIndentStrategy.java
|
JDT
|
1,018
| 164,449
|
Bug 164449 [content assist] Only call ICodeAssist.codeComplete(...) once
|
3.2 and 3.3 M3 JDT Text calls JDT Core code assist twice on each invocation. This happens because the final proposal list is computed by several different completion processors. Two of them (the "no type" and the "other proposals" processor) call ICodeAssist.codeComplete(...). Note that this is not a bug but works as designed since we eat our own dog food by contributing the processor via extension point. We could however try to improve the performance by providing an internal processor that only combines the two and only calls JDT Core once.
|
2006-11-14 06:07:04
| 1,163,500,000
|
resolved fixed
|
d5bd292
| 1,221,750,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaAllCompletionProposalComputer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaCompletionProposalComputer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaNoTypeCompletionProposalComputer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaTypeCompletionProposalComputer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/PreferenceConstants.java
|
JDT
|
1,019
| 247,547
|
Bug 247547 [content assist] prefix complete casted method proposals
| null |
2008-09-16 15:18:20
| 1,221,590,000
|
resolved fixed
|
6c760f1
| 1,221,640,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/MethodInsertCompletionTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaMethodCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/LazyJavaCompletionProposal.java
|
JDT
|
1,020
| 8,624
|
Bug 8624 [misc] Double click should auto select comment
|
Stable Build: 20020125 It should be possible to double click at the start or end of a long comment (i.e. /* or */) and have it automatically select the entire comment. Thanks.
|
2002-01-28 14:56:18
| 1,012,250,000
|
verified fixed
|
c25d92e
| 1,221,490,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JavaDoubleClickSelectorTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesFileSourceViewerConfiguration.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaDoubleClickSelector.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaStringDoubleClickSelector.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavadocDoubleClickStrategy.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/PartitionDoubleClickSelector.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/JavaSourceViewerConfiguration.java
|
JDT
|
1,021
| 243,163
|
Bug 243163 [jar exporter] export directory entries in "Runnable JAR File"
|
Please add an option to "add directory entries" to the new "Runnable JAR File" export. This option already exists in the older "JAR File" export. I ran into a problem where Jar-ing some existing projects with Ganymede caused getClass().getClassLoader().getResource( path ) to return null due to the fact that the empty directory entries had not been exported to the Jar.
|
2008-08-05 09:49:00
| 1,217,940,000
|
resolved fixed
|
e1d1d82
| 1,221,470,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/jarexport/FatJarExportTests.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/FatJarPackageWizard.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/JarWriter4.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/jarpackager/JarWriter3.java
|
JDT
|
1,022
| 38,297
|
Bug 38297 [EditorMgmt] Open Jar Packager when double-clicking on .jardesc file
|
I have a file called SillyBean.jardesc in my workspace, that was created by using the Export Jar --> Save Description facility. The content looks like this: <?xml version="1.0" encoding="UTF-8"?> <jardesc> <jar path="/home/markus/SillyBean.jar"/> <options overwrite="true" compress="false" exportErrors="false" exportWarnings="true" saveDescription="true" descriptionLocation="/SillyBean/SillyBean.jardesc" useSourceFolders="false" buildIfNeeded="true"/> <manifest manifestVersion="1.0" usesManifest="true" reuseManifest="false" saveManifest="false" generateManifest="false" manifestLocation="/SillyBean/META-INF/MANIFEST.MF"> <sealing sealJar="false"> <packagesToSeal/> <packagesToUnSeal/> </sealing> </manifest> <selectedElements exportClassFiles="true" exportJavaFiles="false"> <javaElement handleIdentifier="=SillyBean/src"/> </selectedElements> </jardesc> Whenever I try "Open" or "Open In... Jar Description Editor" the file opens in the normal text editor. I cannot edit the description, still it is possible to build the jar by "Create Jar". Seems that wizard cannot read it's own generated xml files in some circumstances. I saw this on Eclipse 2.1 on Windows 2000 and SuSE LINUX 8.2 GTK.
|
2003-05-31 11:24:22
| 1,054,390,000
|
resolved fixed
|
530b217
| 1,221,220,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarPackagerMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/OpenJarExportWizardEditorLauncher.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/OpenJarPackageWizardActionDelegate.java
|
JDT
|
1,023
| 246,635
|
Bug 246635 [build path] Add project screen shows added projects
|
Build ID: I20080617-2000 Steps To Reproduce: 1. Create many projects on workspace 2. Open the wizard to create a new Java Project 3. Put the name of the project 4. Select the "Projects" tab on "Java Settings" 5. Press the button to add new projects 6. Mark many projects and press ok 7. Press the button to add new projects The projects added should not be visible again but some projects appear on screen. More information:
|
2008-09-08 15:24:07
| 1,220,900,000
|
resolved fixed
|
46e36a1
| 1,220,980,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/ProjectsWorkbookPage.java
|
JDT
|
1,024
| 245,257
|
Bug 245257 [compiler] Allow to suppress fall-through warning
|
R3.4. The fall through warning for switch statements is very good and we have it enabled. There is however some good/valid code were this warning is wrong and we would like to have a flag to ignore that. I suggest to add a $FALL-THROUGH$ (like the NON-NLS) tag that tells the compiler that fall through is intended by the programmer. Note that our source has to be 1.4 compliant and hence we cannot use @suppressWarning.
|
2008-08-26 10:29:54
| 1,219,760,000
|
verified fixed
|
fdb4b0d
| 1,220,960,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java
|
JDT
|
1,025
| 246,501
|
Bug 246501 [content assist] ArrayIndexOutOfBoundsException is thrown by SignatureUtil.getUpperBound
|
Code assists fails to complete normally. Using the following code, place the cursor after the 'S' and before the ')' on the line beginning System.out... package foo; public class Bar { public static void main(String[] args) { double[] da = new double [ 0 ]; System.out.println("da.getClass().getSuperclass() = " + da.getClass().getS); } } Use Ctrl + Space to open code assist and the following error occurs: !ENTRY org.eclipse.ui 4 4 2008-09-07 18:34:50.453 !MESSAGE "Content Assist" did not complete normally. Please see the log for more information. !ENTRY org.eclipse.ui 4 0 2008-09-07 18:34:50.453 !MESSAGE 17 !STACK 0 java.lang.ArrayIndexOutOfBoundsException: 17 at org.eclipse.jdt.internal.corext.template.java.SignatureUtil.getUpperBound(SignatureUtil.java:112) at org.eclipse.jdt.ui.text.java.CompletionProposalLabelProvider.createMethodProposalLabel(CompletionProposalLabelProvider.java:271) at org.eclipse.jdt.ui.text.java.CompletionProposalLabelProvider.createStyledLabel(CompletionProposalLabelProvider.java:536) at org.eclipse.jdt.internal.ui.text.java.LazyJavaCompletionProposal.computeDisplayString(LazyJavaCompletionProposal.java:245) at org.eclipse.jdt.internal.ui.text.java.LazyJavaCompletionProposal.getStyledDisplayString(LazyJavaCompletionProposal.java:224) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.handleSetData(CompletionProposalPopup.java:824) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$24(CompletionProposalPopup.java:814) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$3.handleEvent(CompletionProposalPopup.java:580) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Table.checkData(Table.java:928) at org.eclipse.swt.widgets.Table.wmNotifyChild(Table.java:6292) at org.eclipse.swt.widgets.Control.wmNotify(Control.java:4718) at org.eclipse.swt.widgets.Composite.wmNotify(Composite.java:1756) at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:4348) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3841) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:337) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1565) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1937) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4541) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2273) at org.eclipse.swt.widgets.Table.callWindowProc(Table.java:333) at org.eclipse.swt.widgets.Table.callWindowProc(Table.java:199) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3877) at org.eclipse.swt.widgets.Table.windowProc(Table.java:5476) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4541) at org.eclipse.swt.internal.win32.OS.UpdateWindow(Native Method) at org.eclipse.swt.widgets.Decorations.setVisible(Decorations.java:1378) at org.eclipse.swt.widgets.Shell.setVisible(Shell.java:1764) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.displayProposals(CompletionProposalPopup.java:1189) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$23(CompletionProposalPopup.java:1154) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:497) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:479) at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1664) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:177) at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:471) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:822) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:511) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:126) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1184) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1012) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1040) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1036) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1352) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3894) at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:341) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3787) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:337) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4528) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:2273) at org.eclipse.swt.internal.BidiUtil.windowProc(BidiUtil.java:657) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2370) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3420) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) 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:193) 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:382) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
|
2008-09-07 18:40:22
| 1,220,830,000
|
resolved fixed
|
86332c1
| 1,220,880,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/SignatureUtil.java
|
JDT
|
1,026
| 45,186
|
Bug 45186 [UI Guidelines] Double clicking a view does not activate editor
|
Double click on the outline view and the corresponding location in the file is selected but the editor is not active. This behavior differes from the package explorer view with "show members in package explorer" selected. When show memebers is selected, double clicking on the member selects the member in the editor, and makes the editor active. The outline view should exhibit the same behavior.
|
2003-10-19 22:47:41
| 1,066,620,000
|
resolved fixed
|
66d8dda
| 1,220,550,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/browsing/JavaBrowsingPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyUI.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/OpenLocationAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaOutlinePage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/MethodsViewer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/SubTypeHierarchyViewer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/SuperTypeHierarchyViewer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TraditionalHierarchyViewer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyViewPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyViewer.java
|
JDT
|
1,027
| 244,423
|
Bug 244423 Upgrade to JUnit 4.5
| null |
2008-08-18 09:15:57
| 1,219,070,000
|
resolved fixed
|
a17e79a
| 1,220,520,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JunitPreferenceInitializer.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/BuildPathSupport.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/buildpath/BuildPathSupport.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/JunitPreferenceInitializer.java
|
JDT
|
1,028
| 246,070
|
Bug 246070 [content assist] Multiline method invocation with comment at the end of line causes invalid parameters content assist behaviour
|
Build ID: I20080617-2000 Steps To Reproduce: 1. Put in .java these example methods (assume we have here many parameters so wrapping is necessary): private void test(int p1, int p2, int p3, int p4) {} private void invokeTest() { test(1, 2, 3, 4); test(1, 2, // comment e.g. $NON-NLS-like 3, 4); } 2. Invoke parameter content assist (ctrl-shift-space) at first test() method invocation without comment and you'll see hint with parameters' names and current cursor position at which parameter (bolded) 3. Go with right arrow to next parameters, bold in hint will follow even on the next line 4. Invoke content assist at second test method with comment - bold will stop at parameter p3 because of comment. More information: Really annoying, especially after externalize strings where many such comments ($NON-NLS) appeared.
|
2008-09-03 07:24:43
| 1,220,440,000
|
verified fixed
|
2338c38
| 1,220,520,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaParameterListValidator.java
|
JDT
|
1,029
| 243,712
|
Bug 243712 [preferences] Inconsistent setting of Java Compiler compliance level in preferences.
|
I have Eclipse with jre (JRE 1.6) in eclipse/ directory. When starting for first time in new workspace it sets Window -> Preferences -> Java -> Compiler -> Compiler Compliance level to 1.6 But when I press "Restore Defaults" on the same preference page, it reverts to 1.4 value. This behaviour seems inconsistent specially for products based on Eclipse+JDT that normally ship with their JREs.
|
2008-08-11 03:55:53
| 1,218,440,000
|
verified fixed
|
a8d76f8
| 1,220,460,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ComplianceConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.java
|
JDT
|
1,030
| 239,735
|
Bug 239735 [quick fix][preferences] quick fix should use fully qualified type if already fully qualified
|
Build ID: I20080617-2000 Steps To Reproduce: Example. Create a class called Timer and a method. Start typing in the method body: new Timer Press Ctrl-Space Select java.util.Timer i.e. you have new java.util.Timer Complete to new java.util.Timer(); Press Ctrl-1 for Quickfix Select Assign statment to new local variable which gives the following uncompilable piece of code. package mypackage; import java.util.Timer; public class Timer { public static void main(String[] args) { Timer timer = new java.util.Timer(); } } More information:
|
2008-07-06 17:22:39
| 1,215,380,000
|
resolved fixed
|
b1ac419
| 1,220,450,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AssistQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/AssignToVariableAssistProposal.java
|
JDT
|
1,031
| 245,250
|
Bug 245250 [quick fix] Quick fix for missing synchronized modifier
| null |
2008-08-26 10:10:14
| 1,219,760,000
|
resolved fixed
|
44307a3
| 1,220,340,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/ModifierCorrectionsQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/ModifierCorrectionSubProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/QuickFixProcessor.java
|
JDT
|
1,032
| 233,982
|
Bug 233982 Update JDT test framework to Java 1.6 (rtstubs.jar, etc.)
|
Update the JDT test framework to Java 1.6 (rtstubs.jar, etc.)
|
2008-05-26 12:50:34
| 1,211,820,000
|
resolved fixed
|
2779a46
| 1,220,270,000
|
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/Java16Setup.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/RefactoringTestSetup.java org.eclipse.jdt.ui.tests/test plugin/org/eclipse/jdt/testplugin/JavaProjectHelper.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/binary/StubCreator.java
|
JDT
|
1,033
| 245,777
|
Bug 245777 [refactoring] TypeContextChecker creates stub with syntax error
|
Build ID: I20080617-2000 Method TypeContextChecker#appendTypeParameters fails to insert the closing '>'. When the result is passed to the parser (I observed this in resolveSuperInterfaces) this unnecessarily requires syntax recovery to luckily get the intended result.
|
2008-08-30 18:43:58
| 1,220,140,000
|
resolved fixed
|
f701890
| 1,220,260,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/TypeContextChecker.java
|
JDT
|
1,034
| 233,953
|
Bug 233953 [implementation] Activating an editor can trigger two AST creations
|
3.4 RC2. We have a hole in our code where editor activation can lead in the creation of two ASTs.
|
2008-05-26 09:00:42
| 1,211,810,000
|
resolved fixed
|
9d27d8a
| 1,220,010,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ASTProvider.java
|
JDT
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.