id
int64 1
6.5k
| bug_id
int64 2.03k
426k
| summary
stringlengths 9
251
| description
stringlengths 1
32.8k
⌀ | report_time
stringlengths 19
19
| report_timestamp
int64 1B
1.39B
| status
stringclasses 6
values | commit
stringlengths 7
9
| commit_timestamp
int64 1B
1.39B
| files
stringlengths 25
32.8k
| project_name
stringclasses 6
values |
|---|---|---|---|---|---|---|---|---|---|---|
1,835
| 181,830
|
Bug 181830 Refactor -> Rename now has confusing/problematic workflow
|
3.3 M6 The Refactor->Rename based on a text selection in a java editor now has a very strange workflow. Issue 1: It results in a mini yellow in place chooser appearing over the text in question. I don't think I've seen this elsewhere in our UI. A problem is that its a strange UI control to result because instead of it appearing where your mouse was on menu select, its where the source text is. This makes for an odd workflow. Issue 2: Its possible that a selection results in a dialog. This is another odd workflow that we don't have elsewhere as I recall. Issue 3: It has number of options, each one with a quick key suggestion (e.g. "Enter", "Cntrl-Enter". When I hit these keys nothing happens (perhaps this is a different bug, I recall there's one being looked at where the keys go to the wrong shell). Issue 4: I have to carefully select the right hyperlink from the list, this takes a lot of precision which is odd considering the simplicity of the task (I just want the rename dialog). Issue 5: It seems only one option, "Preview" does anything interesting. I don't understand the other options since I never get to fill in what I want it renamed to. Issue 6: Once you select "Rename", even if you do not do select any of the options (e.g. click away), you retain a blue outline around the word in question, such that anytime thereafter that you click in there you get the little yellow rename option dialog. Selection of text doesn't make it go away, only focus loss of the editor. I'm sure this was all done for a reason but I don't understand what it is. The old behaviour of just getting the rename dialog seemed perfectly good, and this new way isn't presenting any advantages to me, only problems.
|
2007-04-10 15:30:21
| 1,176,230,000
|
resolved fixed
|
558cc1d
| 1,177,690,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameInformationPopup.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/ReorgMessages.java
|
JDT
|
1,836
| 184,444
|
Bug 184444 [package explorer] 'Show In > Package Explorer' broken for properties file
|
I20070427-0010 Had ReorgMessages.properties open in editor and pressed Alt+Shift+W, P => Package Explorer beeps but does not show file. Works for .java files.
|
2007-04-27 10:55:04
| 1,177,690,000
|
resolved fixed
|
eceda1d
| 1,177,690,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerPart.java
|
JDT
|
1,837
| 173,189
|
Bug 173189 [search] IllegalArgumentException when searching for references
|
Build id: I20070206-0010 1. Select a method 2. Select "References > Working Set..." 3. Don't select any working sets in the dialog, but press OK: java.lang.IllegalArgumentException: data must not be null at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.<init>(JavaSearchQuery.java:61) at org.eclipse.jdt.ui.actions.FindAction.performNewSearch(FindAction.java:284) at org.eclipse.jdt.ui.actions.FindAction.run(FindAction.java:277) at org.eclipse.jdt.ui.actions.FindReferencesAction.run(FindReferencesAction.java:97) at org.eclipse.jdt.ui.actions.FindAction.run(FindAction.java:221) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:268) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:244) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3490) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3104) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2257) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2221) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2096) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:456) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:451) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:101) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:146) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:476) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:416) at org.eclipse.equinox.launcher.Main.run(Main.java:1124) at org.eclipse.equinox.launcher.Main.main(Main.java:1099)
|
2007-02-06 16:53:25
| 1,170,800,000
|
resolved fixed
|
3cc8ca3
| 1,177,690,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/SelectWorkingSetAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/JavaSearchScopeFactory.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FindAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FindDeclarationsInHierarchyAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FindDeclarationsInWorkingSetAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FindImplementorsInWorkingSetAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FindReferencesAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FindReferencesInHierarchyAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FindReferencesInWorkingSetAction.java
|
JDT
|
1,838
| 162,541
|
Bug 162541 [misc] save participants not called upon 'Save As'
|
N20061027-0010 The save participants are not called upon 'Save As'.
|
2006-10-27 06:01:07
| 1,161,940,000
|
resolved wontfix
|
5236be7
| 1,177,660,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CleanUpPostSaveListener.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitDocumentProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/saveparticipant/IPostSaveListener.java
|
JDT
|
1,839
| 102,287
|
Bug 102287 [refactoring] [dcr] Implement "Introduce Parameter Object"
| null |
2005-06-30 06:19:28
| 1,120,130,000
|
resolved fixed
|
df38451
| 1,177,610,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testBodyUpdate/in/TestBodyUpdate.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testBodyUpdate/out/TestBodyUpdate.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testDelegateCreation/in/TestDelegateCreation.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testDelegateCreation/out/TestDelegateCreation.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testImportAddEnclosing/in/TestImportAddEnclosing.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testImportAddEnclosing/in/TestImportAddEnclosingCaller.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testImportAddEnclosing/out/TestImportAddEnclosing.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testImportAddEnclosing/out/TestImportAddEnclosingCaller.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testImportAddTopLevel/in/TestImportAddTopLevel.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testImportAddTopLevel/in/TestImportAddTopLevelCaller.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testImportAddTopLevel/out/TestImportAddTopLevel.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testImportAddTopLevel/out/TestImportAddTopLevelCaller.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testImportAddTopLevel/out/TestImportAddTopLevelParameter.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testReorderGetter/in/TestReorderGetter.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testReorderGetter/out/TestReorderGetter.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testSimpleEnclosing/in/TestSimpleEnclosing.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testSimpleEnclosing/out/TestSimpleEnclosing.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testVarArgsNotReordered/in/TestVarArgsNotReordered.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testVarArgsNotReordered/out/TestVarArgsNotReordered.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testVarArgsReordered/in/TestVarArgsReordered.java org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameterObject/testVarArgsReordered/out/TestVarArgsReordered.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/ParameterInfo.java 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/RefactoringCoreMessages.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringExecutionStarter.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/TypeContextChecker.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/BodyUpdater.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ChangeSignatureRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/IDefaultValueAdvisor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/IntroduceParameterObjectRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ParameterObjectFactory.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/RefactoringMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/ActionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/IntroduceParameterObjectAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/RefactorActionGroup.java
|
JDT
|
1,840
| 96,490
|
Bug 96490 [linked mode][navigation] Consider linked position boundaries as word stops
|
Now that "Rename in File" quickfix no longer selects the current token, I am trying to do it manually by typing CTRL+LEFT, CTRL+SHIFT+RIGHT. The problem with this is that it includes the whitespace coming after the variable, which is outside of the linked-edit box, and overwriting deactives the linked edit mode, which is not what I want. It should be easier to select a word. Perhaps "Next Word" should go to the end of the current word instead of the beginning of the next. Or, the linked edit box should be considered a word boundary.
|
2005-05-24 14:45:39
| 1,116,960,000
|
resolved fixed
|
2d6737a
| 1,177,610,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java
|
JDT
|
1,841
| 183,925
|
Bug 183925 [rename] In-place refactoring is vulnerable to backspace
|
Build I20070418-1012. Consider the following code (using pipe character to materialize the insertion point): public class X { void foo() { String s| = ""; System.out.println(s); } } Place the insertion point behind s in the declaration and press Alt-Shit-R. The in-place refactoring hover appears. Press backspace once. s is erased and an error marker appears. The code looks like: public class X { void foo() { String | = ""; System.out.println(s); } } Press backspace a second time. No visible change except that the refactoring hover gets away and the code now looks like: public class X { void foo() { String| = ""; System.out.println(); } } Especially, no change around the System.out.println(); line. Add a whitespace and s again... And you get: public class X { void foo() { String s| = ""; System.out.println(); } } The meaning of the code changed, unnoticed. Note that I detected the behavior on a case where many compile errors resulted from the blanking of the variable name at the other places it was used. This is a bit less annoying in such cases because you get a strong signal that you'd better revert the file. But still, it happens quite often to me to strike backspace just one extra time while renaming, and the current behavior does not help me. Also, the behavior on a longer variable name is not that much better: backspace once more than needed, and the refactoring happens sooner than expected, leaving you no chance to reinsert characters in front of the name. Maybe blocking extra backspaces in some way would help?
|
2007-04-25 02:09:15
| 1,177,480,000
|
resolved fixed
|
e41b372
| 1,177,610,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameLinkedMode.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LinkedNamesAssistProposal.java
|
JDT
|
1,842
| 183,093
|
Bug 183093 [build path] unable to create a src folder if it already exists in the build path
|
Build ID: M20070212-1330 Steps To Reproduce: The export to archive option does not export directories which are empty. This causes issues in cases where the directory is part of the src path. Importing such a projects results in errors in the problems view. Project web is missing required source folder: 'src' project cannot be built until build path errors are resolved At this point if the user switches to the project explorer view, right click on java resources and selects the option to create a new source folder named src an error message is displayed the folder is already a source folder when it does not physically exist The folder is already a source folder. create a new web project export the project to an archive delete the project along with files import the archived project from the archive notice the errors in the problems view switches to the project explorer view right click on java resources and select the option to create a new source folder called src this will fail More information:
|
2007-04-18 20:54:10
| 1,176,940,000
|
resolved fixed
|
54d9256
| 1,177,600,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/AddSourceFolderWizardPage.java
|
JDT
|
1,843
| 182,716
|
Bug 182716 [IDE] Improve 'New' menu regarding projects
| null |
2007-04-17 05:25:13
| 1,176,800,000
|
verified fixed
|
b2b15dd
| 1,177,600,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaHierarchyPerspectiveFactory.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaPerspectiveFactory.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/browsing/JavaBrowsingPerspectiveFactory.java
|
JDT
|
1,844
| 143,025
|
Bug 143025 [build path] Derived attribute on default output folder of Java project doesn't work
|
When I create a new Java project, I configure it with separate source and output folders (src and bin). The code that creates the output folder (BuildPathsBlock.flush) sets the derived attribute on the folder, but when I check the folder's properties later, the folder is not marked as derived. This means that when I shared the project (commit to CVS), the bin folder is going to be added to the repository. If I create Main.java in the default (unnamed) package, the corresponding class file, "project/bin/Main.class" is marked as derived. If I create an empty, top-level package (e.g. "dummy"), the corresponding directory, "project/bin/dummy", is marked as derived. My expectation was that the derived attribute would be set in the properties of the bin folder, and that the folder would not be shared with CVS. Setting the component to UI, but I don't have any confidence that is correct. FYI, tested with 3.2 RC4.
|
2006-05-22 13:45:57
| 1,148,320,000
|
verified fixed
|
692d9cd
| 1,177,600,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/util/CoreUtility.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/JavaProjectWizardSecondPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/BuildPathsBlock.java
|
JDT
|
1,845
| 184,197
|
Bug 184197 New Java Project wizard should filter out aggregate working sets
|
HEAD The New Java Project wizard should filter out aggregate working sets. It's probably best to filter out all non-editable sets, see IWorkingSet#isEditable().
|
2007-04-26 06:36:54
| 1,177,580,000
|
resolved fixed
|
aedaecd
| 1,177,600,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/SimpleWorkingSetSelectionDialog.java
|
JDT
|
1,846
| 184,193
|
Bug 184193 [browsing] Filtering empty parent packages no longer working in Packages view
|
I20070424-0930 In the Java Browsing perspective, the Packages view doesn't filter empty parent packages any longer.
|
2007-04-26 06:19:32
| 1,177,580,000
|
resolved fixed
|
afa0429
| 1,177,580,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/browsing/PackageViewerWrapper.java
|
JDT
|
1,847
| 170,239
|
Bug 170239 [extract superclass] IllegalArgumentException during Extract Superclass refactor
|
This class will produce an IllegalArgumentException after selecting methods to be removed from the subclass: import java.io.FilterReader; import java.io.IOException; import java.io.Reader; public class ClassA extends FilterReader { public ClassA(Reader in) { super(in); } @Override public int read(char[] cbuf, int off, int len) throws IOException { return super.read(cbuf, off, len); } } Steps to Reproduce: 1- Select the class "ClassA" 2- Choose "Refactor|Extract Superclass..." from the menus. 3- Enter a superclass name, i.e., "SuperClass" 4- Check the "read" method under "Specify actions for members:" 5- Set the action to "extract" 6- Click "Next". 7- Ensure the "read" method is checked. 8- Click "Next". Results: An error is displayed: "A fatal error occured while performing the refactoring.", "An unexpected exception occured while creating a change object. See the error log for details." If the "read" method does not exist (e.g. substitute "toString") then the exception does not occur.
|
2007-01-11 12:47:41
| 1,168,540,000
|
verified fixed
|
673d77f
| 1,177,510,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ExtractSupertypeProcessor.java
|
JDT
|
1,848
| 171,770
|
Bug 171770 [pull up] Pulling Up Methods to an interface ignores other implementations of that interface
|
Build ID: M20060921-0945 Steps To Reproduce: 1. In JUnit 3.8.1, select junit.framework.TestCase 2. Refactor > Pull Up... and select getName() & setName(.) 3. Ignore the empty list of subtypes (?) 4. Finish 5. Observe the 4 errors introduced in two direct implementers of Test (the changed interface)
|
2007-01-26 05:04:59
| 1,169,810,000
|
verified fixed
|
4d1a6fa
| 1,177,510,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PullUpRefactoringProcessor.java
|
JDT
|
1,849
| 178,335
|
Bug 178335 [build path] New Project wizard: execution environment default not alligned with other values
|
I20070320-0010. The new option to choose an execution environment has its value hard coded. This is not understandable for the user as the other two default values are always set based on the default JRE. I see three different solutions: - allow to globally set the default EE (like we have the default JRE) and use it - compute the EE that best matches the default JRE - remember the last value If the wizard remembers the last used value then my next user question would be: why aren't the other values remembered as well?
|
2007-03-20 12:42:04
| 1,174,410,000
|
resolved fixed
|
327a649
| 1,177,500,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/JavaProjectWizardFirstPage.java
|
JDT
|
1,850
| 162,549
|
Bug 162549 [surround with] Surround-with-if generates wrong code, brackets not matching
|
Hi, Please refer to the attached screenshot, I have a code snippet with some lines commented off in the end, when performing Source / Surround With / if statement, I see a wrong output, the curly brakets even don't match, It seems the template has been molested by those ending commets which also contain curly brackets.
|
2006-10-27 08:17:11
| 1,161,950,000
|
resolved fixed
|
fd34159
| 1,177,500,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/SurroundWithTemplateTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/SurroundWith.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/template/contentassist/SurroundWithTemplateProposal.java
|
JDT
|
1,851
| 183,857
|
Bug 183857 [package explorer] NPE from PackageExplorerPart for unknown editor input
|
When opening a compare editor, I get an NPE from PackageExplorerPart: java.lang.NullPointerException at org.eclipse.jdt.ui.JavaUI.getEditorInputJavaElement(JavaUI.java:731) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.editorActivated(PackageExplorerPart.java:1112) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$1.partActivated(PackageExplorerPart.java:229) at org.eclipse.ui.internal.PartListenerList2$1.run(PartListenerList2.java:68) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:850) at org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:53) at org.eclipse.ui.internal.PartListenerList2.firePartActivated(PartListenerList2.java:66) at org.eclipse.ui.internal.PartService.firePartActivated(PartService.java:77) at org.eclipse.ui.internal.PartService.setActivePart(PartService.java:171) at org.eclipse.ui.internal.WorkbenchPagePartList.fireActivePartChanged(WorkbenchPagePartList.java:56) at org.eclipse.ui.internal.PartList.setActivePart(PartList.java:126) at org.eclipse.ui.internal.WorkbenchPage.setActivePart(WorkbenchPage.java:3289) at org.eclipse.ui.internal.WorkbenchPage.activate(WorkbenchPage.java:601) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2670) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2592) at org.eclipse.ui.internal.WorkbenchPage.access$12(WorkbenchPage.java:2584) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2569) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2564) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2548) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2531) at org.eclipse.compare.internal.CompareUIPlugin$1.run(CompareUIPlugin.java:454) at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1171) at org.eclipse.compare.internal.CompareUIPlugin.internalOpenEditor(CompareUIPlugin.java:465) at org.eclipse.compare.internal.CompareUIPlugin.openEditorInBackground(CompareUIPlugin.java:436) at org.eclipse.compare.internal.CompareUIPlugin.openCompareEditor(CompareUIPlugin.java:426) at org.eclipse.compare.CompareUI.openCompareEditorOnPage(CompareUI.java:135) at org.eclipse.team.internal.ui.synchronize.actions.OpenInCompareAction.openCompareEditor(OpenInCompareAction.java:210) at org.eclipse.team.internal.ui.synchronize.actions.OpenInCompareAction.openCompareEditor(OpenInCompareAction.java:169) at org.eclipse.team.internal.ui.synchronize.actions.OpenInCompareAction.openCompareEditor(OpenInCompareAction.java:113) at org.eclipse.team.internal.ui.synchronize.actions.OpenInCompareAction.run(OpenInCompareAction.java:65) at org.eclipse.team.ui.synchronize.ModelSynchronizeParticipantActionGroup$1.run(ModelSynchronizeParticipantActionGroup.java:103) at org.eclipse.team.internal.ui.synchronize.StructuredViewerAdvisor.handleOpen(StructuredViewerAdvisor.java:171) at org.eclipse.team.internal.ui.synchronize.StructuredViewerAdvisor.access$0(StructuredViewerAdvisor.java:167) at org.eclipse.team.internal.ui.synchronize.StructuredViewerAdvisor$3.open(StructuredViewerAdvisor.java:131) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:850) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:45) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:187) at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:818) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079) at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:353) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1178) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3673) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2365) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2329) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2204) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:101) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:480) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:419) at org.eclipse.equinox.launcher.Main.run(Main.java:1145) at org.eclipse.equinox.launcher.Main.main(Main.java:1120)
|
2007-04-24 16:11:04
| 1,177,450,000
|
resolved fixed
|
7b1cd43
| 1,177,490,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerPart.java
|
JDT
|
1,852
| 174,275
|
Bug 174275 [package explorer] 'Open Project' action should open closed projects in mixed selection
|
I20070213-0907 The Open Project action in the Package Explorer behaves a bit weird. If only closed projects are selected, the action appears in the context menu and works fine. But if a mix of open and closed projects is selected, the action does not appear in the context menu, and 'menubar > Project > Open Project' shows a selection dialog. => When the selection contains at least one closed project, - the action should be in the context menu (Navigator does that too, and it's in line with Close Project) - the action should not show a dialog but open the closed project(s)
|
2007-02-15 06:33:05
| 1,171,540,000
|
resolved fixed
|
2bdbf98
| 1,177,490,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/OpenCloseWorkingSetAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/ViewActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/WorkingSetActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenProjectAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ProjectActionGroup.java
|
JDT
|
1,853
| 177,796
|
Bug 177796 [preferences] Add new options to 'code formatter' to expose constant from bug 20793
| null |
2007-03-16 13:19:22
| 1,174,070,000
|
resolved fixed
|
1de2997
| 1,177,430,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/CommentsTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/FormatterMessages.java
|
JDT
|
1,854
| 183,685
|
Bug 183685 [preferences] UI for Wrap binary expression before operator
| null |
2007-04-23 19:50:33
| 1,177,370,000
|
resolved fixed
|
1cbdf00
| 1,177,430,000
|
org.eclipse.jdt.ui.tests/test plugin/org/eclipse/jdt/testplugin/TestOptions.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/FormatterMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/LineWrappingTabPage.java
|
JDT
|
1,855
| 97,006
|
Bug 97006 [package explorer] Working set order is not restored after switching to project mode and reopening package explorer
|
I20050527-0010 Steps to reproduce: - Switch to workingset mode - Create several working sets - Rearrange them - Switch to project mode - Close package explorer - Reopen package explorer - Switch to workingset mode -> The working set dialog lost the order of the workingsets -> The order should be persisted either in the specialized Java workingset dialog or in the package explorer itself
|
2005-05-27 11:17:25
| 1,117,210,000
|
resolved fixed
|
6c43d3f
| 1,177,410,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/GotoResourceAction.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/packageview/PackagesFrameSource.java
|
JDT
|
1,856
| 183,149
|
Bug 183149 [create on paste] Paste code into empty Package Explorer produces stale Java project
|
JDT UI Head Steps to reproduce: - Start with fresh workspace - Paste following snippet to empty Package Explorer: package test; public abstract class E {} - Note the stale project (see attached screenshot)
|
2007-04-19 05:52:23
| 1,176,980,000
|
resolved fixed
|
63ff908
| 1,177,400,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/PasteAction.java
|
JDT
|
1,857
| 183,513
|
Bug 183513 [rename] Misleading inline rename preview for static method hiding
|
3.3M6 I20070323-1616 In the following code (single source file): public class X { public static void method() { } } class Y extends X { public static void method() { } } Go to either method and invoke inline rename (Alt-Shift-R). Both unrelated methods are marked for renaming. Once one is changed the false match reverts to its original name.
|
2007-04-21 17:52:01
| 1,177,190,000
|
resolved fixed
|
950846d
| 1,177,340,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/dom/LinkedNodeFinder.java
|
JDT
|
1,858
| 68,357
|
Bug 68357 [spell checking][preferences] Dictionary is missing
|
When spell-check is enabled, every word is marked as having been misspelt. I suppose that's because the dictionary is missing (or empty).
|
2004-06-23 14:44:24
| 1,088,020,000
|
verified fixed
|
9241e49
| 1,177,340,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/spelling/SpellCheckEngine.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/PreferenceConstants.java
|
JDT
|
1,859
| 175,244
|
Bug 175244 [clean up] Remove built in profile save participant
|
I20070222-0951 This profile is not useful anymore with the new save action story
|
2007-02-23 05:28:43
| 1,172,230,000
|
resolved fixed
|
cb7bb35
| 1,177,340,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CleanUpPreferenceUtil.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/CleanUpMessages.java
|
JDT
|
1,860
| 183,617
|
Bug 183617 [clean up] Clean up details section should use HTML bullet list
|
I20070417-0800 3.3M7 polish item. A bullet list would look much better. Also for the save actions additional actions info field.
|
2007-04-23 09:42:35
| 1,177,340,000
|
resolved fixed
|
4976ac9
| 1,177,340,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/CleanUpSaveParticipantPreferenceConfiguration.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/CleanUpConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/DialogBrowserConfigurationBlock.java
|
JDT
|
1,861
| 180,929
|
Bug 180929 [clean up] sort fields should warn for semantic change
|
Build ID: I20070323-1616 Steps To Reproduce: 1.Create an empty class 2.Add two constants private static final int z=5; private static final int a=2*Z; 3.Sort/cleanup with sort enabled/save with automatic sorting enabled More information: I entered a new bug regarding sorting, even though there are already, because all existing ones I found have been postponed with state LATER pointing out that sorting is no refactoring action and thus is not meant to preserve semantic. This might have been ok, as long as sorting was a deliberate act by the programmer she or he had to invoke explicitly. With 3.3 one can include sorting in Clean-Up and also have sort performed automatically on save. These automatic rules make no sense at all, if sort can occasionally produce code which does not compile any more.
|
2007-04-04 08:26:31
| 1,175,690,000
|
resolved fixed
|
cf72a37
| 1,177,320,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/CleanUpMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/CodeFormatingTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/ModifyDialogTabPage.java
|
JDT
|
1,862
| 178,945
|
Bug 178945 [JUnit] Upgrade to JUnit 4.3
|
JUnit 4.3 is released and contains several bug fixes. Eclipse ships with JUnit 4.1.
|
2007-03-23 03:25:00
| 1,174,630,000
|
resolved fixed
|
2f7dce1
| 1,177,320,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/launcher/JUnit3TestFinder.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/launcher/JUnit4TestFinder.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/util/TestSearchEngine.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/JUnit3TestFinder.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/JUnit4TestFinder.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/util/TestSearchEngine.java org.eclipse.jdt.ui.tests/testresources/JUnitWorkspace/JUnit4Tests/src/pack/Failures.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/junit/tests/JUnit4TestFinderTest.java
|
JDT
|
1,863
| 183,576
|
Bug 183576 [clean up] Additional actions section enabled when it should not be
|
I20070417-0800 1. Open Project Properties Page Java Editor>Save Actions 2. Configure Workspace Settings 3. Perform selected actions on save 4. Additional actions 5. OK 6. Restore Defaults Is: The additional actions text field becomes enabled Should: Not be enabled
|
2007-04-23 05:12:56
| 1,177,320,000
|
resolved fixed
|
2ec03bc
| 1,177,320,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/CleanUpSaveParticipantPreferenceConfiguration.java
|
JDT
|
1,864
| 173,425
|
Bug 173425 [clean up] CleanUpSaveParticipantPreferenceConfiguration should show workspace settings as defaults
| null |
2007-02-08 04:53:00
| 1,170,930,000
|
resolved fixed
|
ee980af
| 1,177,320,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/CleanUpSaveParticipantPreferenceConfiguration.java
|
JDT
|
1,865
| 120,269
|
Bug 120269 [refactoring] Preview filter combo: selecting an item does not update preview
| null |
2005-12-11 12:22:32
| 1,134,320,000
|
verified fixed
|
cdd0a18
| 1,177,310,000
|
org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/PreviewWizardPage.java
|
JDT
|
1,866
| 149,775
|
Bug 149775 [extract superclass] extract superclass refactor can cause stack overflow in refactored code
|
If i have these 2 classes... public class ExistingSuper { void method() { // do something } } public class Subclass extends ExistingSuper { @Override void method() { super.method(); } } ...and I extract a superclass for 'SubClass' and select the method to be moved up to superclass then I get this... public class Extracted extends ExistingSuper { public Extracted() { super(); } @Override void method() { this.method(); } } ...which has super.method() replaced with this.method() which causes a stack overflow. It should remain as super.method().
|
2006-07-05 22:00:12
| 1,152,150,000
|
verified fixed
|
7a51de3
| 1,177,310,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PullUpRefactoringProcessor.java
|
JDT
|
1,867
| 182,866
|
Bug 182866 [actions] The width of "New Java Class" wizard is different depending on the operation.
|
Build ID: I20070323-1616 Steps To Reproduce: 1. Eclipse launch in Windows Vista (Japanese) 2. Window > preference > General > Appearance > Color and Fonts "MS UI Gotic" set as the Dialog font. 3. Execute "New Java Class" wizard. More information: The width of the wizard displayed by Operation-1 and Operation-2 of the operations is different. Operation-1: - File menu > New > Other - Select "Class" Operation-2 - Click Downward triangle of (C+) button in the tool bar - Select "Class"
|
2007-04-18 02:15:24
| 1,176,880,000
|
resolved fixed
|
37b73d9
| 1,177,080,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/CreateTargetQueries.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocWizard.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/NewCUCompletionUsingWizardProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/util/PixelConverter.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/ClasspathContainerWizard.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/CreateLinkedSourceFolderAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/CreateSourceFolderAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/EditFilterAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/AbstractOpenWizardAction.java
|
JDT
|
1,868
| 182,921
|
Bug 182921 [Sync View] Missing outgoing/incoming icon in Java Model
|
I20070417-0800 The synchronize view has lost the incoming and outgoing icons when using the Java Workspace model.
|
2007-04-18 06:51:38
| 1,176,890,000
|
resolved fixed
|
5a41673
| 1,177,080,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/model/JavaSynchronizationLabelProvider.java
|
JDT
|
1,869
| 182,993
|
Bug 182993 Occasionally unable to refactor (by changing the name) get NullPointerException
|
Build ID: I20070323-1616 Steps To Reproduce: 1. Hit Refactor->Rename 2. Nothing happens (except stack trace) If I exit eclipse, and restart, all is fine again. More information: Unhandled event loop exception during blocked modal context. org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:3499) at org.eclipse.swt.SWT.error(SWT.java:3422) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3233) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2926) at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:158) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:326) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:495) at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:265) at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.disconnectFromWorkspace(IDEWorkbenchAdvisor.java:404) at org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.postShutdown(IDEWorkbenchAdvisor.java:321) at org.eclipse.ui.internal.Workbench.shutdown(Workbench.java:2650) at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:902) at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:819) at org.eclipse.ui.internal.Workbench$22.run(Workbench.java:1063) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1061) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1033) at org.eclipse.ui.internal.QuitAction.run(QuitAction.java:57) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1097) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3256) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2923) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2337) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2301) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2176) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:463) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:458) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:101) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:146) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:356) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:171) 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:476) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:416) at org.eclipse.equinox.launcher.Main.run(Main.java:1141) Caused by: java.lang.NullPointerException at org.eclipse.jdt.internal.ui.refactoring.reorg.RenameLinkedMode.cancel(RenameLinkedMode.java:328) at org.eclipse.jdt.internal.ui.refactoring.reorg.RenameInformationPopup$2.run(RenameInformationPopup.java:125) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) ... 44 more
|
2007-04-18 11:44:58
| 1,176,910,000
|
verified fixed
|
49964b0
| 1,177,000,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameLinkedMode.java
|
JDT
|
1,870
| 154,471
|
Bug 154471 WST code assumes IResource.getLocation() returns a non-null value
| null |
2006-08-20 10:51:46
| 1,156,090,000
|
resolved fixed
|
344102d
| 1,176,980,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/source/GenerateHashCodeEqualsTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/GenerateHashCodeEqualsOperation.java
|
JDT
|
1,871
| 183,142
|
Bug 183142 [package explorer] [working sets] Remove from WS does not work for resource working sets
|
I20070417-0800 1. Create a new java project P01 2. In PkgExpl select Top Level Elements>Working Sets 3. Create new Resource Working Set RWS and add P01 to it 4. Show RWS in PE 5. Right click on P01 6. Remove From Working Set Is: Nothing happen Should: Be moved to Other Projects
|
2007-04-19 05:15:54
| 1,176,970,000
|
resolved fixed
|
e4afc2b
| 1,176,970,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/RemoveWorkingSetElementAction.java
|
JDT
|
1,872
| 154,447
|
Bug 154447 [pull up] Assertion failure when invoking pull up
|
I have received the following assertion failure for every refactor -> pull up I have tried to perform so far. Common points - in each case, I was pulling up a single method from a concrete class into an interface. One method returned void, the other returned boolean. java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:350) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:851) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.internalPerformFinish(RefactoringWizard.java:545) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.performFinish(UserInputWizardPage.java:154) at org.eclipse.jdt.internal.ui.refactoring.PullUpMemberPage.performFinish(PullUpMemberPage.java:889) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish(RefactoringWizard.java:611) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:680) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog.finishPressed(RefactoringWizardDialog.java:97) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:355) at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.java:660) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:132) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:145) at org.eclipse.jdt.internal.ui.refactoring.actions.RefactoringStarter.activate(RefactoringStarter.java:40) at org.eclipse.jdt.internal.corext.refactoring.RefactoringExecutionStarter.startPullUpRefactoring(RefactoringExecutionStarter.java:355) at org.eclipse.jdt.ui.actions.PullUpAction.run(PullUpAction.java:139) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:271) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:243) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177) 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.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952) Caused by: org.eclipse.core.runtime.AssertionFailedException: assertion failed: at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109) at org.eclipse.core.runtime.Assert.isTrue(Assert.java:95) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.checkMethodReturnTypes(PullUpRefactoringProcessor.java:904) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.checkMembersInTypeAndAllSubtypes(PullUpRefactoringProcessor.java:890) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.checkFinalConditions(PullUpRefactoringProcessor.java:699) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:175) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:83) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:118) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:189) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) Root exception: org.eclipse.core.runtime.AssertionFailedException: assertion failed: at org.eclipse.core.runtime.Assert.isTrue(Assert.java:109) at org.eclipse.core.runtime.Assert.isTrue(Assert.java:95) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.checkMethodReturnTypes(PullUpRefactoringProcessor.java:904) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.checkMembersInTypeAndAllSubtypes(PullUpRefactoringProcessor.java:890) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.checkFinalConditions(PullUpRefactoringProcessor.java:699) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:175) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:83) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:118) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:189) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
|
2006-08-19 19:29:58
| 1,156,030,000
|
verified fixed
|
5cdc450
| 1,176,970,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PullUpRefactoringProcessor.java
|
JDT
|
1,873
| 183,010
|
Bug 183010 FilteredTypesSelectionDialog does not call TypeSelectionExtension#initialize(..)
|
I20070417-0800 FilteredTypesSelectionDialog does not call TypeSelectionExtension#initialize(..). This is an API break, since JavaUI.createTypeDialog(.., TypeSelectionExtension) uses the FilteredTypesSelectionDialog now, and extensions cannot trigger a refresh any more.
|
2007-04-18 12:56:41
| 1,176,920,000
|
resolved fixed
|
6e985e4
| 1,176,960,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/FilteredTypesSelectionDialog.java
|
JDT
|
1,874
| 58,779
|
Bug 58779 [reconciling] Java reconciler should not be triggered by "normal" marker changes
|
I20040413 The Java reconciler listens for marker deltas and if there's one it reconciles the CU. We could be smarter and only reconcile if the delta contains a maker type that is handled by J Core.
|
2004-04-16 03:21:29
| 1,082,100,000
|
resolved fixed
|
8ba8460
| 1,176,910,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaReconciler.java
|
JDT
|
1,875
| 182,520
|
Bug 182520 open / close project takes 100 % of the CPU
| null |
2007-04-16 04:57:20
| 1,176,710,000
|
resolved fixed
|
39308e9
| 1,176,910,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/FilterUpdater.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaViewerFilter.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/ProblemTreeViewer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/WorkingSetFilter.java
|
JDT
|
1,876
| 182,948
|
Bug 182948 [rename] Rename in editor should save file if operation started in saved file
|
Rename in editor should save file if operation started in saved file.
|
2007-04-18 09:21:10
| 1,176,900,000
|
resolved fixed
|
34c1559
| 1,176,910,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameLinkedMode.java
|
JDT
|
1,877
| 182,739
|
Bug 182739 [quick fix] Change method to Quickfix proposes invalid array dimension
|
In the following code: public class ArrayTest { public void test(String[] a){ blubb(a); } private void blubb(int a[]) { } } The quickfix proposes: change method blubb(int[]) to blubb(String[]) but creates: private void blubb(String[] a[]) { }
|
2007-04-17 08:50:26
| 1,176,810,000
|
resolved fixed
|
ffaf609
| 1,176,900,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedMethodsQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/ASTResolving.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/ChangeMethodSignatureProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/UnresolvedElementsSubProcessor.java
|
JDT
|
1,878
| 176,502
|
Bug 176502 [quick assist] convert iterable for loop removes imports which are in use
|
Build ID: I20070222-0951 Steps To Reproduce: Put the following code in a Java file (has dependencies on EMF): package com.castortech.iris; import java.util.Iterator; import org.eclipse.emf.ecore.EObject; import org.eclipse.emf.ecore.resource.Resource; import org.eclipse.emf.ecore.util.Diagnostician; public class BugTest { public static void main(String[] args) { Resource resource = null; for (Iterator j = resource.getContents().iterator(); j.hasNext();) { EObject eObject = (EObject)j.next(); Diagnostician.INSTANCE.validate(eObject); } } } Choose source->Clean Up, and make sure the profile has "Remove unused imports" selected. The refactoring will incorrectly try to remove the imports for EObject and Diagnostician. More information: Note that while trying to minimize the example reproducing the bug, I was unable to get rid of the dependency on EMF. Replacing resource.getContents() with a java.util.List, for example, makes the bug go away.
|
2007-03-06 10:51:20
| 1,173,200,000
|
resolved fixed
|
a1ccd1b
| 1,176,900,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/ConvertIterableLoopQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/ConvertIterableLoopOperation.java
|
JDT
|
1,879
| 182,923
|
Bug 182923 NPE in AbstractFix#getAdditionalInfo
|
I20070417-0800 Given: package test1; public class E1 { public void foo(int[] is) { for (int i = 0; i < is.length; i++) { System.out.println(is[i]); } } } 1. Set caret after 'for' 2. Ctrl-1 3. Wait a sec Is: Caused by: java.lang.NullPointerException at org.eclipse.jdt.internal.corext.fix.AbstractFix.getAdditionalInfo(AbstractFix.java:120) at org.eclipse.jdt.internal.ui.text.correction.FixCorrectionProposal.getAdditionalProposalInfo(FixCorrectionProposal.java:113) at org.eclipse.jface.text.contentassist.AdditionalInfoController$6.run(AdditionalInfoController.java:162) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) ... 23 more
|
2007-04-18 07:00:32
| 1,176,890,000
|
resolved fixed
|
37cd097
| 1,176,890,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/LinkedFix.java
|
JDT
|
1,880
| 173,081
|
Bug 173081 [clean up] Remove trailing whitespace should not remove space after * in doc comment
|
I20070206-0010 Remove trailing whitespace always removes the space at the end of line " * " in doc comments: /** * Bla. * * Blah. */ A line "<indentation>* " is effectively an empty line, so the whitespace should stay if "Ignore empty lines" is checked. This is also what the formatter does.
|
2007-02-06 10:17:57
| 1,170,780,000
|
resolved fixed
|
166edba
| 1,176,890,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/CodeFormatFix.java
|
JDT
|
1,881
| 79,764
|
Bug 79764 [JUnit] Stop button is not disabled after tests finished in debug mode
|
Smoke for I20041130. Launch a JUnit test in debug mode with "Keep Junit running..." OFF. After the test run has finished, the "Stop" button is still enabled, even though the VM is already down. Pressing the button disables it.
|
2004-11-30 06:44:07
| 1,101,820,000
|
resolved fixed
|
7c82376
| 1,176,830,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestRunSession.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/TestRunSession.java
|
JDT
|
1,882
| 182,725
|
Bug 182725 NPE in New Java Project wizard
|
HEAD Resource perspective, Package Explorer closed. Select something in the Project Explorer and try to create a new Java Project NPE: java.lang.NullPointerException at org.eclipse.jdt.internal.ui.wizards.JavaProjectWizard.getWorkingSets(JavaProjectWizard.java:171) at org.eclipse.jdt.internal.ui.wizards.JavaProjectWizard.addPages(JavaProjectWizard.java:63) at org.eclipse.jface.wizard.WizardSelectionPage.getNextPage(WizardSelectionPage.java:113) at org.eclipse.ui.internal.dialogs.WorkbenchWizardSelectionPage.getNextPage(WorkbenchWizardSelectionPage.java:100) at org.eclipse.ui.internal.dialogs.NewWizardSelectionPage.advanceToNextPageOrFinish(NewWizardSelectionPage.java:71) at org.eclipse.ui.internal.dialogs.NewWizardNewPage$1.doubleClick(NewWizardNewPage.java:355) at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:799) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:850) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:45) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:187) at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:797) at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1348) at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1168) at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:237) at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:234) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:295) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3673) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.actions.NewWizardAction.run(NewWizardAction.java:182) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:123) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:221) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:471) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:424) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:164) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:467) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:791) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:838) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:565) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:507) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:124) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1139) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:947) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:975) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:971) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1285) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3764) at org.eclipse.swt.widgets.Tree.WM_CHAR(Tree.java:5222) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3664) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:5218) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4355) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2255) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3282) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2365) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2329) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2204) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:101) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:359) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:174) 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:474) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:414) at org.eclipse.equinox.launcher.Main.run(Main.java:1139) at org.eclipse.equinox.launcher.Main.main(Main.java:1114)
|
2007-04-17 06:50:57
| 1,176,810,000
|
verified fixed
|
30d534d
| 1,176,810,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/JavaProjectWizard.java
|
JDT
|
1,883
| 181,188
|
Bug 181188 [type wizards] Creating a class that implements an inner interface generates incorrect code
|
In 3.3M6, the generated code appears to include $ symbols. Open up the 'New Class Wizard'. Type in a name for the class. Click 'Add' in the interface section and type in 'Entry'. Select java.util.Map.Entry. Click 'Finish'. Generated code: import java.util.Map$Entry; public class EntryImp implements Map$Entry { } The $ symbol causes the code to not compile out-of-the-box.
|
2007-04-05 08:44:27
| 1,175,780,000
|
resolved fixed
|
3fab17d
| 1,176,800,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/SuperInterfaceSelectionDialog.java
|
JDT
|
1,884
| 178,484
|
Bug 178484 [organize imports] Static method in enum declaration results in spurious import declarations
|
Build ID: I20070222-0951 Steps To Reproduce: 1. Create a class containing the following code package test; public enum TestEnum { SPECIFIC(1), DEFAULT(getDefaultValue()); TestEnum(int value) {} private static int getDefaultValue() { return -1; } } 2. Run organize-imports 3. Eclipse will create a spurious import for test.TestEnum.getDefaultValue(), which is unneeded, and in turn causes an error ("The import test.TestEnum.getDefaultValue cannot be resolved"). More information: This only happens if the enum is in a package. If it's in the default package, organize imports has no effect.
|
2007-03-21 00:39:57
| 1,174,450,000
|
resolved fixed
|
11553a1
| 1,176,730,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/ScopeAnalyzerTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/dom/Bindings.java
|
JDT
|
1,885
| 182,341
|
Bug 182341 Show invisible characters on formatter preview
| null |
2007-04-13 11:18:57
| 1,176,480,000
|
resolved fixed
|
a628b4d
| 1,176,710,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/CleanUpPreview.java 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/formatter/BlankLinesTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/BracesTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/CommentsTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/ControlStatementsTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/FormatterMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/FormatterTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/IndentationTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/JavaPreview.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/LineWrappingTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/NewLinesTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/WhiteSpaceTabPage.java
|
JDT
|
1,886
| 182,458
|
Bug 182458 stack overflow renaming public type
|
N20070415-0010 * Select a public top level type in editor outline * Rename the type > stack overflow java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:350) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:310) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.internalPerformFinish(RefactoringWizard.java:550) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.performFinish(UserInputWizardPage.java:154) at org.eclipse.jdt.internal.ui.refactoring.reorg.RenameTypeWizardInputPage.performFinish(RenameTypeWizardInputPage.java:144) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish(RefactoringWizard.java:616) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.okPressed(RefactoringWizardDialog2.java:439) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:464) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:616) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:227) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3673) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:142) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:154) at org.eclipse.jdt.internal.ui.refactoring.actions.RefactoringStarter.activate(RefactoringStarter.java:49) at org.eclipse.jdt.internal.ui.refactoring.UserInterfaceStarter.activate(UserInterfaceStarter.java:60) at org.eclipse.jdt.internal.ui.refactoring.reorg.RenameUserInterfaceStarter.activate(RenameUserInterfaceStarter.java:31) at org.eclipse.jdt.ui.refactoring.RenameSupport.openDialog(RenameSupport.java:156) at org.eclipse.jdt.ui.refactoring.RenameSupport.openDialog(RenameSupport.java:115) at org.eclipse.jdt.internal.corext.refactoring.RefactoringExecutionStarter.startRenameRefactoring(RefactoringExecutionStarter.java:425) at org.eclipse.jdt.internal.ui.refactoring.actions.RenameJavaElementAction.run(RenameJavaElementAction.java:194) at org.eclipse.jdt.internal.ui.refactoring.actions.RenameJavaElementAction.run(RenameJavaElementAction.java:106) at org.eclipse.jdt.ui.actions.RenameAction.run(RenameAction.java:104) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:268) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:244) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:545) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:402) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3673) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3284) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2361) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2325) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:101) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:359) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:174) 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:589) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:474) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:414) at org.eclipse.equinox.launcher.Main.run(Main.java:1139) at org.eclipse.equinox.launcher.Main.main(Main.java:1114) Caused by: java.lang.StackOverflowError at org.eclipse.jdt.internal.corext.refactoring.RefactoringSearchEngine.findAffectedCompilationUnits(RefactoringSearchEngine.java:99) at org.eclipse.jdt.internal.corext.refactoring.RefactoringSearchEngine.findAffectedCompilationUnits(RefactoringSearchEngine.java:99) at org.eclipse.jdt.internal.corext.refactoring.RefactoringSearchEngine.findAffectedCompilationUnits(RefactoringSearchEngine.java:99) at org.eclipse.jdt.internal.corext.refactoring.RefactoringSearchEngine.findAffectedCompilationUnits(RefactoringSearchEngine.java:99) at
|
2007-04-15 10:09:27
| 1,176,650,000
|
verified fixed
|
6a5a662
| 1,176,670,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringSearchEngine.java
|
JDT
|
1,887
| 181,941
|
Bug 181941 [search] References to package filtered although all filters are disabled
|
I20070410-1043 Select package /org.eclipse.jdt.ui.tests/ui/org.eclipse.jdt.ui.tests.dialogs and search for references in workspace. Search view content description says: "[..] 3 references in workspace (no JRE) (3 matches filtered from view)". But when I open the filters dialog, all filters are disabled. Enabling the "Potential matches" filter in the dialog (but not from the menu!) reveals the 3 matches.
|
2007-04-11 10:38:46
| 1,176,300,000
|
resolved fixed
|
042649b
| 1,176,650,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/JavaMatchFilter.java
|
JDT
|
1,888
| 173,079
|
Bug 173079 [clean up] remove trailing whitespace not visible in preview
|
I20070206-0010 Remove trailing whitespace is not visible in preview. - public void stop() { } has a space after public, but it is not removed with the "All lines" setting - there's no example for whitespace on empty lines
|
2007-02-06 10:08:22
| 1,170,770,000
|
resolved fixed
|
62ce7cc
| 1,176,480,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/CodeFormatCleanUp.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/CommentFormatCleanUp.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/SortMembersCleanUp.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/CleanUpPreview.java 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/CodeFormatingTabPage.java
|
JDT
|
1,889
| 151,988
|
Bug 151988 [surround with] Surround With menu: Sort code templates
|
As a part of (I believe) 135285, The Surround With... menu was created, and the proposals were removed from Quick Fix. This causes two issues: 1) users must learn another keystroke, and 2) the sort order to access the templates is completely different. Can we make this available as an option? Or, and I know this is not easy, what about making Ctrl+1 cycle in a way similar to how Ctrl+Space now works. Pat.
|
2006-07-27 08:42:09
| 1,154,000,000
|
resolved fixed
|
968592b
| 1,176,460,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/QuickTemplateProcessor.java
|
JDT
|
1,890
| 97,200
|
Bug 97200 [package explorer] [working sets] Enable 'New' action for working sets
|
If I want to create a new folder in a project, I right-click the project. If I want to create a new project in a working set, I right-click the working set... and then remember that it doesn't work that way. I suggest that "New Project" should be enabled from the working set context menu, and the new project should add itself to the working set.
|
2005-05-30 05:38:21
| 1,117,450,000
|
verified fixed
|
0bd616d
| 1,176,460,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/NewWizardsActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/JavaProjectWizard.java
|
JDT
|
1,891
| 178,744
|
Bug 178744 [misc] Editor opened upon an out of sync resource should allow for refresh action
|
I20070320-0010 Scenario: - create new file test.txt in project P; - edit it; - leave Eclipse; - touch test.txt; - launch Eclipse; - answer 'No' to the 'File Changed' prompt; - you get your editor to display 'Resource is out of sync...'; - while refreshing it from the Navigator is easy, I found no means to refresh the resource from the editor itself, which I find non intuitive. Note: that behavior is somewhat general and other scenarios enable to display the file contents instead of the 'Resource is out of sync...' disclaimer, for which a contextual menu is available, but that menu has no refresh item. Checked behavior for Linux and XP.
|
2007-03-22 05:27:22
| 1,174,560,000
|
resolved fixed
|
a95389a
| 1,176,370,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitEditorActionContributor.java
|
JDT
|
1,892
| 181,805
|
Bug 181805 [convert local] Convert local to field fails with shorthand array initializer
|
I20070403-1110 public class Try { void m() { final boolean[] finished= { false }; } } Convert 'finished' to field gives: Caused by: java.lang.IllegalArgumentException at org.eclipse.jdt.core.dom.ASTNode.checkNewChild(ASTNode.java:1869) at org.eclipse.jdt.core.dom.ASTNode.preReplaceChild(ASTNode.java:1931) at org.eclipse.jdt.core.dom.Assignment.setRightHandSide(Assignment.java:417) at org.eclipse.jdt.internal.corext.refactoring.code.PromoteTempToFieldRefactoring.createExpressionStatementThatInitializesField(PromoteTempToFieldRefactoring.java:749) at org.eclipse.jdt.internal.corext.refactoring.code.PromoteTempToFieldRefactoring.addLocalDeclarationSplit(PromoteTempToFieldRefactoring.java:718) at org.eclipse.jdt.internal.corext.refactoring.code.PromoteTempToFieldRefactoring.createChange(PromoteTempToFieldRefactoring.java:523) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
|
2007-04-10 13:22:41
| 1,176,230,000
|
resolved fixed
|
db5dc7d
| 1,176,310,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/PromoteTempToField/canPromote/A_test24_in.java org.eclipse.jdt.ui.tests.refactoring/resources/PromoteTempToField/canPromote/A_test24_out.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/PromoteTempToFieldTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/PromoteTempToFieldRefactoring.java
|
JDT
|
1,893
| 137,114
|
Bug 137114 [build path] compliance settings for new Java projects are global
|
When you go through the new Java Project wizard you are given the opportunity to change compiler compilance settings etc. The wizard does not however make it very clearl that these settings are the global ones and not the ones for the project that you are creating. When I went through this I thought "great, I'm making a new project and it is letting me set it all up" but that turned out not to be the case and I had to go an figure out what the old settings were. Furhter, it is unclear what would happen if I chose a project specific JRE what scope the compilance setting changes would have. That is, would I have a project-specific JRE but global compliance settings?
|
2006-04-17 20:55:08
| 1,145,320,000
|
resolved fixed
|
0c90acf
| 1,176,300,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/JavaProjectWizardFirstPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewWizardMessages.java
|
JDT
|
1,894
| 135,298
|
Bug 135298 [nls tooling] Duplicate entries in string externalization wizard preview
|
N20060405-0010 There seems to be an error in the externalize string wizard preview. (see attached picture) The tree shows 2 changes for each string being externalized. If you click on the first change, you are shown the diff as expected. The second change shows nothing.
|
2006-04-06 11:18:23
| 1,144,340,000
|
resolved fixed
|
920fd16
| 1,176,300,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/nls/NLSSourceModifier.java
|
JDT
|
1,895
| 181,915
|
Bug 181915 [rename] in-place Rename Field refactoring forces preview even if textual occurrences are not updated
|
I20070410-1043 The in-place Rename Field refactoring forces preview even if textual occurrences updating is not enabled.
|
2007-04-11 06:49:33
| 1,176,290,000
|
verified fixed
|
74e35ee
| 1,176,290,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameLinkedMode.java
|
JDT
|
1,896
| 171,099
|
Bug 171099 [Sync View] Java content provider provides wrong label for folder
|
When view a resource project (i.e. non-Java) in the Sync view when using compressed folder, the Java content provider is somehow asked to provide a label and only provides a single segment instead of the project relative path. This is probably related to the use of pipelining (i.e. I recall that pipelining prevented the CN framework from being able to determine the proper model to ask for the label.
|
2007-01-19 15:48:45
| 1,169,240,000
|
resolved fixed
|
5bdd565
| 1,176,220,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/model/JavaSynchronizationLabelProvider.java
|
JDT
|
1,897
| 176,282
|
Bug 176282 Link With Editor in Navigator and Project Explorer should work for IEditInput that can adapt to IFile
|
If I define an IEditorInput implementation that returns an IFile when asked for an IFile.class adapter, the Link With Editor capability of the Navigator or Project Explorer should work properly. But it appears that this capability is supported by doing an instanceof IFileEditorInput test instead. That's far less flexible and doesn't seem like the right way to implement it. I talked to Dani about this problem, and he said he fixed it right away for the Package Explorer, which currently has the same proble. Perhaps this isn't a big concern, but I also noticed problems with how equals is defined for FileEditorInput. It only considers itself equal to another IFileEditorInput, even though it implements IPathEditorInput too. Yet JavaFileEditorInput will consider itself equal to another IPathEditorInput with a matching path. So one could have a JavaFileEditorInput that's considers itself equal to a particular FileEditorInput but the opposite would not be true. I think that makes equals poorly defined. I also don't think the hashCode method for JavaFileEditorInput is properly defined to match the equality algorithm. I suppose this hasn't caused any real problems...
|
2007-03-03 08:46:59
| 1,172,930,000
|
verified fixed
|
0d075ca
| 1,176,220,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaFileLinkHelper.java
|
JDT
|
1,898
| 133,530
|
Bug 133530 [javadoc location] validating location on typing very slow
| null |
2006-03-28 09:34:16
| 1,143,560,000
|
resolved fixed
|
3f0ddf2
| 1,176,220,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavadocConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java
|
JDT
|
1,899
| 130,725
|
Bug 130725 [build path] New Java project wizard should allow to set compliance for project only
|
I20060301-0800 The link to configure the compliance on the Java project wizard only allows to configure the workbench preference. It would make sense to hava a link to configure the project settings as well.
|
2006-03-07 07:00:26
| 1,141,730,000
|
resolved fixed
|
e8f8873
| 1,176,210,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/JavaProjectWizardFirstPage.java
|
JDT
|
1,900
| 181,758
|
Bug 181758 [clean up] CUR should use its own working copy owner
|
I20070403-1110 Would increase performance and lower memory footprint
|
2007-04-10 09:30:52
| 1,176,210,000
|
resolved fixed
|
01cceb4
| 1,176,210,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CleanUpRefactoring.java
|
JDT
|
1,901
| 181,193
|
Bug 181193 NPE in JavaEditor.isMarkingOccurrences(...)
|
Using I20070403-1110, I got this NPE debugging some code in java.util.zip.ZipFile. java.lang.NullPointerException at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.isMarkingOccurrences(JavaEditor.java:2899) at org.eclipse.jdt.internal.ui.javaeditor.ClassFileEditor$3.run(ClassFileEditor.java:683) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) The guilty line is: return getPreferenceStore().getBoolean(PreferenceConstants.EDITOR_MARK_OCCURRENCES); Not sure how it is possible to get a NPE there, but I got it twice.
|
2007-04-05 09:13:29
| 1,175,780,000
|
resolved fixed
|
dbbb65c
| 1,176,200,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java
|
JDT
|
1,902
| 178,508
|
Bug 178508 [clean up] performance degredation in clean up tests
| null |
2007-03-21 06:39:47
| 1,174,470,000
|
resolved fixed
|
3991c68
| 1,176,200,000
|
org.eclipse.jdt.ui.tests/performance/org/eclipse/jdt/ui/tests/performance/views/CleanUpPerfTest.java
|
JDT
|
1,903
| 177,709
|
Bug 177709 [rename] Inplace Rename refactoring not consistent with dialog refactoring
|
I20070313-1051 The editor inplace Rename refactoring is not consistent with dialog refactoring: while the dialog refactoring forces/requires the user to look at the preview when textual matches are replace, no preview is shown when renaming inplace. So - either the preview is really a must in the textual case and then it also has to appear in the inplace mode, or it is not a must and then the user must not be forced to look at it in the dialog mode.
|
2007-03-16 04:17:14
| 1,174,030,000
|
resolved fixed
|
5f1292a
| 1,175,790,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameLinkedMode.java
|
JDT
|
1,904
| 92,095
|
Bug 92095 [open type] Support access to "Type Filters" preferences directly from the Open Type dialog
|
I find that the type filters preference is a very handy feature and useful for cutting down on the size of files in the open types dialog, as well as duplicates. But I find this feature hard to discover under the "Appearance" preferences, it seems like the preference page should not be under appearance. Also it would be really nice to have a hook from the open types dialog to set this feature (i.e. select an item in the open types dialog and choose "Ignore all members in package "javax.blah.blah" or some such support).
|
2005-04-20 11:48:48
| 1,114,010,000
|
resolved fixed
|
5d9c024
| 1,175,790,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaUIMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/FilteredTypesSelectionDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/TypeFilterPreferencePage.java
|
JDT
|
1,905
| 181,160
|
Bug 181160 [organize import] Should use new CleanUpAction to do multi organize imports
| null |
2007-04-05 05:42:58
| 1,175,770,000
|
resolved fixed
|
1627d49
| 1,175,780,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTestCase.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/ImportsFix.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringExecutionStarter.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/CleanUpAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/MultiOrganizeImportAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/MultiSortMembersAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/ImportsCleanUp.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OrganizeImportsAction.java
|
JDT
|
1,906
| 181,157
|
Bug 181157 [organize import] NPE on cancel multi organize import
|
I20070327-0800 Running organize import and then pressing cancel resulted in: Caused by: java.lang.IllegalArgumentException: AST must not be null at org.eclipse.jdt.core.dom.rewrite.ImportRewrite.create(ImportRewrite.java:185) at org.eclipse.jdt.ui.CodeStyleConfiguration.createImportRewrite(CodeStyleConfiguration.java:64) at org.eclipse.jdt.internal.corext.codemanipulation.StubUtility.createImportRewrite(StubUtility.java:1502) at org.eclipse.jdt.internal.corext.codemanipulation.OrganizeImportsOperation.createTextEdit(OrganizeImportsOperation.java:420) at org.eclipse.jdt.internal.corext.codemanipulation.OrganizeImportsOperation.run(OrganizeImportsOperation.java:393) at org.eclipse.jdt.ui.actions.OrganizeImportsAction$3.run(OrganizeImportsAction.java:438) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:155) at org.eclipse.ui.internal.UISynchronizer$2.run(UISynchronizer.java:125) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) ... 44 more
|
2007-04-05 05:22:32
| 1,175,760,000
|
resolved fixed
|
8e9b2cd
| 1,175,770,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/OrganizeImportsOperation.java
|
JDT
|
1,907
| 60,557
|
Bug 60557 Inline method: creates same AST 4 times [refactoring]
|
I20040430 The current implementation of InlineAction#run(ITextSelection) is rather expensive. If you set the caret to a method call and run Refactor > Inline, the same AST (with bindings) is created 4 times: 3 times for each try... method and a last time when the refactoring is finally executed. The problem is that we don't pass the AST around.
|
2004-04-30 08:16:01
| 1,083,330,000
|
resolved fixed
|
420ef98
| 1,175,730,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringExecutionStarter.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/InlineTempRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/util/RefactoringASTParser.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/actions/InlineConstantAction.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/actions/InlineMethodAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/InlineAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/InlineTempAction.java
|
JDT
|
1,908
| 133,277
|
Bug 133277 [actions] Allow Sort Members to be performed on package and project levels
|
After talking to Martin A at EclipseCon, I suggested that it would be good if Sort Members could be made into an action that could be applied to projects as well as packages, like format and organise imports do. This would then enable such an action to be hooked into the Code Cleanup wizard. I'd love to help out fixing this bug. I've dug around into the code before since I had to apply my own operation to recursively process Java files, and I think that this functionality could be extracted into a superclass that could be made publically available for any others wanting to apply a recursive behaviour to Java projects.
|
2006-03-25 16:38:17
| 1,143,320,000
|
resolved fixed
|
09a5938
| 1,175,700,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpStressTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTestCase.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CleanUpRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringExecutionStarter.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/RefactoringMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/ActionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/AllCleanUpsAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/CleanUpAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/MultiSortMembersAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/GenerateActionGroup.java
|
JDT
|
1,909
| 178,730
|
Bug 178730 [navigation] Fake CU must use encoding from IEncodedStorage (GB18030: DBCS)
|
OS: Windows Vista Language: Simplified Chinese Build Name: IES 3.3M5 JDK version: J2RE 1.5.0 IBM J9 2.3 Windows Vista x86-32 j9vmwi3223-20070318(JIT Enabled) Summary: DBCS chars displayed as garbage in Outline view. Steps to recreate problem: 1. Launch IES3.3 Workbench, set Text File encoding to UTF-8 by clicking Window ->Preferences ->General ->Workspace. 2. Create a Java Project named myProject. 3. Create a Class named with DBCS chars like [unicode 6d4b,8bd5]. 4. Open the created class with Java editor and add a main function, save the file. 5. Right click the class and select Compare With ->Local History. 6. In History View, open a state. -->Problem: DBCS chars displayed as garbage in Outline view. Expected Result: DBCS chars should displayed correctly. Remark: 1. The screencap is attached. 2. Same problem occurs on RHEL5.
|
2007-03-22 03:31:08
| 1,174,550,000
|
closed fixed
|
1fb64ff
| 1,175,690,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitDocumentProvider.java
|
JDT
|
1,910
| 179,689
|
Bug 179689 [spell checking] SpellCheckEngine needs a lot of memory
|
N20070327-0010 I have a user dictionary with less than 500KB contents, but SpellCheckEngine takes up more than 6MB at run time.
|
2007-03-28 05:16:32
| 1,175,070,000
|
resolved fixed
|
d447410
| 1,175,690,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/spelling/engine/AbstractSpellDictionary.java
|
JDT
|
1,911
| 147,767
|
Bug 147767 [build path] exception in new source folder wizard when closed project is seed selection
|
*Close a projects in the workspace *Select the closed project *File > New Source Folder Got the following exception, which was reported as an Internal Error in the Error Log view: org.eclipse.core.internal.resources.ResourceException: Resource /Plug-in Project is not open. at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:145) at org.eclipse.core.internal.resources.Project.hasNature(Project.java:507) at org.eclipse.jdt.internal.ui.wizards.NewSourceFolderWizardPage.updateProjectStatus(NewSourceFolderWizardPage.java:301) at org.eclipse.jdt.internal.ui.wizards.NewSourceFolderWizardPage.packRootDialogFieldChanged(NewSourceFolderWizardPage.java:272) at org.eclipse.jdt.internal.ui.wizards.NewSourceFolderWizardPage$RootFieldAdapter.dialogFieldChanged(NewSourceFolderWizardPage.java:246) at org.eclipse.jdt.internal.ui.wizards.dialogfields.DialogField.dialogFieldChanged(DialogField.java:70) at org.eclipse.jdt.internal.ui.wizards.dialogfields.StringDialogField.setText(StringDialogField.java:162) at org.eclipse.jdt.internal.ui.wizards.NewSourceFolderWizardPage.init(NewSourceFolderWizardPage.java:169) at org.eclipse.jdt.internal.ui.wizards.NewSourceFolderCreationWizard.addPages(NewSourceFolderCreationWizard.java:40) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:499) at org.eclipse.jface.window.Window.create(Window.java:426) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1124) at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:102) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400) 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:585) at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336) at org.eclipse.core.launcher.Main.basicRun(Main.java:280) at org.eclipse.core.launcher.Main.run(Main.java:977) at org.eclipse.core.launcher.Main.main(Main.java:952)
|
2006-06-19 14:40:19
| 1,150,740,000
|
resolved fixed
|
03b027e
| 1,175,600,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewSourceFolderWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewWizardMessages.java
|
JDT
|
1,912
| 180,497
|
Bug 180497 [build path] Use Execution Env radio not disabled on detect
|
I20070327-0800 1. Go to New Java Project Wizard 2. Name: 'P0' 3. Select 'Create Project from existing source' 4. Select an existing Project Is: 'Use an execution environment JRE' is not disabled Should: be disabled
|
2007-04-02 11:14:35
| 1,175,530,000
|
resolved fixed
|
b55627e
| 1,175,530,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/JavaProjectWizardFirstPage.java
|
JDT
|
1,913
| 180,406
|
Bug 180406 [Common Navigator] Patch for bugs 179179, 157314, 156357
| null |
2007-04-01 21:45:41
| 1,175,480,000
|
resolved fixed
|
8c91964
| 1,175,530,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/CommonLayoutActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaNavigatorActionProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaNavigatorContentProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaNavigatorLabelProvider.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/PackageExplorerActionProvider.java
|
JDT
|
1,914
| 165,758
|
Bug 165758 [inline] Inline local in constructor with compile error does remove code
|
I20061121-1845 Given: package test; public class E1 { public E1(String label) {} public E1() { String s= "foo"; this(s); } } 1. Select variable 's' 2. Inline 's' (either through quick assist or through refactor menu) Is: public E1() { this(s); } Should: public E1() { this("foo"); } No exception is thrown.
|
2006-11-24 03:55:05
| 1,164,360,000
|
resolved fixed
|
440679b
| 1,175,520,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/InlineTempWizard.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/RefactoringMessages.java
|
JDT
|
1,915
| 148,313
|
Bug 148313 [build path] "Configure Build Path" incorrectly appears for non-Java projects
|
In Eclipse 3.2RC7, if I right-click a closed project or an open non-Java project in the Package Explorer, "Build Path" incorrectly appears on the context menu, and the submenu contains the single entry "Configure Build Path". Clicking on this entry opens the Info page of the project properties. (Presumably Eclipse tries to open the Java Build Path page, but it is not present.)
|
2006-06-22 18:07:53
| 1,151,010,000
|
resolved fixed
|
f40295f
| 1,175,520,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/ConfigureBuildPathAction.java
|
JDT
|
1,916
| 179,056
|
Bug 179056 [compiler] Compiler gives misleading Range for invisible field
|
public class A { private int test; public static A a = new A(); } class B { private void foo() { A.a.test=8; } } In method foo() the small a is highlighted while the real problem is test. This leads to a wrong change visibility quickfix. (The visibility of A is "raised" to friend access)
|
2007-03-23 11:58:14
| 1,174,670,000
|
verified fixed
|
9f5f867
| 1,175,510,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java
|
JDT
|
1,917
| 173,438
|
Bug 173438 [Contexts] ContextAuthority$1.widgetDisposed(..) does not handle case where shell is already disposed
|
I20070208-0010 ContextAuthority$1.widgetDisposed(..) does not handle the case where the shell is already disposed. It should check whether newShell has been disposed before calling newShell.removeDisposeListener(this). To reproduce, remove the asyncExec(..) workaround in HEAD of org.eclipse.jdt.internal.ui.refactoring.reorg.RenameInformationPopup.PopupVisibilityManager.start().new DisposeListener() {...}.widgetDisposed(DisposeEvent). org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:3478) at org.eclipse.swt.SWT.error(SWT.java:3401) at org.eclipse.swt.SWT.error(SWT.java:3372) at org.eclipse.swt.widgets.Widget.error(Widget.java:432) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:325) at org.eclipse.swt.widgets.Widget.removeDisposeListener(Widget.java:907) at org.eclipse.ui.internal.contexts.ContextAuthority$1.widgetDisposed(ContextAuthority.java:267) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:116) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:938) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:962) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:943) at org.eclipse.swt.widgets.Widget.release(Widget.java:740) at org.eclipse.swt.widgets.Widget.dispose(Widget.java:410) at org.eclipse.swt.widgets.Decorations.dispose(Decorations.java:441) at org.eclipse.swt.widgets.Shell.dispose(Shell.java:653) at org.eclipse.swt.widgets.Decorations.closeWidget(Decorations.java:302) at org.eclipse.swt.widgets.Shell.close(Shell.java:476) at org.eclipse.swt.widgets.Shell.traverseEscape(Shell.java:1634) at org.eclipse.swt.widgets.Control.traverse(Control.java:3197) at org.eclipse.swt.widgets.Control.translateTraversal(Control.java:3174) at org.eclipse.swt.widgets.Composite.translateTraversal(Composite.java:935) at org.eclipse.swt.widgets.Display.translateTraversal(Display.java:4012) at org.eclipse.swt.widgets.Display.filterMessage(Display.java:1021) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3100) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2264) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2228) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2103) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:457) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:452) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:101) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:146) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:169) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:476) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:416) at org.eclipse.equinox.launcher.Main.run(Main.java:1124) at org.eclipse.equinox.launcher.Main.main(Main.java:1099)
|
2007-02-08 08:30:52
| 1,170,940,000
|
verified fixed
|
25ab3d1
| 1,175,160,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameInformationPopup.java
|
JDT
|
1,918
| 173,770
|
Bug 173770 [JUnit] "Run As" menu items disappear
|
Build ID: I20070209-1006 Steps To Reproduce: 1. Click the Run menu 2. Drag cursor down to the "Run As" submenu 3. Wait for a sec, no submenu appears 4. Continue dragging cursor, and menu items disappear as the cursor moves over them More information: eclipse 3.3M5 on OS X 10.4.8
|
2007-02-11 00:49:26
| 1,171,170,000
|
resolved fixed
|
be6d035
| 1,175,090,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitPropertyTester.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/JUnitPropertyTester.java
|
JDT
|
1,919
| 141,517
|
Bug 141517 [JUnit] High memory consumption from JUnit history
|
3.2 - I20060505-1306 I am running with -Xmx512M on the command line; and noticed the heap size monitor to say 493M of 512M allocated, which is way more than in average for my self-hosting workspace (usually cruising at 240M). Using yourkit 5.5, I got a memory dump, which shows 50M are held by the JUnit history. This is not a leak per se, since I flushed history and the memory got claimed back correctly (still 50M for junit history is huge... entire JavaModel only takes 17M).
|
2006-05-12 06:48:34
| 1,147,430,000
|
resolved fixed
|
2f74baa
| 1,175,090,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitCorePlugin.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/ITestSessionListener.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/JUnitModel.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestRunHandler.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestRunListenerAdapter.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestRunSession.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/ITestSessionListener.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/JUnitModel.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/TestRunHandler.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/TestRunListenerAdapter.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/TestRunSession.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/JUnitPlugin.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestRunnerViewPart.java
|
JDT
|
1,920
| 179,729
|
Bug 179729 IAE in CompilationUnitDocumentProvider$CompilationUnitAnnotationModel.setIsActive()
|
I20070327-0800 !ENTRY org.eclipse.jdt.ui 4 0 2007-03-28 15:36:54.683 !MESSAGE Error in JDT Core during reconcile !STACK 0 java.lang.IllegalArgumentException: at org.eclipse.core.runtime.Assert.isLegal(Assert.java:62) at org.eclipse.core.runtime.Assert.isLegal(Assert.java:46) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitDocumentProvider$CompilationUnitAnnotationModel.setIsActive(CompilationUnitDocumentProvider.java:726) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:90) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:82) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:149) at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.reconcile(CompositeReconcilingStrategy.java:86) at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.reconcile(JavaCompositeReconcilingStrategy.java:96) at org.eclipse.jface.text.reconciler.MonoReconciler.process(MonoReconciler.java:75) at org.eclipse.jdt.internal.ui.text.JavaReconciler.process(JavaReconciler.java:343) at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:204)
|
2007-03-28 09:54:11
| 1,175,090,000
|
resolved fixed
|
93cd1cd
| 1,175,090,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitDocumentProvider.java
|
JDT
|
1,921
| 179,696
|
Bug 179696 [decorators] Should not use new ProblemsLabelDecorator() from jdt.ui
|
I20070327-0800 In the jdt.ui plug-in, we have a few callers of the no-arg constructor ProblemsLabelDecorator(). I think these should all be replaced by ProblemsLabelDecorator(null), since that one reuses the Java plugin's image registry.
|
2007-03-28 05:37:30
| 1,175,070,000
|
resolved fixed
|
d140688
| 1,175,080,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarimport/JarImportWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarManifestWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarPackageWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/model/JavaSynchronizationLabelProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/SearchLabelProvider.java
|
JDT
|
1,922
| 87,522
|
Bug 87522 [quick fix] remove assignment without sideeffects can have side effects
|
When eclipse reports an unused variable and offers to remove the variable and all assignments without side effects, it can have side effects. For instance MyDialog d; d = new MyDialog(); In this case it would remove the constructor "new MyDialog()". However the constructor could be doing something useful, such as displaying itself. Thus removing it will have side effects. If it just changed it to this: new MyDialog(); it would not have side effects.
|
2005-03-09 12:05:56
| 1,110,390,000
|
resolved fixed
|
5e7475a
| 1,175,000,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/AbstractFix.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/FixMessages.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/UnusedCodeFix.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/UnusedCodeCleanUp.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/FixCorrectionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java
|
JDT
|
1,923
| 179,460
|
Bug 179460 No 'Run as Junit Plug-in test' on methods
|
3.3 M6 1. create a test case in a PDE project 2. add some test methods 3. Open the 'Run As' context menu on the method. You only see 'Run as Junit Test', but no 'Run as Junit Plu-in Test' Problem is that <test property="org.eclipse.debug.ui.projectNature" value="org.eclipse.pde.PluginNature"/> doesn't work on IMethods as they don't adapt to IResource
|
2007-03-27 05:24:29
| 1,174,990,000
|
resolved fixed
|
9c8bc59
| 1,174,990,000
|
org.eclipse.jdt.core.manipulation/common/org/eclipse/jdt/internal/core/manipulation/JavaElementPropertyTester.java
|
JDT
|
1,924
| 178,819
|
Bug 178819 [misc] BIDI3.3:<HCG: function name in tool tip text window is not shown properly>
|
Build ID: Version 3.3 Steps To Reproduce: Note: treat Caps Lock latin letters as BiDi letters Hebrew\Arabic. 1. Run eclipse with -dir rtl flag. 2.Create a jave project. 3.Create a Java Class with BiDi name. as - EMANSSALC. 4. declare a function with 2 parameters when the method and the variables names are Bidi names. 5. Move your mouse on the function name. 6.Pay attention to the order of the function name and it's variables. Consider the function CLASS.NAME.FUNC( int VAR1, int VAR2) Actual Res: (2Var int, 1VAR int)FUNC.CLASSNAME return_type Ex_Result: return_type CLASSNAME.FUNC(int VAR1, int VAR2) More information: Note: The same problem happens with "Content Assist" on rtl. Also presented in Outline,Project Explorer view, etc'.
|
2007-03-22 11:48:45
| 1,174,580,000
|
verified fixed
|
9db710e
| 1,174,980,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaOutlinePage.java
|
JDT
|
1,925
| 172,284
|
Bug 172284 [JUnit] update JUnit4 to 4.2
| null |
2007-01-31 04:12:56
| 1,170,230,000
|
resolved fixed
|
f3d5738
| 1,174,930,000
|
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
|
JDT
|
1,926
| 179,018
|
Bug 179018 [preference][hovering] 'Externalized String' hover modifier key should be same as Hyperlink modifier
|
I20070322-1800 'Java > Editor > Hovers > Externalized String' hover modifier key should by default be the same as the 'Editors > Text Editors > Hyperlinking > Java Property Key' modifier keys. Was: unconfigured Expected: Ctrl+Alt
|
2007-03-23 10:10:40
| 1,174,660,000
|
resolved fixed
|
3cb2cd4
| 1,174,910,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/PreferenceConstants.java
|
JDT
|
1,927
| 179,022
|
Bug 179022 [nls tooling][hovering] 'Externalized String' hover modifier key does not work
|
I20070322-1800 The 'Externalized String' hover modifier key does not work (tooltip never shows up). Interestingly, it works as part of the Combined Hover.
|
2007-03-23 10:21:59
| 1,174,660,000
|
resolved fixed
|
ecf8bfc
| 1,174,900,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/NLSStringHover.java
|
JDT
|
1,928
| 172,314
|
Bug 172314 [Dialogs] FilteredItemsSelectionDialog does not allow us adding camel case navigation handler
|
I20070130-0800 FilteredItemsSelectionDialog does not allow us adding a camel case navigation handler to the filter field. In JDT's previous Open Type implementation, the user could press Ctrl+Left, Ctrl+Right, etc. to jump into camel case words (e.g. |Array|List|). This functionality is missing in HEAD, and JDT/UI cannot add it since we don't have access to the Text widget (FilteredItemsSelectionDialog.pattern). When we have the Text field, it's just a one-liner for the Open Type dialog: TextFieldNavigationHandler.install(patternTextField);
|
2007-01-31 09:52:59
| 1,170,260,000
|
verified fixed
|
1cb5c6d
| 1,174,580,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/FilteredTypesSelectionDialog.java
|
JDT
|
1,929
| 178,440
|
Bug 178440 Finalize Experimental jdt.junit APIs
|
I20070320-0010 There are still APIs in jdt.junit marked as EXPERIMENTAL. This has to be finalized for M6.
|
2007-03-20 17:55:58
| 1,174,430,000
|
resolved fixed
|
fd98b3d
| 1,174,470,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/junit/TestRunListener.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/ITestSuiteElement.java org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/TestRunListener.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/ITestSuiteElement.java
|
JDT
|
1,930
| 61,817
|
Bug 61817 [api] Provide API to execute move refactorings headless [refactoring]
|
Since there is public API for "RenameSupport", I was wondering why there isn't similar "MoveSupport" (or is there...) to kick off Java move/refactoring.
|
2004-05-11 17:40:58
| 1,084,310,000
|
resolved fixed
|
ca2e79d
| 1,174,320,000
|
org.eclipse.jdt.core.manipulation/refactoring/org/eclipse/jdt/core/refactoring/descriptors/MoveDescriptor.java org.eclipse.jdt.core.manipulation/refactoring/org/eclipse/jdt/internal/core/refactoring/descriptors/DescriptorMessages.java
|
JDT
|
1,931
| 82,296
|
Bug 82296 [typing][preferences] Move "tabs to spaces" function from JavaEditor to TextEditor
| null |
2005-01-05 18:19:21
| 1,104,970,000
|
resolved fixed
|
fd8d1d2
| 1,174,300,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitEditor.java
|
JDT
|
1,932
| 177,502
|
Bug 177502 [decorators] new volatile decorator should honor common style convention
|
I20070313-1051 + JDT UI from HEAD I always found it practical that the decorator for 'static' and 'final' followed the common style i.e. first 'static' then 'final' and not the other way around. If possoble, the same should be honored for the new volatile decorator. Currently it is added on the left which is not common style. The common style is: static volatile ....
|
2007-03-15 04:19:21
| 1,173,950,000
|
resolved fixed
|
a513bf0
| 1,174,170,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/JavaElementImageDescriptor.java
|
JDT
|
1,933
| 177,749
|
Bug 177749 [api] Make AbstractReusableInformationControlCreator API
|
I20070313-1051 We have 4 internal copies of AbstractReusableInformationControlCreator. This is a pain to maintain and should therefore be provide as API.
|
2007-03-16 09:50:03
| 1,174,050,000
|
resolved fixed
|
a098bd6
| 1,174,120,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/AbstractJavaCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/AbstractReusableInformationControlCreator.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavaInformationProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
1,934
| 170,310
|
Bug 170310 [javadoc export] JAR exporter misbehaves if debug information is disabled
|
Build ID: M20060629-1905 Steps To Reproduce: If the option "Add source file name to generated class file" in the Project properties (in Java Compiler options) is disabled, the JAR exporter exports all classes in the project even if only some of them are selected for export. More information:
|
2007-01-12 05:58:10
| 1,168,600,000
|
verified fixed
|
04aa374
| 1,174,060,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarFileExportOperation.java
|
JDT
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.