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 |
|---|---|---|---|---|---|---|---|---|---|---|
2,235
| 94,189
|
Bug 94189 [5.0] Add support for {@code} and {@literal} javadoc tags
| null |
2005-05-09 15:26:20
| 1,115,670,000
|
resolved fixed
|
7027d55
| 1,153,760,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JavaDoc2HTMLTextReaderTester.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavaDoc2HTMLTextReader.java
|
JDT
|
2,236
| 108,121
|
Bug 108121 [ccp] Also create project when pasting code snippet into Package Explorer
|
I20050823-0800 + plug-in export I like the new feature which generates the Java elements when pasting code snippets into the Package Explorer. Of course I tried to paste onto an empty Package Explorer and it did not work. I'd like to create a new project when pasting code snippet on Package Explorer where no project is selected.
|
2005-08-26 10:40:24
| 1,125,070,000
|
resolved fixed
|
f07077f
| 1,153,510,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/PasteAction.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/ReorgMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/BuildPathsBlock.java
|
JDT
|
2,237
| 50,832
|
Bug 50832 [package explorer] Show In Package Explorer doesn't work for CUs not on classpath
|
I20040127 Open a .java file from org.eclipse.jdt.ui.tests.refactoring/resources/.. (Note: 'resources' is not a source folder) => 'Navigate > Show In > Package Explorer' doesn't reveal the CU.
|
2004-01-29 04:48:53
| 1,075,370,000
|
resolved fixed
|
fa6e3e7
| 1,153,500,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerPart.java
|
JDT
|
2,238
| 140,163
|
Bug 140163 [build path] Set focus to DialogPackageExplorer when showing second project wizard page
|
N20060504-0010 To reproduce: 1. Open the new Java Project Wizard throgh clicking on New Java Project button in the toolbar 2. Type in a name 3. click next 4. click the help button in the lower left corner or press F1 Is: Nothing happens 5. Select the 'Source' 6. Click the button or press F1 Now the correct help is shown. Not sure why that is. I guess because the focus is on the 'Back' button. When the wizard is started through 'New->Project->Java Project' a help is shown, but the wrong one.
|
2006-05-04 10:23:40
| 1,146,750,000
|
resolved fixed
|
3614059
| 1,153,490,000
|
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/BuildPathBasePage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/BuildPathsBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/ClasspathOrderingWorkbookPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/LibrariesWorkbookPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/ProjectsWorkbookPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/SourceContainerWorkbookPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/NewSourceContainerWorkbookPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/JavaCapabilityConfigurationPage.java
|
JDT
|
2,239
| 150,249
|
Bug 150249 [typing] Pasting a contents inside a string to get string concatenation doesn't work if the string is not an empty string
|
Using 3.2, copy some code. Open a new empty string. Paste your code and it ends up as string concatenation. Now copy some code. Open a string which is not an empty string. Select the contents of the string except the starting and ending double quote and paste your code. The code is not seen as a string concatenation.
|
2006-07-11 09:41:42
| 1,152,630,000
|
resolved fixed
|
baf0a6c
| 1,153,480,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaStringAutoIndentStrategy.java
|
JDT
|
2,240
| 149,941
|
Bug 149941 [nls tooling] PropertiesFileDocumentProvider throws org.eclipse.core.internal.resources.ResourceException when a properties file cannot be found
|
The following exception is thrown when you have had a properties file open in an editor, and then the properties file is deleted, and then the "back" tool is clicked. An attempt to find the deleted properties file fails with the following excepiton. This is very easy to reproduce. Let me know if you need more detailed steps. org.eclipse.core.internal.resources.ResourceException: Resource /com.ibm.simona.admin/src/com/ibm/simona/admin/properties/configuration.properties does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:311) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:187) at org.eclipse.core.internal.resources.File.getContentDescription(File.java:270) at org.eclipse.jdt.internal.ui.propertiesfileeditor.PropertiesFileDocumentProvider.createFileInfo(PropertiesFileDocumentProvider.java:64) at org.eclipse.ui.editors.text.TextFileDocumentProvider.connect(TextFileDocumentProvider.java:482) at org.eclipse.ui.texteditor.AbstractTextEditor.doSetInput(AbstractTextEditor.java:3063) at org.eclipse.ui.texteditor.StatusTextEditor.doSetInput(StatusTextEditor.java:173) at org.eclipse.ui.texteditor.AbstractDecoratedTextEditor.doSetInput(AbstractDecoratedTextEditor.java:1512) at org.eclipse.ui.editors.text.TextEditor.doSetInput(TextEditor.java:178) at org.eclipse.ui.texteditor.AbstractTextEditor$17.run(AbstractTextEditor.java:2396) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:763) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:760) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2283) at org.eclipse.ui.texteditor.AbstractTextEditor.internalInit(AbstractTextEditor.java:2414) at org.eclipse.ui.texteditor.AbstractTextEditor.init(AbstractTextEditor.java:2441) at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:839) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:583) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:372) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:566) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2588) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2521) at org.eclipse.ui.internal.WorkbenchPage.access$10(WorkbenchPage.java:2513) at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2498) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2493) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2478) at org.eclipse.ui.internal.NavigationHistoryEntry.restoreLocation(NavigationHistoryEntry.java:66) at org.eclipse.ui.internal.NavigationHistory.gotoEntry(NavigationHistory.java:385) at org.eclipse.ui.internal.NavigationHistory.shiftEntry(NavigationHistory.java:436) at org.eclipse.ui.internal.NavigationHistory.backward(NavigationHistory.java:420) at org.eclipse.ui.internal.NavigationHistoryAction.run(NavigationHistoryAction.java:201) 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$6.handleEvent(ActionContributionItem.java:441) 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-07-06 22:30:15
| 1,152,240,000
|
resolved fixed
|
58e798a
| 1,153,480,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesFileDocumentProvider.java
|
JDT
|
2,241
| 150,159
|
Bug 150159 [refactoring] Refactoring participant actions get lost during preview involving back, next
| null |
2006-07-10 11:28:54
| 1,152,550,000
|
verified fixed
|
f2effeb
| 1,153,480,000
|
org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/participants/ProcessorBasedRefactoring.java
|
JDT
|
2,242
| 21,904
|
Bug 21904 [misc] Can't Ctrl+C copy from class file editor without source
|
The 'Ctrl+C' copy shortcut doesn't work in the Java class file editor (the one which appears when no source is available). The Windows shortcut 'Ctrl+Ins' works correctly. There's also no context menu with 'Copy' on it, nor is 'Copy' eabled on the 'Edit' pull down menu. Curiously, 'Select All' IS enabled, but doesn't seem to do anything.
|
2002-07-25 10:35:34
| 1,027,610,000
|
resolved fixed
|
035434e
| 1,153,480,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ClassFileEditor.java
|
JDT
|
2,243
| 145,733
|
Bug 145733 [rename] Renaming of Project causes linked folders to be unlinked and moved
|
When renaming a Project (Not a java project, but a "Simple" one) any linked folder gets changed to a standard folder and its contents are MOVED to the new location, instead of mantaining the linked folder. Steps to reproduce: 1) Create a new project (New > Project > Simple > Project) 2) Create a folder on C:\ (or whatever you like) and put some files in it. 3) Add the folder as a link in the project (New > Folder > (Advanced>>) > Link to folder in the filesystem. 4) Rename the project (Refactor > Rename) Now the linked folder has turned into a standard folder, and the contents have been moved. The linked folder's target doesn't exist anymore (it's been moved to the new Project location).
|
2006-06-07 06:26:33
| 1,149,680,000
|
verified fixed
|
222f080
| 1,153,470,000
|
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/RenameResourceChangeTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/changes/RenameResourceChange.java
|
JDT
|
2,244
| 151,280
|
Bug 151280 [misc] Providing a JavaSourceViewerConfiguration to SemanticHighlightingManager
| null |
2006-07-20 13:13:01
| 1,153,420,000
|
resolved fixed
|
3fbc7ef
| 1,153,470,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/SemanticHighlightingManager.java
|
JDT
|
2,245
| 151,024
|
Bug 151024 [actions] Format should not stop on read-only files, it should skip instead.
|
If I only have a few files checked out, when I try to format all the source code in my project, the formatter stops, since it detects some of my files being read-only. It should not halt at read-only files, instead it should just skip them and only format the writable files. It would provide better usability, as it will do as much as possible, which in this case is exactly what I want. Note, this issue is not related to the following bugs 27207, 69193, and 121552 that want to format the read-only files. I do not want that!
|
2006-07-18 20:11:59
| 1,153,270,000
|
verified fixed
|
334597b
| 1,153,410,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/ActionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FormatAllAction.java
|
JDT
|
2,246
| 151,062
|
Bug 151062 [templates] 'for' template does not work in detail formatters dialog
|
I20060718-0800 Preferences > Java > Debug > Detail Formatters: Add a detail formatter, write "for", invoke content assist, and chose any of the for templates. -> Template not inserted, log: java.lang.NullPointerException at org.eclipse.jdt.internal.corext.template.java.JavaContext.suggestVariableName(JavaContext.java:393) at org.eclipse.jdt.internal.corext.template.java.JavaContext.suggestVariableNames(JavaContext.java:377) at org.eclipse.jdt.internal.corext.template.java.NameResolver.resolve(NameResolver.java:75) at org.eclipse.jface.text.templates.TemplateContextType.resolve(TemplateContextType.java:272) at org.eclipse.jface.text.templates.TemplateContextType.resolve(TemplateContextType.java:239) at org.eclipse.jdt.internal.corext.template.java.JavaContext.evaluate(JavaContext.java:164) at org.eclipse.jdt.internal.ui.text.template.contentassist.TemplateProposal.apply(TemplateProposal.java:173) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.insertProposal(CompletionProposalPopup.java:784) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.insertSelectedProposalWithMask(CompletionProposalPopup.java:735) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.verifyKey(CompletionProposalPopup.java:1142) at org.eclipse.jface.text.contentassist.ContentAssistant$InternalListener.verifyKey(ContentAssistant.java:761) at org.eclipse.jface.text.TextViewer$VerifyKeyListenersManager.verifyKey(TextViewer.java:436) at org.eclipse.swt.custom.StyledTextListener.handleEvent(StyledTextListener.java:61) 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.Widget.sendEvent(Widget.java:952) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:709) at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:5051) at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:4793) 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.Widget.sendEvent(Widget.java:952) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:965) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:961) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1275) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3349) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3249) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4054) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1927) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2995) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.jdt.internal.debug.ui.JavaDetailFormattersPreferencePage.editType(JavaDetailFormattersPreferencePage.java:324) at org.eclipse.jdt.internal.debug.ui.JavaDetailFormattersPreferencePage$4.doubleClick(JavaDetailFormattersPreferencePage.java:181) at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:796) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:794) at org.eclipse.jface.viewers.StructuredViewer.handleDoubleSelect(StructuredViewer.java:1051) at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1158) at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:223) at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:220) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:281) 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:3377) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2997) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) 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:3377) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2997) 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-07-19 06:50:59
| 1,153,310,000
|
resolved fixed
|
93ad8fe
| 1,153,410,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/CompilationUnitCompletion.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/CompilationUnitContext.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/JavaContext.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/JavaDocContext.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/JavaFormatter.java
|
JDT
|
2,247
| 151,190
|
Bug 151190 [build path] Regression to Overlapping products in source tree tutorial
|
I20060718-0800 Step 7. of the Getting Started Tutorial 'Overlapping products in Source Tree': The DialogPackageExplorer does not render the content correct. Looks like getChildren is worng.
|
2006-07-20 03:50:25
| 1,153,380,000
|
resolved fixed
|
f3d8876
| 1,153,400,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/DialogPackageExplorer.java
|
JDT
|
2,248
| 150,989
|
Bug 150989 [syntax highlighting] Allow different colors for brackets and operators
|
The syntax coloring preferences dialog for the Java editor has one category for "brackets and operators". I prefer having brackets with bright colors that stand out (especially braces since they help delinate code blocks), but since operators are so much more common in code, having them also be bright is distracting. Apps like JCreator and even TextPad have separate classifications for brackets and operators - Eclipse should too!
|
2006-07-18 14:32:07
| 1,153,250,000
|
resolved fixed
|
5262be6
| 1,153,330,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaEditorColoringConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaCodeScanner.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/PreferenceConstants.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/IJavaColorConstants.java
|
JDT
|
2,249
| 150,698
|
Bug 150698 [rename] Failure caused by misnamed class when renaming a package
|
While trying to rename a package and it's subpackages the operation failed with this message, Refactoring An unexpected exception occurred while performing the refactoring. See the error log for more details. org/eclipse/ltk/internal/ui/refactoring/UIPerformChangeOperation$1 (Wrong name: org/eclipse/ltk/internal/ui/refactoring/UIPerHormChangeOperation$1) UIPerHormChangeOperation includes a typo. ^
|
2006-07-14 14:43:53
| 1,152,900,000
|
resolved fixed
|
8fd7d09
| 1,153,320,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testHierarchicalDisabledImport/in/my/pack/C.java org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testHierarchicalDisabledImport/out/your/pack/C.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/RenamePackageTests.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/RenameTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RefactoringScanner.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenamePackageProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/TextMatchUpdater.java
|
JDT
|
2,250
| 150,853
|
Bug 150853 [clean up] 'Remove unused imports' multi quick fix doesn't work on non-existing classes
|
'Remove unused imports' quick fix doesn't work on imports of non-existing classes. Example: //A.java import foo.Bar; public class A {} //B.java import foo.Bar; public class B {} Click on 'The import foo cannot be resolved' entry in Problems view and select QuickFix, then 'Find Similar Problems' (the other class appears on the 'Problems' list), 'Select All' and 'OK'. Progress bar appears and then window is closed and nothing happens. There are no errors in Error Log view.
|
2006-07-17 14:52:49
| 1,153,160,000
|
resolved fixed
|
4c13c47
| 1,153,210,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/UnusedCodeFix.java
|
JDT
|
2,251
| 149,954
|
Bug 149954 [call hierarchy] Open Call Hierarchy should not open editor
|
Activating "Open Call Hierarchy" for a reference of a method opens additionally an editor with the function. This did not happen in past versions. It is not necessary if one looks for other references of this funtion. To open a function definition one uses easier the "hyperlink feature".
|
2006-07-07 04:27:18
| 1,152,260,000
|
resolved fixed
|
14b5cd0
| 1,153,150,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyUI.java
|
JDT
|
2,252
| 67,967
|
Bug 67967 [search] Filter read/write variable references
|
The java search view filters for read and write access should be updated to filter read and write references to local variable, too.
|
2004-06-21 04:30:05
| 1,087,810,000
|
verified fixed
|
fd9a9b4
| 1,153,150,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/MatchFilter.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/NewSearchResultCollector.java
|
JDT
|
2,253
| 150,481
|
Bug 150481 [clean up] Removing qualified this expressions may change semantic
|
Hi! I just tried the new "Clean Up" feature and I found the following problem. Try to use it on this code and you'll find that it "cleans" up the code in a wrong way. --- public class Test { public Test() { doTest(); } public synchronized void doTest() { System.out.println("doTest started"); (new Inner()).start(); try { wait(); } catch(InterruptedException e) { e.printStackTrace(); } System.out.println("doTest finished"); } private class Inner extends Thread { @Override public void run() { try { Thread.sleep(2000); } catch(InterruptedException e) { e.printStackTrace(); } synchronized(Test.this) { Test.this.notifyAll(); } } } public static void main(final String[] args) { new Test(); } } --- The problem is with the option "Use 'this' qualifier for method access" set to "Only if necessary": it removes the "Test.this." qualifier... but the result is not lexically the same as the original code. I hope to have been of help. Mauro.
|
2006-07-13 04:01:13
| 1,152,780,000
|
verified fixed
|
572965c
| 1,152,790,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CodeStyleFix.java
|
JDT
|
2,254
| 148,118
|
Bug 148118 [Sync View] Outgoing deletion in package not showing in synchronize view
|
3.2 I20060602-1317 Steps to reproduce 1. create a project "P" 2. create a folder "f1" 3. create a folder "f2" 4. create a file "a" in "f1" 4. create a file "b" in "f1" 5. create a file "a" in "f2" 6. release the result of steps 1-5 to CVS 7. delete file "a" in "f1" and in "f2" 8. synchronize -> "a" in "f1" is marked as an outgoing deletion "a" in "f2" does not appear as a change at all
|
2006-06-21 16:51:23
| 1,150,920,000
|
verified fixed
|
6a34dba
| 1,152,720,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/model/ContentProviderTests.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/model/MockPluginView.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/model/JavaSynchronizationContentProvider.java
|
JDT
|
2,255
| 139,732
|
Bug 139732 [build path] Button enablement in User Library preferences
|
3.2RC2 Go to the user libary pref page. - add a user library - add a jar etc - create access rules - expand the access rules tree node > "Edit" button is enabled, but doesn't do anything < expected: "Edit" button disabled, or takes me to the access rules edit dialog - "Remove" button enablement: - enabled, but no-op when on "access rules" tree node or any rule sub-node - enabled, but a no-op when on an empty source / jar location
|
2006-05-02 12:02:44
| 1,146,590,000
|
resolved fixed
|
5541c05
| 1,152,620,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/UserLibraryPreferencePage.java
|
JDT
|
2,256
| 150,149
|
Bug 150149 [quick assist] Surround with template "flickers"
|
I20060704-0800 Given: package test; public class E { public void foo() { int i = 10; final int j = 10; System.out.println(i); System.out.println(j); int k = 10; k++; System.out.println(k); System.out.println(i); System.out.println(j); } } 1. Select System.out.println(i); System.out.println(j); int k = 10; k++; System.out.println(k); 2. Alt-Shift-Z 3. Surround with runnable Is: The editor "flickers", meaning you can see how lines are added/removed Should: Not flicker
|
2006-07-10 10:54:06
| 1,152,540,000
|
resolved fixed
|
769cc56
| 1,152,540,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/template/contentassist/SurroundWithTemplateProposal.java
|
JDT
|
2,257
| 139,938
|
Bug 139938 [quick assist] Surround with template adds unnecessary spaces
|
3.2. RC2 Given: public void foo() { System.out.println(10); } 1. Select line ' System.out.println(10);' 2. 'Alt-Shift-Z' 3. Surround with runnable Is: public void foo() { Runnable runnable = new Runnable() { public void run() { System.out.println(10); } }; <-Tab or spaces here } Should: have no spaces at the end
|
2006-05-03 08:58:44
| 1,146,660,000
|
resolved fixed
|
3eeb70b
| 1,152,540,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java 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/template/contentassist/SurroundWithTemplateProposal.java
|
JDT
|
2,258
| 139,675
|
Bug 139675 [quick fix] Convert 'if-else Blocks to Statements' is a no-op
|
3.2. RC2 Given: if (true) if (false) <cursor> { ; } else { ; } 1. Cursor to <cursor> 2. Ctrl-1 3. Change 'if-else' blocks to Statement Is: nothing happens Should: if (true) if (false) ; else ;
|
2006-05-02 09:41:14
| 1,146,580,000
|
resolved fixed
|
56414b9
| 1,152,530,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AssistQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/ControlStatementsFix.java
|
JDT
|
2,259
| 150,083
|
Bug 150083 Incremental find is disabled when text editor is embedded in MultiPageEditorPart
|
It looks like AbstractTextEditor.getStatusLineManager() is the culprit. MultiPageEditorSite.getActionBarContributor() always returns null so AbstractTextEditor.getStatusLineManager() will always return null. Shouldn't AbstractTextEditor.getStatusLineManager() just call getEditorSite().getActionBars().getStatusLineManager()? As currently written, it seems any editor without a contributor will have the same problem.
|
2006-07-08 21:40:49
| 1,152,410,000
|
resolved fixed
|
a8c276c
| 1,152,530,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/AddImportOnSelectionAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OrganizeImportsAction.java
|
JDT
|
2,260
| 149,990
|
Bug 149990 [clean up] Remove block changes semantic of if-then-else
|
I20060704-0800 Given: package test; public class E { public void foo() { if (false) { while (true) if (false) ; } else ; } } 1. Cursor at ^ 2. Ctrl-1 Is: 'Change if block to stmt' is available Should: Not be available Same for clean up. But clean up is much harder to fix. Quick fix is legal here: if (false) { while (true) { if (false) ; } } else ; But not the clean up, since it will change the while block to a stmt. I need to detect that case beforhand...
|
2006-07-07 11:06:13
| 1,152,280,000
|
verified fixed
|
62a4ef6
| 1,152,520,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AssistQuickFixTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/ControlStatementsFix.java
|
JDT
|
2,261
| 147,429
|
Bug 147429 [syntax highlighting] Autoboxing coloring not working on negative numbers
|
In preferences, Java->Editor->Syntax coloring->Java->Auto(un)boxed expressions is enabled, the coloring is not working for negative numbers, although auto-boxing still occurs.
|
2006-06-16 09:06:58
| 1,150,460,000
|
resolved fixed
|
bcf4daa
| 1,152,290,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/AutoboxingSemanticHighlightingTest.java org.eclipse.jdt.text.tests/testResources/semanticHighlightingTest1/Autoboxing.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/SemanticHighlightings.java
|
JDT
|
2,262
| 149,800
|
Bug 149800 [JUnit] NPE while copying editor code to clipboard during JUnit run
|
Build 3.2.0 While JUnit tests were running, I selected some text in a Java editor, and performed a copy action. A dialog popped up saying a NPE had occurred, see trace below (from console). It seems that there got some confusion in dispatch in between the editor thread and the Junit run. !ENTRY org.eclipse.ui 4 0 2006-07-06 12:20:01.989 !MESSAGE java.lang.NullPointerException !STACK 0 java.lang.NullPointerException at java.io.StringReader.<init>(StringReader.java:33) at org.eclipse.jdt.internal.junit.ui.JUnitCopyAction.convertLineTerminators(JUnitCopyAction.java:90) at org.eclipse.jdt.internal.junit.ui.JUnitCopyAction.run(JUnitCopyAction.java:64) at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) at org.eclipse.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:229) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:461) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:424) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:160) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:466) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:799) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:846) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:564) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:506) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:122) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:982) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:927) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:965) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:961) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1275) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3346) at org.eclipse.swt.widgets.Table.WM_CHAR(Table.java:4495) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3246) at org.eclipse.swt.widgets.Table.windowProc(Table.java:4491) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1923) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2966) 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-07-06 06:19:34
| 1,152,180,000
|
verified fixed
|
3509c31
| 1,152,200,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/JUnitCopyAction.java
|
JDT
|
2,263
| 149,797
|
Bug 149797 [quick assist] NPE in ConvertForLoopOperation
|
I20060704-0800 Given: package test; public class E { private int ba r() {return 0;} public void foo(int[] ints) { for^(int i = 0, max = ints.length, b= bar(); i < max; i++) { System.out.println(ints[i] + b); } } } 1. _Select_ space at ^ 2. Ctrl-1 Is: java.lang.NullPointerException at org.eclipse.jdt.internal.corext.fix.ConvertForLoopOperation$3.visit(ConvertForLoopOperation.java:726) at org.eclipse.jdt.core.dom.MethodInvocation.accept0(MethodInvocation.java:236) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2466) at org.eclipse.jdt.internal.corext.fix.ConvertForLoopOperation.doInferCollectionFromExpression(ConvertForLoopOperation.java:715) at org.eclipse.jdt.internal.corext.fix.ConvertForLoopOperation.doInferCollectionFromInitializers(ConvertForLoopOperation.java:697) at org.eclipse.jdt.internal.corext.fix.ConvertForLoopOperation.doInferCollection(ConvertForLoopOperation.java:639) at org.eclipse.jdt.internal.corext.fix.ConvertForLoopOperation.arrayCanBeInferred(ConvertForLoopOperation.java:416) at org.eclipse.jdt.internal.corext.fix.ConvertForLoopOperation.satisfiesPreconditions(ConvertForLoopOperation.java:188) at org.eclipse.jdt.internal.corext.fix.ControlStatementsFix.createConvertForLoopToEnhancedFix(ControlStatementsFix.java:294) at org.eclipse.jdt.internal.ui.text.correction.QuickAssistProcessor.getConvertForLoopProposal(QuickAssistProcessor.java:1150) at org.eclipse.jdt.internal.ui.text.correction.QuickAssistProcessor.getAssists(QuickAssistProcessor.java:166) at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor$SafeAssistCollector.safeRun(JavaCorrectionProcessor.java:369) at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor$SafeCorrectionProcessorAccess.run(JavaCorrectionProcessor.java:307) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor$SafeCorrectionProcessorAccess.process(JavaCorrectionProcessor.java:297) at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor.collectAssists(JavaCorrectionProcessor.java:473) at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor.collectProposals(JavaCorrectionProcessor.java:255) at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionProcessor.computeQuickAssistProposals(JavaCorrectionProcessor.java:211) at org.eclipse.jface.text.quickassist.QuickAssistAssistant$ContentAssistProcessor.computeCompletionProposals(QuickAssistAssistant.java:64) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1733) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:476) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$17(CompletionProposalPopup.java:473) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:408) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:402) at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1562) at org.eclipse.jface.text.quickassist.QuickAssistAssistant.showPossibleQuickAssists(QuickAssistAssistant.java:117) at org.eclipse.jdt.internal.ui.text.correction.JavaCorrectionAssistant.showPossibleQuickAssists(JavaCorrectionAssistant.java:176) ...
|
2006-07-06 06:00:04
| 1,152,180,000
|
verified fixed
|
f52ca9a
| 1,152,180,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/ConvertForLoopQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/ConvertForLoopOperation.java
|
JDT
|
2,264
| 148,419
|
Bug 148419 [clean up] convert to enhanced for loop ignores assignment to array if field access
|
I ran the source clean up on a large body of code with the use enhanced for loop where possible option turned on. Fortunately, I examined the results of the refactoring before applying. The clean-up turned code such as this: Foo[] foos = new Foo[10]; for (int i = 0; i < foos.length; ++i) { foos[i] = new Foo(); ... set some other properties on foos[i]... } into this: Foo[] foos = new Foo[10]; for (Foo element : foos) { element = new Foo(); // this is a problem .. set some other properties on element ... } The refactoring should not be allowed if the array variable appears on the left hand side of an = sign.
|
2006-06-23 13:43:21
| 1,151,080,000
|
verified fixed
|
e1d1a4d
| 1,152,180,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/ConvertForLoopQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/ConvertForLoopOperation.java
|
JDT
|
2,265
| 149,540
|
Bug 149540 [ltk] problems overriding TextFileChange#commit() [refactoring]
|
The implementation of TextFileChange.commit() may not actually perform the commit: if (needsSaving()) { fBuffer.commit(pm, false); } If I override the method, I cannot use the same condition, as needsSaving() is private. Even if I rely on the TextFileChange.commit() by calling super.commit() I then do not know if the commit was actually performed. I suggest to move the if-statement to the method perform(), such that commit() is called when it is supposed to be performed, only.
|
2006-07-04 05:40:45
| 1,152,010,000
|
verified fixed
|
b12d08c
| 1,152,100,000
|
org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/TextFileChange.java
|
JDT
|
2,266
| 149,496
|
Bug 149496 [hashcode/equals] Generate hashCode() violates naming conventions
| null |
2006-07-03 17:00:53
| 1,151,960,000
|
verified fixed
|
602c88e
| 1,152,100,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
|
2,267
| 104,941
|
Bug 104941 [getter setter] generating getters disobeys declaration order [code generation]
|
When generating getters for a class, the getters were generated in alphabetical order, whereas I expected them to be generated in the same order as the variables declared in the class.
|
2005-07-24 04:40:29
| 1,122,190,000
|
verified fixed
|
5fe1ceb
| 1,152,100,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/AddGetterSetterAction.java
|
JDT
|
2,268
| 140,416
|
Bug 140416 [content assist] restore proposal computers if none present
| null |
2006-05-05 14:35:10
| 1,146,850,000
|
verified fixed
|
dd95c05
| 1,152,100,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ContentAssistProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaTextMessages.java
|
JDT
|
2,269
| 144,747
|
Bug 144747 [preferences] TVT3.2:TCT807: KO: Extra mnemonic on Content Assist Advanced preference page
|
OS : RHEL 3.1 Must fix or not a must fix: NO Build date: 20060530 Component Name: Base Windows menu Blocking: No Language: KO Bitmap Location: V:\defects\KO\04.001510.gif Tester Name: Junghan Yoo Problem Description: Extra mnemonic. Please see the screen shot attached below. Steps to reproduce: On the menu bar from the main Workbench panel, click Windows > Preference Expand and Select General Select Keys Click on the View tab on the right-hand pane This article was reassigned from Category:''TVT/Testing''.
|
2006-05-31 15:06:08
| 1,149,100,000
|
verified fixed
|
48404c4
| 1,152,100,000
|
org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/ErrorWizardPage.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/history/RefactoringHistoryWizard.java
|
JDT
|
2,270
| 139,961
|
Bug 139961 [junit] JUnit runner collecting classes outside of src tree
|
I have tests which extend XMLTestCase from XMLUnit. The JUnit runner attempts to execute the tests in XMLTestCase which causes a failure because it has no tests. I do not think that the runner should attempt to run tests in XMLTestCase since its not in the source tree.
|
2006-05-03 10:35:40
| 1,146,670,000
|
resolved fixed
|
ea17241
| 1,152,100,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/util/TestSearchEngine.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/util/TestSearchEngine.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/junit/tests/TestTestSearchEngine.java
|
JDT
|
2,271
| 149,468
|
Bug 149468 [generate delegate] is missing final methods
|
See this example, in class B Eclipse is requested to generate delegate methods from A: public class A { public void a() {} public final void b() {} } public class B { A a; // Methods generated by Eclipse public void a() { a.a(); } // b() is missing! } Method b() is not generated.
|
2006-07-03 10:59:07
| 1,151,940,000
|
verified fixed
|
9aada57
| 1,152,100,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/source/GenerateDelegateMethodsTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility2.java
|
JDT
|
2,272
| 145,028
|
Bug 145028 [clean up] Use of modifier final messes volatile variables
|
When applying the Clean Up Wizard with the option "Use modifier 'final' where possible" active, it doesn't check if an variable has the "volatile" keyword. The result is a compiler error for affected classes.
|
2006-06-02 04:24:12
| 1,149,240,000
|
resolved fixed
|
d79e8df
| 1,152,020,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/VariableDeclarationFix.java
|
JDT
|
2,273
| 148,373
|
Bug 148373 [quick assist] Duplicate final modifiers added during code assist.
|
I have a method called public Double[] calc(Integer int){...} The IDE tries to assist me to add final modifiers to the int variable. But when I allow the IDE to perform this for me, it changes the method to the following : public Double[] calc(final final Integer int){...}
|
2006-06-23 08:16:26
| 1,151,060,000
|
resolved fixed
|
172517c
| 1,152,020,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AssistQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/VariableDeclarationFix.java
|
JDT
|
2,274
| 149,440
|
Bug 149440 [build path] Default src folder rendered as package in new project wizard
|
I20060628-1135 1. New Java Project 2. Type in name 'P01' 3. Seperate src and output folder 4. Next> Is: default package is shown and 'src' is shown as a package Should: No default package and 'src' is a source folder Select "package" 'src' and 'Add package src to bp': org.eclipse.core.runtime.CoreException: The folder is already a source folder. at org.eclipse.jdt.internal.corext.buildpath.ClasspathModifier.validateAndAddEntry(ClasspathModifier.java:1952) at org.eclipse.jdt.internal.corext.buildpath.ClasspathModifier.setNewEntry(ClasspathModifier.java:1880) at org.eclipse.jdt.internal.corext.buildpath.ClasspathModifier.addToClasspath(ClasspathModifier.java:236) at org.eclipse.jdt.internal.corext.buildpath.AddSelectedSourceFolderOperation.run(AddSelectedSourceFolderOperation.java:72) at org.eclipse.jdt.internal.ui.util.BusyIndicatorRunnableContext$BusyRunnable.internalRun(BusyIndicatorRunnableContext.java:113) at org.eclipse.jdt.internal.ui.util.BusyIndicatorRunnableContext$BusyRunnable.run(BusyIndicatorRunnableContext.java:80) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jdt.internal.ui.util.BusyIndicatorRunnableContext.run(BusyIndicatorRunnableContext.java:126) at org.eclipse.jdt.internal.ui.wizards.buildpaths.newsourcepage.HintTextGroup$2.linkActivated(HintTextGroup.java:234) at org.eclipse.ui.forms.widgets.FormText.activateLink(FormText.java:1515) at org.eclipse.ui.forms.widgets.FormText.handleMouseClick(FormText.java:1330) at org.eclipse.ui.forms.widgets.FormText.access$16(FormText.java:1304) at org.eclipse.ui.forms.widgets.FormText$6.mouseUp(FormText.java:436) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:137) 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:3375) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2995) at org.eclipse.jface.window.Window.runEventLoop(Window.java:820) at org.eclipse.jface.window.Window.open(Window.java:796) at org.eclipse.jdt.ui.actions.AbstractOpenWizardAction.run(AbstractOpenWizardAction.java:83) at org.eclipse.jdt.internal.ui.wizards.OpenJavaProjectWizardToolbarAction.run(OpenJavaProjectWizardToolbarAction.java:45) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254) at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229) 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$6.handleEvent(ActionContributionItem.java:441) 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:3375) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2995) 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) !SUBENTRY 1 org.eclipse.jdt.ui 4 4 2006-07-03 12:41:54.210 !MESSAGE The folder is already a source folder. Works fine in 3.2
|
2006-07-03 06:40:56
| 1,151,920,000
|
resolved fixed
|
9a0ca19
| 1,152,020,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/BuildPathDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/BuildPathsBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/DialogPackageExplorer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/NewSourceContainerWorkbookPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/JavaCapabilityConfigurationPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPage.java
|
JDT
|
2,275
| 148,635
|
Bug 148635 [build path] "Ok" button in "New Variable Classpath Entry" window is disabled
|
Goto Project->Properties->Java Build Path->Libraries for a java project Click Add Variable Click Configure Variables to add a new variable Click Ok to get back to the "New Variable Classpath Entry" The "Ok" button in this window is disabled. The only way out of this window is to click "cancel" (which does not cancel the creation of a new variable :) or close the window by clicking the aqua closebutton in the upper left corner of the window I'm on MacOS X 10.4.6 with java 1.5.0_06-112
|
2006-06-26 07:24:15
| 1,151,320,000
|
resolved fixed
|
8fb31dc
| 1,152,020,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ClasspathVariablesPreferencePage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/NewVariableEntryDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/VariableBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/dialogfields/ListDialogField.java
|
JDT
|
2,276
| 149,114
|
Bug 149114 [quick fix] 'create class' quickfix with varargs finds wrong superclass
|
(place cursor on 'UnknownClass', hit quick fix, choose 'create class') import java.util.*; public class Strange { { // suggests "class UnknownClass implements Number[]" (doesn't do varargs) Arrays.<Number>asList( new UnknownClass() ); // suggests "class UnknownClass" (same issue, I assume) Arrays.<Number>asList( new Integer(42), new UnknownClass() ); // now this is the weird one // suggests "class UnknownClass implements Arrays[]" Arrays.asList( new UnknownClass() ); } } This is with build i20060602-1317
|
2006-06-29 02:48:02
| 1,151,560,000
|
verified fixed
|
d9460c7
| 1,152,000,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedVariablesQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/ASTResolving.java
|
JDT
|
2,277
| 100,763
|
Bug 100763 [content assist] parameterized type proposals set wrong selection when entered using a trigger character
|
3.1-RC3 test pass - have the cu below - code assist after Col - select 'Collection' using the arrow keys (don't insert the proposal yet) - insert the proposal by pressing '.' expected: selection after the '.' actual: the closing '>' is selected This happens because the generic java type proposal selects the first ambiguous type argument when inserted. We should either: - not let '.' be a trigger character for parameterized type proposals, or - not set the selection if the proposals is entered by a trigger character (as opposed to 'return' or mouse click.
|
2005-06-20 04:49:44
| 1,119,260,000
|
resolved fixed
|
633fde7
| 1,151,940,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/GenericJavaTypeProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/LazyJavaTypeCompletionProposal.java
|
JDT
|
2,278
| 93,121
|
Bug 93121 [5.0][content assist] parameter hints for generic types
|
I20050426 we should offer parameter hints for the type parameters to a generic type: Map<K,V> map;
|
2005-04-28 10:12:58
| 1,114,700,000
|
resolved fixed
|
e091064
| 1,151,930,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaHeuristicScanner.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ExperimentalResultCollector.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/GenericJavaTypeProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaCompletionProposalComputer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaMethodCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaNoTypeCompletionProposalComputer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaTypeCompletionProposalComputer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/LazyJavaCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/LazyJavaTypeCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/CompletionProposalLabelProvider.java
|
JDT
|
2,279
| 144,902
|
Bug 144902 [navigation] Show in Package Explorer has no effect
|
3.2 RC5 - in the Keys preference page, bind a key sequence like Ctrl+Alt+P to Show In Package Explorer (in the Navigate category) - in a Java editor, press the key sequence - it has no effect
|
2006-06-01 11:45:13
| 1,149,180,000
|
verified fixed
|
d91a961
| 1,151,930,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java
|
JDT
|
2,280
| 140,565
|
Bug 140565 [clean up] 'change all acces through instances' + 'remove unused imports' leads to code with fatal errors
|
Version: 3.2.0 RC2 Build id: I20060428-1315 Given are the following example classes: ClassA.java: public class ClassA { static ClassB instanceOfClassB; } ClassB.java: public class ClassB { static ClassC instanceOfClassC; } ClassC.java: public class ClassC { static ClassD instanceOfClassD; } ClassD.java: public class ClassD { } Example.java: import java.io.*; public class Example { private void testFunction() { ClassA.instanceOfClassB.instanceOfClassC.instanceOfClassD.toString(); } } A 'clean up' of Example.java with 'change all acces through instances' and 'remove unused imports' checked lead's to ClassBClassA.instanceOfClassC.instanceOfClassD.toString(); which renders the code unusable. It should at least lead to ClassB.instanceOfClassC.instanceOfClassD.toString(); or to ClassD.toString(); Best regards Thomas Boeck
|
2006-05-08 10:12:22
| 1,147,100,000
|
verified fixed
|
99088b7
| 1,151,920,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CodeStyleFix.java
|
JDT
|
2,281
| 139,000
|
Bug 139000 [import rewrite] wrong import decision in ContextSensitiveImportRewriteContext for nested types
| null |
2006-04-27 13:04:44
| 1,146,160,000
|
resolved fixed
|
4ecf74f
| 1,151,920,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/AddImportTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/ContextSensitiveImportRewriteContext.java
|
JDT
|
2,282
| 144,058
|
Bug 144058 [build path] Default Java project layout should create separate source and output folders
|
Eclipse 3.2 Currently, when a user creates a new Java project, the default project layout is set to use the project's folder as the root for source and output class files. This creates a very cluttered directory structure for the user, should there ever be a need to examine the project's folder in the "Navigator" view or in some file manager. Most developers creates a separate build folder when compiling with Ant, so having this similar "feature" activated from the get-go as the default will teach new (Java) programmers how to properly organize their files in the event that they are not using an IDE.
|
2006-05-26 20:42:15
| 1,148,690,000
|
resolved fixed
|
334a5e7
| 1,151,680,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/NewJavaProjectPreferencePage.java
|
JDT
|
2,283
| 140,777
|
Bug 140777 [nls tooling] Wrong dialog title for 'Externalize Strings...'
| null |
2006-05-09 08:25:19
| 1,147,180,000
|
resolved fixed
|
7fe4848
| 1,151,680,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ExternalizeStringsAction.java
|
JDT
|
2,284
| 148,954
|
Bug 148954 [search] FindImplementorsAction fills log with newNotPresentException
|
I20060627-1200 I often get these while editing files. You should also check all other Find actions. !ENTRY org.eclipse.jdt.ui 4 10001 2006-06-27 15:23:26.445 !MESSAGE An error occurred while accessing a Java element !STACK 1 Java Model Exception: Java Model Status [<anonymous #3> [in createTextWidget(Composite, int) [in TextViewer [in [Working copy] TextViewer.java [in org.eclipse.jface.text [in src [in org.eclipse.jface.text]]]]]] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:485) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:516) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:249) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:235) at org.eclipse.jdt.internal.core.SourceType.isInterface(SourceType.java:565) at org.eclipse.jdt.ui.actions.FindImplementorsAction.canOperateOn(FindImplementorsAction.java:76) at org.eclipse.jdt.ui.actions.FindAction.canOperateOn(FindAction.java:101) at org.eclipse.jdt.ui.actions.FindAction.selectionChanged(FindAction.java:258) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchSelectionChanged(SelectionDispatchAction.java:255) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.selectionChanged(SelectionDispatchAction.java:250) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:149) at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:1976) at org.eclipse.jface.viewers.StructuredViewer.handleInvalidSelection(StructuredViewer.java:1092) at org.eclipse.jdt.internal.ui.viewsupport.ProblemTreeViewer.handleInvalidSelection(ProblemTreeViewer.java:206) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1336) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1413) at org.eclipse.jdt.internal.ui.browsing.JavaBrowsingContentProvider$2.run(JavaBrowsingContentProvider.java:389) at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:152) at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:28) at org.eclipse.swt.widgets.Display.syncExec(Display.java:3763) at org.eclipse.jdt.internal.ui.browsing.JavaBrowsingContentProvider.postRunnable(JavaBrowsingContentProvider.java:503) at org.eclipse.jdt.internal.ui.browsing.JavaBrowsingContentProvider.postRefresh(JavaBrowsingContentProvider.java:385) at org.eclipse.jdt.internal.ui.browsing.JavaBrowsingContentProvider.processDelta(JavaBrowsingContentProvider.java:318) at org.eclipse.jdt.internal.ui.browsing.JavaBrowsingContentProvider.processDelta(JavaBrowsingContentProvider.java:360) at org.eclipse.jdt.internal.ui.browsing.JavaBrowsingContentProvider.elementChanged(JavaBrowsingContentProvider.java:216) at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1486) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1476) at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1342) at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1300) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:760) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:779) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1123) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1095) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitDocumentProvider$3.run(CompilationUnitDocumentProvider.java:1159) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitDocumentProvider.commitWorkingCopy(CompilationUnitDocumentProvider.java:1156) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitDocumentProvider$4.execute(CompilationUnitDocumentProvider.java:1268) at org.eclipse.ui.editors.text.TextFileDocumentProvider$DocumentProviderOperation.run(TextFileDocumentProvider.java:144) at org.eclipse.ui.actions.WorkspaceModifyDelegatingOperation.execute(WorkspaceModifyDelegatingOperation.java:68) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:101) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:113) at org.eclipse.ui.internal.editors.text.WorkspaceOperationRunner.run(WorkspaceOperationRunner.java:73) at org.eclipse.ui.internal.editors.text.WorkspaceOperationRunner.run(WorkspaceOperationRunner.java:63) at org.eclipse.ui.editors.text.TextFileDocumentProvider.executeOperation(TextFileDocumentProvider.java:460) at org.eclipse.ui.editors.text.TextFileDocumentProvider.saveDocument(TextFileDocumentProvider.java:744) at org.eclipse.ui.texteditor.AbstractTextEditor.performSave(AbstractTextEditor.java:3795) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.performSave(CompilationUnitEditor.java:1343) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.doSave(CompilationUnitEditor.java:1396) at org.eclipse.ui.internal.SaveableHelper$1.run(SaveableHelper.java:131) at org.eclipse.ui.internal.SaveableHelper$4.run(SaveableHelper.java:252) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:369) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:313) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:763) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:760) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2283) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:258) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:136) at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1360) at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:2978) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:2991) at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:67) at org.eclipse.jface.action.Action.runWithEvent(Action.java:499) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:461) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:424) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:160) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:466) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:799) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:846) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:564) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:506) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:122) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:982) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:927) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:952) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:937) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:965) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:961) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1275) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:3349) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3249) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1923) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2966) 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) !SUBENTRY 1 org.eclipse.jdt.core 4 969 2006-06-27 15:23:26.445 !MESSAGE <anonymous #3> [in createTextWidget(Composite, int) [in TextViewer [in [Working copy] TextViewer.java [in org.eclipse.jface.text [in src [in org.eclipse.jface.text]]]]]] does not exist
|
2006-06-28 04:58:47
| 1,151,490,000
|
verified fixed
|
ec5583f
| 1,151,510,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/FindImplementorsAction.java
|
JDT
|
2,285
| 148,617
|
Bug 148617 [ltk] TextFileChange: violates API-contract of TextChange.acquireDocument
|
When acquiring the document from a TextFileChange twice, the counter <code>fAcquireCount</code> is not incremented to two. Therefore on the first call to releaseDocument, the document is released. The documentation of TextChange indicates that only the second call to releaseDocument should do this.
|
2006-06-26 05:16:27
| 1,151,310,000
|
resolved fixed
|
956630c
| 1,151,430,000
|
org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/TextFileChange.java
|
JDT
|
2,286
| 32,936
|
Bug 32936 [pull up] No progress monitoring when switching to method page [refactoring]
|
RC1 - JUnit setup - select TestCase.countTestCases - pull up - press next observe: you don't see and task or subtaskm labels.
|
2003-02-25 06:54:58
| 1,046,170,000
|
verified fixed
|
f2b6599
| 1,151,400,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/PullUpMethodPage.java
|
JDT
|
2,287
| 148,664
|
Bug 148664 [spec] IJavaModel#getJavaProject(String) throws IAE for invalid name
|
I20060620-1010 IJavaModel#getJavaProject(String) throws an IllegalArgumentException for an invalid project name, see IWorkspaceRoot#getProject(String). #getJavaProject() should either repeat the constraints on the name, or it should accept any name. Steps to reproduce: - open Run... dialog - doubleclick "Junit Plug-in Test" - select second radio button "Run all tests..." The empty launch configuration is a bug in debug (fixed in HEAD). I've added a check to avoid the issue in JDT/UI HEAD.
|
2006-06-26 11:16:19
| 1,151,340,000
|
verified fixed
|
e7066b7
| 1,151,340,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/JUnitMainTab.java
|
JDT
|
2,288
| 74,979
|
Bug 74979 [JUnit] key bindings for 'Rerun Test'
|
There are two specific keybindings I want for JUnit: 1) Run the last test run (function just like the button on the JUnit view) 2) Run As JUnit ( Just like choosing Run As JUnit from the run menu).
|
2004-09-24 14:13:57
| 1,096,050,000
|
verified fixed
|
2462e6b
| 1,151,330,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestRunnerViewPart.java
|
JDT
|
2,289
| 10,694
|
Bug 10694 [templates] need more flexible type mechanism
|
Templates provide some rudimentary support for indicating the type of a variable. If you use ${array}, for instance, the template tries to pick an array for that variable. But the built-in types are already insufficient, and I cannot imagine that we could possibly satisfy 80% of the users with only built in types. (For instance, I've written templates which cry for ${string} and ${iterator} types.) I think that the template support should provide some sort of generic mechanism for specifying the type of a variable. Something like ${java.lang.String string} or ${int index}. (20020215 build)
|
2002-03-04 12:53:51
| 1,015,260,000
|
closed fixed
|
0558c84
| 1,151,060,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/CompilationUnitCompletion.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/CompilationUnitContext.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/ElementTypeResolver.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/JavaContext.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/JavaContextType.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/JavaFormatter.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/JavaVariable.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/NameResolver.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/TypeVariableResolver.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/VarResolver.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaPlugin.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/TemplateEditorSourceViewerConfiguration.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/template/contentassist/MultiVariable.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/template/contentassist/MultiVariableGuess.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/template/contentassist/TemplateProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/template/preferences/TemplateVariableProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/template/preferences/TemplateVariableProposal.java
|
JDT
|
2,290
| 36,195
|
Bug 36195 [code templates] make method name available as variable
|
For code generation in the preferences | java | code generation | code and comments in case of exception there seems to be available only: date, dollar, exception_type, exception_var, time, todo, user, year Is it possible to make the enclosing method name accessible the exception is generated in? Thanks Ido
|
2003-04-08 05:55:16
| 1,049,800,000
|
resolved fixed
|
3b68f78
| 1,151,050,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/CodeTemplateContextType.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/surround/SurroundWithTryCatchRefactoring.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java
|
JDT
|
2,291
| 148,115
|
Bug 148115 errors in JDT user and isv doc
|
I used a software tool to run accessibility checks of the content in the <> Doc and found some problems. I will attach the reports, with a list of the problems sorted by severity (most severe first). Each problem lists the file, line number, severity and error. Please have a look at the reports and act as follows: 1. Fix problems with severity SV(severe violation) and V(violation) first. 2. Investigate whether problems marked with severity PSV(possible severe violation) and PV(possible violation) are truly problems and fix as required. 3. Optionally correct problems marked with severity I(informational); often these are deprecations. Some of the errors in the /reference files of the step1-reports appear to be due to the javadoc generator. Does a separate bug need to be opened if that is the case?
|
2006-06-21 16:21:10
| 1,150,920,000
|
verified fixed
|
31c69a7
| 1,150,970,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/ISharedImages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/JavaElementImageDescriptor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/JavaElementLabels.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/JavaUI.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/PreferenceConstants.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/ProblemsLabelDecorator.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/jarpackager/JarPackageData.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/refactoring/RenameSupport.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/JavaSourceViewerConfiguration.java
|
JDT
|
2,292
| 140,214
|
Bug 140214 [clean up] PotentialProgrammingProblemFix must be cleaned up
|
N20060504-0010 The PotentialProgrammingProblemsFix class must be cleaned up: - Fallback must be removed - Policy needed when calculation of id fails (warn the user) - ITypeBinding must be used to get the binary name - Code needs to be cleaned up it's hard to understand and read
|
2006-05-04 14:26:46
| 1,146,770,000
|
resolved fixed
|
be24339
| 1,150,970,000
|
org.eclipse.jdt.ui.tests/performance/org/eclipse/jdt/ui/tests/performance/views/CleanUpPerfTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/AbstractSerialVersionOperation.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CleanUpRefactoring.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/PotentialProgrammingProblemsFix.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/SerialVersionDefaultOperation.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/AbstractCleanUp.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/ICleanUp.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/PotentialProgrammingProblemsCleanUp.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMarkerResolutionGenerator.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/SerialVersionHashOperation.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/SerialVersionLaunchConfigurationDelegate.java
|
JDT
|
2,293
| 105,743
|
Bug 105743 [generalize type] Internal Error with exception in catch clause
|
The following Java code is written under JDK 1.5.04 with the Java-Editor of Eclipse 3.1 (WinXP): ----------- <snip> ----------------- import java.io.*; public class C { public void f(File f) { try { FileInputStream is = new FileInputStream(f); } catch (FileNotFoundException ex) { System.err.println("file not found"); } } } -------------- </snip> --------------- When trying to generalize the type FileNotFoundException (refactoring), I get an "internal error during computation of valid types" (reproducable). When I do the same thing for the FileInputStream, everything is fine. Bye, Michael
|
2005-08-01 17:36:13
| 1,122,930,000
|
verified fixed
|
18fecfb
| 1,150,720,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ChangeTypeRefactoring/positive/A_testCatchClause_in.java org.eclipse.jdt.ui.tests.refactoring/resources/ChangeTypeRefactoring/positive/A_testCatchClause_out.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ChangeTypeRefactoringTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ChangeTypeRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/typeconstraints/FullConstraintCreator.java
|
JDT
|
2,294
| 97,280
|
Bug 97280 [use supertype] Use Supertype Refactoring and Refactor menu not available in class file editor [refactoring]
|
3.1 RC1 Steps to reproduce: - Open binary type java.util.BitSet - Invoke context menu on selected type name -> No refactoring menu available -> Content outline correctly shows refactor menu with menu entry Use Supertype
|
2005-05-30 11:11:38
| 1,117,470,000
|
verified fixed
|
3a5c968
| 1,150,470,000
|
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 refactoring/org/eclipse/jdt/internal/ui/refactoring/actions/MoveInstanceMethodAction.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/actions/MoveStaticMembersAction.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/actions/RenameJavaElementAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/ExtractSuperClassAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/ExtractSuperTypeAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/SelectionConverter.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ClassFileEditor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitEditor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ChangeTypeAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ConvertAnonymousToNestedAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ConvertLocalToFieldAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ConvertNestedToTopAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ExtractConstantAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ExtractInterfaceAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ExtractMethodAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ExtractTempAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/InferTypeArgumentsAction.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 org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/IntroduceFactoryAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/IntroduceParameterAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ModifyParametersAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/MoveAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/PullUpAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/PushDownAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/RefactorActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/RenameAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/SelfEncapsulateFieldAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/UseSupertypeAction.java
|
JDT
|
2,295
| 99,963
|
Bug 99963 [extract local] on generic 'this' needs type arguments
|
I20050610-1757 (3.1RC2) Extract Local Variable, Extract Method and Introduce Parameter don't add type arguments when extracting 'this' of a generic type: Select 'this' in the class below => the type is always just MyArrayList. Expected: MyArrayList<E>. class MyArrayList<E> extends ArrayList<E> { void inspect() { for (Iterator<E> iter= this.iterator(); iter.hasNext();) { iter.next(); } } }
|
2005-06-14 10:17:35
| 1,118,760,000
|
resolved fixed
|
5f39a67
| 1,150,450,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractTemp/canExtract/A_test99_in.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractTemp/canExtract/A_test99_out.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ExtractTempTests.java
|
JDT
|
2,296
| 140,111
|
Bug 140111 [JUnit] Dynamic help is not displayed in the JUnit Launch configuration main tab
|
Dynamic help is not displayed in the Launch configuration JUnit main tab It is thought fixed as follows. 1) In org.eclipse.jdt.junit plug-in src/org/eclipse/jdt/internal/junit/launcher/JUnitMainTab.java Insert following line to public void createControl(Composite parent)method PlatformUI.getWorkbench().getHelpSystem().setHelp(getControl(), "org.eclipse.jdt.junit.launch_configuration_dialog_junit_main_tab"); //$NON-NLS-1$ 2) In org.eclipse.jdt.doc.user plug-in contexts_JDT_JUnit.xml Insert following lines: <context id="launch_configuration_dialog_junit_main_tab" > <description>This tab allows you specify parameters associated with the JUnit for the launch.</description> </context>
|
2006-05-03 23:55:02
| 1,146,710,000
|
resolved fixed
|
ced0be6
| 1,150,450,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/JUnitMainTab.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/IJUnitHelpContextIds.java
|
JDT
|
2,297
| 77,067
|
Bug 77067 [package explorer] Select All in the Package Explorer
|
Please support Select All in the package explorer.
|
2004-10-26 17:56:55
| 1,098,830,000
|
verified fixed
|
cb2af77
| 1,150,450,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/SelectAllAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerActionGroup.java
|
JDT
|
2,298
| 95,232
|
Bug 95232 [working sets] Edit Working Set dialog is too slow
|
The performance of the Edit Working Set dialog for a Java Working Set is really slow, it takes a lot of time to open and finish. My current project have arround 4500 files and near 100 in the working set, the machine is a Pentium 3 1Ghz with 512ram with near half memory not in use. The dialog takes near 20 seconds to open using 100% cpu and doing no I/O. This problem could be solved if new resources are automatically included to the selected working set and the context menu allows to remove a resource from the selected working set.
|
2005-05-13 16:57:50
| 1,116,020,000
|
verified fixed
|
495f12b
| 1,150,450,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/JavaWorkingSetPage.java
|
JDT
|
2,299
| 93,292
|
Bug 93292 [render] Package Explorer file icons not updated when file associations change
| null |
2005-04-29 12:39:49
| 1,114,790,000
|
verified fixed
|
0128f10
| 1,150,440,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/AppearanceAwareLabelProvider.java
|
JDT
|
2,300
| 146,532
|
Bug 146532 [inline] inline method produces compile error with this-qualified remote field access
|
Version: 3.2.0 Build id: I20060602-1317 When applying refactor / inline on the call to nonRecursiveAnalyseCodeLeaf in Z, the resulting code does not compile. Source files: X.java public class X { X left, right; Type resolvedType; public void checkNPE(BlockScope currentScope, FlowContext flowContext, FlowInfo flowInfo) { } public FlowInfo analyseCode(BlockScope currentScope, FlowContext flowContext, FlowInfo flowInfo) { // keep implementation in sync with CombinedBinaryExpression#analyseCode if (this.resolvedType.id == Type.T_JavaLangString) { return this.right.analyseCode( currentScope, flowContext, this.left.analyseCode(currentScope, flowContext, flowInfo).unconditionalInits()) .unconditionalInits(); } else { this.left.checkNPE(currentScope, flowContext, flowInfo); flowInfo = this.left.analyseCode(currentScope, flowContext, flowInfo).unconditionalInits(); this.right.checkNPE(currentScope, flowContext, flowInfo); return this.right.analyseCode(currentScope, flowContext, flowInfo).unconditionalInits(); } } FlowInfo nonRecursiveAnalyseCodeLeaf(BlockScope currentScope, FlowContext flowContext, FlowInfo flowInfo) { if (this.resolvedType.id != Type.T_JavaLangString) { this.left.checkNPE(currentScope, flowContext, flowInfo); } return this.left.analyseCode(currentScope, flowContext, flowInfo). unconditionalInits(); } } class FlowInfo { FlowInfo unconditionalInits() { return null; } } class BlockScope { } class FlowContext { } class Type { public int id; public static final int T_JavaLangString = 0; } Z.java public class Z extends X { X internalNodes[]; int depth; public FlowInfo analyseCode(BlockScope currentScope, FlowContext flowContext, FlowInfo flowInfo) { flowInfo = this.internalNodes[0].nonRecursiveAnalyseCodeLeaf( // inline this call currentScope, flowContext, flowInfo); return flowInfo; } } Result of the refactoring: public class Z extends X { X internalNodes[]; int depth; public FlowInfo analyseCode(BlockScope currentScope, FlowContext flowContext, FlowInfo flowInfo) { X r = this.internalNodes[0]; if (r.resolvedType.r.id != Type.T_JavaLangString) { r.left.checkNPE(currentScope, flowContext, flowInfo); } flowInfo = r.left.analyseCode(currentScope, flowContext, flowInfo). unconditionalInits(); return flowInfo; } } note the extraneous r in r.resolvedType.r.id.
|
2006-06-12 06:17:10
| 1,150,110,000
|
resolved fixed
|
e0101d3
| 1,150,390,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/receiver_in/TestRemoteFieldReceiver.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/receiver_out/TestRemoteFieldReceiver.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/InlineMethodTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/SourceAnalyzer.java
|
JDT
|
2,301
| 139,730
|
Bug 139730 [ltk][scripting] inappropriate internal error when apply script fails [refactoring]
|
Build: 3.2 RC2 1) Checked out org.eclipse.equinox.common from repository 2) Applied two refactorings (rename method and add parameter, script attached). 3) Exported the plugin as a JAR file, including the refactoring script. 4) Unzipped resulting JAR file to get the script file on disk 5) Deleted project from workspace 6) Checked out the following projects from HEAD: org.eclipse.equinox.common org.eclipse.core.jobs org.eclipse.core.filesystem org.eclipse.core.resources org.eclipse.core.runtime 7) Refactor > Apply Script. 8) Selected the script generated by the export in step 3) -> two "Internal Errors" occur and the script cannot be applied. I will attach the log.
|
2006-05-02 11:52:36
| 1,146,590,000
|
resolved fixed
|
e035b1a
| 1,150,370,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/JavaRefactoringDescriptor.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/PerformRefactoringHistoryOperation.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/history/RefactoringHistoryWizard.java
|
JDT
|
2,302
| 78,929
|
Bug 78929 [package explorer] search-result naviagtion dones honor "link with editor"
|
hi. when I navigate through the a search result via the buttons "show next match" / "show previuous match" the editor shows correctly the right java file, but the package explorer is not correctly updated ("link with editor" is set) cya - Marcel.
|
2004-11-18 05:51:12
| 1,100,780,000
|
verified fixed
|
19e9d16
| 1,150,360,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerPart.java
|
JDT
|
2,303
| 144,785
|
Bug 144785 [generate constructor] should not declare parameters as final when members are final [code generation]
|
3.2 RC6 When I declare a set of private final member variables, then execute the Source option 'Generate Constructor Using Fields', the generated constructor parameters are also declared final. I don't think the finality of the member variables are really related to the finality of the parameters, and I think the parameters should always be non-final - or at least the wizard should provide an option to toggle the parameter finality.
|
2006-05-31 17:28:23
| 1,149,110,000
|
verified fixed
|
5780425
| 1,150,360,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/source/GenerateConstructorUsingFieldsTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility2.java
|
JDT
|
2,304
| 67,589
|
Bug 67589 [reorg] cannot move folder into folder of non-java project [refactoring]
|
Cannot move folder into a folder inside a non-java project with ReorgMove. The move dialog only shows the simple project, without any children. Reason: StandardJavaElementContentProvider#getChildren(..) doesn't return children of an IProject. PackageExplorerContentProvider#getChildren has special code, which explains why children of non-java projects are visible in the Package Explorer: if (parentElement instanceof IProject) return ((IProject)parentElement).members(); In StandardJavaElementContentProvider#getChildren(..), ... if (element instanceof IFolder) return getResources((IFolder)element); ... should be changed to ... if (element instanceof IContainer) return getResources((IContainer)element);
|
2004-06-17 03:46:21
| 1,087,460,000
|
verified fixed
|
fa4f066
| 1,150,360,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/DestinationContentProvider.java
|
JDT
|
2,305
| 147,181
|
Bug 147181 [implementation] Incorrect use of instanceof TextSelection
| null |
2006-06-14 21:11:02
| 1,150,330,000
|
resolved fixed
|
3d9468f
| 1,150,360,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java
|
JDT
|
2,306
| 144,941
|
Bug 144941 [reorg] NPE in ReorgPolicyFactory [refactoring]
|
1. Create a Java Project JavaProj 2. Create a Java Class JC1 in Package P1 3. Create a basic Project NonJavaProj 4. Select JC1.java in the Package Explorer and Refactor ... Move it using the context menu 5. On the Move wizard, select NonJavaProj as the destination. 6. Check the "Update fully qualified names in non-Java text files (forces preview)" option and click Preview. RESULT: Exceptions thrown. The root exception is ... java.lang.NullPointerException at org.eclipse.jdt.internal.corext.refactoring.reorg.ReorgPolicyFactory$MoveFilesFoldersAndCusPolicy.handleType(ReorgPolicyFactory.java:1935) at org.eclipse.jdt.internal.corext.refactoring.reorg.ReorgPolicyFactory$MoveFilesFoldersAndCusPolicy.computeQualifiedNameMatches(ReorgPolicyFactory.java:1925) at org.eclipse.jdt.internal.corext.refactoring.reorg.ReorgPolicyFactory$MoveFilesFoldersAndCusPolicy.checkFinalConditions(ReorgPolicyFactory.java:1946) at org.eclipse.jdt.internal.corext.refactoring.reorg.JavaMoveProcessor.checkFinalConditions(JavaMoveProcessor.java:158) 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.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) If we do not perform Step 6 and still go to the preview page, things are fine and the refactoring completes successfully. Q1. Do we want to allow moving Java classes to non-Java Projects?? Q1a. If yes then the behavior should be consistent irrespective of whether the user performs Step 6 or not. Ideally, I would prefer if this Refactoring was disallowed in the main Move Wizard page itself.
|
2006-06-01 15:00:08
| 1,149,190,000
|
verified fixed
|
6c76496
| 1,150,300,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/ReorgPolicyFactory.java
|
JDT
|
2,307
| 129,547
|
Bug 129547 [hashcode/equals] add preference for instanceof [code generation]
|
Hibernate can load a POJO from a DB. However, it instanciates a proxy class instead of the real POJO class. This allows it to lazily load the attributes when a getter is invoked. However, if equals() or hashCode() is called before any of these getters is called, then the attribute values are null or 0. If there was an option (yes, I hate these as much as the next person) to use getter methods instead of direct access to the data members, that would be great. There is still a problem for these Hibernate/EJB3 pojos. The equals() code uses getClass() == other.getClass(). Because other is a proxy, this always fails. I have read all the discussion about this in JavaLobby, and I understand the reasons for doing this, but for my hibernate objects, I must change it to using instanceof. Again, I would be happy with an option in the generate dialog.
|
2006-02-27 06:03:12
| 1,141,040,000
|
verified fixed
|
7255aac
| 1,150,300,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 org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaUIMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/GenerateHashCodeEqualsDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/SourceActionDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/GenerateHashCodeEqualsAction.java
|
JDT
|
2,308
| 146,813
|
Bug 146813 [navigation] Changing default background color for Declaration view does nothing
|
I'm using dark background so the default of Declaration view (kind of yellow) doesn't look good. I've tried to change the background color, but it didn't work. The option was added in #41867 bug, along with Javadoc view background color. The later works ok.
|
2006-06-13 08:40:25
| 1,150,200,000
|
verified fixed
|
9d51747
| 1,150,290,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/SourceView.java
|
JDT
|
2,309
| 141,277
|
Bug 141277 [ltk] details pane of refactoring history control flickers when switching between refactorings [refactoring]
| null |
2006-05-11 07:03:40
| 1,147,350,000
|
resolved fixed
|
ba8ad8b
| 1,150,290,000
|
org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/history/RefactoringHistoryControl.java
|
JDT
|
2,310
| 98,069
|
Bug 98069 [jar exporter] generated exporter scripts should use encoding preference
| null |
2005-06-02 05:25:10
| 1,117,700,000
|
resolved fixed
|
401a226
| 1,150,290,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarFileExportOperation.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarPackageWriter.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocOptionsManager.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocWriter.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/UserLibraryPreferencePage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/CodeFormatterConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/ProfileStore.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/jarpackager/JarPackageData.java
|
JDT
|
2,311
| 140,315
|
Bug 140315 [ltk][scripting] refactoring history is empty if compilation unit selected [refactoring]
|
1) have a project with a CU and some refactorings done 2) selected the CU in the package explorer, File -> Export -> JAR file 3) check 'Export refactorings...' and see that the list of aviable refactoring is empty if you select the project in the package explorer everything works fine.
|
2006-05-05 04:58:24
| 1,146,820,000
|
resolved fixed
|
29daf46
| 1,150,220,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarPackageWizardPage.java
|
JDT
|
2,312
| 139,007
|
Bug 139007 [migrate jar] title does not change when selecting refactorings [refactoring]
|
steps: 1) open 'Replace JAR' and select a JAR file which has no refactoring info 2) title message is getting changed to 'Jar file does not...' and 'Next' button is disabled 3) select JAR which has refactoring info 4) title message does not change, 'Next' button is enabled
|
2006-04-27 13:23:25
| 1,146,160,000
|
verified fixed
|
e1a5005
| 1,150,220,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarimport/JarImportWizardPage.java
|
JDT
|
2,313
| 145,784
|
Bug 145784 [build path] BuildPathSupport is violating ClasspathContainerInitializer api contract
| null |
2006-06-07 11:09:58
| 1,149,690,000
|
verified fixed
|
3ac5a8c
| 1,150,190,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/BuildPathSupport.java
|
JDT
|
2,314
| 144,426
|
Bug 144426 [compiler] Compiler incorrectly reports "assignment to variable has no effect" when it is a duplicate
|
Eclipse 3.2RC4 for Win23: eclipse-SDK-3.2RC4-win32.zip Running on Windows XP SP2 public class Test { public static void main(String[] args) { int x = 2; if (true) { int x = 4; } } } "x = 4" is underlined with multiple markers: "The assignment to variable x has no effect", and "Duplicate local variable x". I believe that the first one is incorrect ("has no effect").
|
2006-05-30 08:54:51
| 1,148,990,000
|
verified fixed
|
29cfa40
| 1,150,120,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/RenameTemp/canRename/A_test62_in.java org.eclipse.jdt.ui.tests.refactoring/resources/RenameTemp/canRename/A_test62_out.java org.eclipse.jdt.ui.tests.refactoring/resources/RenameTemp/canRename/A_test63_in.java org.eclipse.jdt.ui.tests.refactoring/resources/RenameTemp/canRename/A_test63_out.java org.eclipse.jdt.ui.tests.refactoring/resources/RenameTemp/cannotRename/A_testFail32.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/RenameTempTests.java
|
JDT
|
2,315
| 139,142
|
Bug 139142 [ltk][scripting] indicate on wich project a refactoring is applied [refactoring]
|
N20060428 Apply a refactoring script. On the second page it should be somehow indicated on which project the refactoring will be applied. I.e. when having a refactoring 'Extract method 'private void init()' form 'main.Main.start()'to 'main.Main' the user does not know which project will be modified if there are multible projects with multible Main classes. Datails could contain: - Project: P1 or - Destination type: P1/main.Main or ...
|
2006-04-28 09:45:19
| 1,146,230,000
|
verified fixed
|
5e40f3d
| 1,149,780,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/JavaRefactoringDescriptorComment.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/code/ConvertAnonymousToNestedRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractConstantRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractTempRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/InlineConstantRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/InlineMethodRefactoring.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/code/IntroduceFactoryRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceIndirectionRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceParameterRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/PromoteTempToFieldRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ReplaceInvocationsRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/generics/InferTypeArgumentsRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameCompilationUnitProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameEnumConstProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameFieldProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameJavaProjectProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameLocalVariableProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameMethodProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenamePackageProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameResourceProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameSourceFolderProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameTypeParameterProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameTypeProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/sef/SelfEncapsulateFieldRefactoring.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/ChangeTypeRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ExtractInterfaceProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ExtractSupertypeProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInnerToTopRefactoring.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInstanceMethodProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveStaticMembersProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PullUpRefactoringProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PushDownRefactoringProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/UseSuperTypeProcessor.java
|
JDT
|
2,316
| 141,501
|
Bug 141501 [jar exporter] remove unused methods in JarPackagerUtil
|
3.2 RC4 The method getRefactoringHistory(...) is unused and should be removed
|
2006-05-12 04:48:05
| 1,147,420,000
|
resolved fixed
|
a59b088
| 1,149,780,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarPackagerUtil.java
|
JDT
|
2,317
| 129,929
|
Bug 129929 IDE no longer responsive when junit tests are running
|
Build 3.2m5 When running the junit tests for JDTCore, I observed that it is almost impossible to further edit some files (e.g. buildnotes) until the tests have completed. I accept the tests are using lots of CPU, but this is on a different VM instance. Other applications are still responsive (email client, web browser, etc...). Is this progress reporting causing grief here ?
|
2006-03-01 07:54:56
| 1,141,220,000
|
verified fixed
|
d5f4a85
| 1,149,000,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestElement.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestSuiteElement.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/TestElement.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/TestSuiteElement.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestSessionLabelProvider.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestViewer.java
|
JDT
|
2,318
| 143,481
|
Bug 143481 [misc] Multiple entries in view menu per category
|
I20060519-1206 1. Start with a fresh workspace 2. Create new java project 3. past: package pack; /** * @category API */ public class Controller { /** * @category internal */ private int value; /** * @category API getter */ public int getValue() { return value; } /** * @category setter */ public void setValue(int v) { value= v; } } 4. Open Menu in Outline View 5. Deselect 'internal' 6. Open menu again Is: Two entries for 'internal' Should: Only be one
|
2006-05-24 11:08:13
| 1,148,480,000
|
verified fixed
|
2776ca5
| 1,148,550,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/CategoryFilterActionGroup.java
|
JDT
|
2,319
| 141,527
|
Bug 141527 Message in "Add New Source Folder" wizard doesnt expand "relative to"
| null |
2006-05-12 08:56:40
| 1,147,440,000
|
verified fixed
|
0da8efa
| 1,148,480,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewWizardMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/AddSourceFolderWizardPage.java
|
JDT
|
2,320
| 141,994
|
Bug 141994 [JUnit] Runner does not find any test case when a class fails loading
|
* Symptoms ---------- When a test case class fails to load (in my case, there was an exception in the static initializer) the "Run all tests..." launch configuration does nothing at all. * Steps to reproduce -------------------- 1) Create a new empty Java project 2) Create a new JUnit test case TestDate, adding JUnit to the class path 3) Replace the source by the following import java.text.SimpleDateFormat; import junit.framework.TestCase; public class TestDate extends TestCase { private static final SimpleDateFormat FORMAT = new SimpleDateFormat("YYYY-MM-dd HH:mm:ss"); public void testThing() { assertNull(null); } } 4) Define a Run configuration with "Run all test in the following project" 5) Try running this configuration * Result -------- The run exits almost immediately with 0 test cases found and executed. * Expected outcome ------------------ At least an error message telling me some class could not be loaded
|
2006-05-16 09:52:40
| 1,147,790,000
|
verified fixed
|
3f6d7cd
| 1,148,400,000
|
org.eclipse.jdt.junit.runtime/src/org/eclipse/jdt/internal/junit/runner/RemoteTestRunner.java
|
JDT
|
2,321
| 143,171
|
Bug 143171 [misc] 'Update conflicts' dialog appears on save - save no longer possible
|
R3.1.2 and 3.2 RC5 1. create a Java project with a CU 2. add some text and save 2. close the Java editor 3. open the Java editor for above class 4. change the text without saving 5. from the Package Explorer's context menu select: Replace With > Previous From Local History 6. Give focus to Java editor 7. click 'No' to the dialog 8. Save ==> "Save problems" dialog appears with message: Save could not be completed. Reason: Update conflict NOTE: does not happen with standard text editor POSSIBLE WORKAROUNDS: - type another character and save works again - use Save As
|
2006-05-23 07:03:39
| 1,148,380,000
|
verified fixed
|
761f2ba
| 1,148,400,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitDocumentProvider.java
|
JDT
|
2,322
| 142,266
|
Bug 142266 [implementation] Remove workaround for bug 137091
| null |
2006-05-17 11:58:44
| 1,147,880,000
|
verified fixed
|
06470aa
| 1,148,400,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/BasicJavaEditorActionContributor.java
|
JDT
|
2,323
| 138,972
|
Bug 138972 [replace jar][inline method] Missing warning message
|
My client is using a method which has been inlined now. Performing 'Replace JAR' does not show that refactoring which seem reasonable to me. However, one could get a warning message about the change and its consequences.
|
2006-04-27 12:04:20
| 1,146,150,000
|
verified fixed
|
1061e0e
| 1,147,450,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarPackageWizardPage.java
|
JDT
|
2,324
| 141,400
|
Bug 141400 [Model Sync] New non-Java files do not appear in Sync View
|
I20060511-0800 The Java model content provider does not show new non java files in the sync view. Repro: 1. Check out the same project twice in the workspace. 2. Create a binary file and commit it in one of the projects (I created a .png). 3. Sync the other project, notice how the binary file is missing from the incoming changes when the Java Workspace model is selected.
|
2006-05-11 15:41:03
| 1,147,380,000
|
verified fixed
|
78f3f66
| 1,147,440,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/model/JavaSynchronizationContentProvider.java
|
JDT
|
2,325
| 140,553
|
Bug 140553 [junit] New JUnit launch configs mapped onto wrong existing ones
|
3.2 RC3 When starting a JUnit test via (context) menu it first tries to find an existing launch configuration. The code that does the matching does not take the loader into account and hence unexpected results can happen, e.g. saying that no tests are found even though there are tests. For 3.2 we either need to fix the code which matches launch configurations or put this into the readme.
|
2006-05-08 09:12:36
| 1,147,090,000
|
verified fixed
|
be23b3a
| 1,147,420,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitMessages.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/launcher/TestKindRegistry.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/JUnitBaseLaunchConfiguration.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/JUnitLaunchShortcut.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/TestKindRegistry.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/JUnitMessages.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestRunnerViewPart.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/util/TestSearchEngine.java
|
JDT
|
2,326
| 140,901
|
Bug 140901 Deletion of source-controlled file now considered a refactor, causing interactive checkout prompts
|
Using Eclipse 3.2 RC3, the act of deleting a source controlled file using our source control plugin now causes a validateEdit event to be fired as if the deletion it is necessary to check out the file in our "pessimistic filesystem" team plugin. Our source control provider does not need (indeed does not WANT) to have the file readable, as it only needs to check out the containing folder. This is counter to prior behavior. The behavior for Eclipse up to and including 3.2M5a has been to go straight to MoveDeleteHook's deleteFile method. You now get there only after having to go thru validateEdit... this alas, isn't an edit, strictly speaking. This behavior seems to have come with the release 3.2M6. In Eclipse 3.1, the SCM Adapter would not prompt to checkout on a deletion since since the delete process never called into validateEdit in said version. If I choose to not checkout... I get an prompt that says "The Refactor failed..." Evidently deletion is an interactive refactoring as opposed to a non-interactive process... In any event, this will cause a significant usability problem for team plugins that work with a pessimistic file system and implement validateEdit, (or so it would seem) when "deleting" multiple file resources.
|
2006-05-09 15:21:47
| 1,147,200,000
|
verified fixed
|
72e2252
| 1,147,370,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/JavaRenameProcessor.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameModifications.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/MoveModifications.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/RefactoringModifications.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/ReorgPolicyFactory.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/participants/ResourceChangeChecker.java
|
JDT
|
2,327
| 141,213
|
Bug 141213 [ccp] new artwork for 'copy qualified name'
| null |
2006-05-11 03:42:21
| 1,147,330,000
|
verified fixed
|
d4a0607
| 1,147,370,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaPluginImages.java
|
JDT
|
2,328
| 140,551
|
Bug 140551 [junit] Strange ignored node in JUnit view
|
3.2 RC3 The ignored items in the JUnit view can't be opened. A dialog is shown. This is probably caused by the 'hacked' name. This should be fixed for 3.2.
|
2006-05-08 09:02:48
| 1,147,090,000
|
verified fixed
|
076350d
| 1,147,360,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitMessages.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestCaseElement.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/TestCaseElement.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/CounterPanel.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/JUnitMessages.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestRunnerViewPart.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestSessionLabelProvider.java
|
JDT
|
2,329
| 140,982
|
Bug 140982 Refactor->Use Supertype causes Stack overflow error
|
I got this error, which shut down my JVM, after I selected "Refactor->Use Supertype Where Possible...", in the Package Explorer. The trace is: java.lang.StackOverflowError at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:1842) at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1292) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:4734) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025) at org.eclipse.swt.internal.win32.OS.SendMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.SendMessage(OS.java:2589) at org.eclipse.swt.widgets.Tree.CDDS_ITEMPREPAINT(Tree.java:864) at org.eclipse.swt.widgets.Tree.wmNotifyChild(Tree.java:6103) at org.eclipse.swt.widgets.Control.WM_NOTIFY(Control.java:3794) at org.eclipse.swt.widgets.Composite.WM_NOTIFY(Composite.java:1166) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3298) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025) at org.eclipse.swt.internal.win32.OS.CallWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.CallWindowProc(OS.java:1842) at org.eclipse.swt.widgets.Tree.callWindowProc(Tree.java:1292) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3334) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:4734) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4025) at org.eclipse.swt.internal.win32.OS.SendMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.SendMessage(OS.java:2514) at org.eclipse.swt.widgets.TreeItem.setExpanded(TreeItem.java:1137) at org.eclipse.jface.viewers.TreeViewer.setExpanded(TreeViewer.java:642) at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpandToLevel(AbstractTreeViewer.java:1482) at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpandToLevel(AbstractTreeViewer.java:1490) at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpandToLevel(AbstractTreeViewer.java:1490) at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpandToLevel(AbstractTreeViewer.java:1490) at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpandToLevel(AbstractTreeViewer.java:1490) at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpandToLevel(AbstractTreeViewer.java:1490) at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpandToLevel(AbstractTreeViewer.java:1490) at org.eclipse.jface.viewers.AbstractTreeViewer.internalExpandToLevel(AbstractTreeViewer.java:1490) at <snip... this went on for a few pages>
|
2006-05-10 01:46:12
| 1,147,240,000
|
verified fixed
|
7bbfdf5
| 1,147,360,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/UseSupertypeWizard.java
|
JDT
|
2,330
| 140,761
|
Bug 140761 [junit] decouple filtering from presentation mode
| null |
2006-05-09 05:46:09
| 1,147,170,000
|
verified fixed
|
d73a425
| 1,147,360,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestRunnerViewPart.java
|
JDT
|
2,331
| 140,332
|
Bug 140332 [migrate jar] Migrate jar fails to create stubs for types in default package
|
3.2 RC2 Steps to reproduce: - Create project 'Test' with following cu in default package: public class MyTest { } - Create a client project 'Test' with MyTest in a JAR on the build path - Rename MyTest to MyTests - Export JAR with this refactoring - Invoke Migrate JAR file -> NPE occurs java.lang.NullPointerException at org.eclipse.jdt.internal.ui.refactoring.binary.BinaryRefactoringHistoryWizard$2.createCompilationUnit(BinaryRefactoringHistoryWizard.java:464) at org.eclipse.jdt.internal.corext.refactoring.binary.StubCreationOperation.run(StubCreationOperation.java:93) at org.eclipse.jdt.internal.corext.refactoring.binary.AbstractCodeCreationOperation.run(AbstractCodeCreationOperation.java:177) at org.eclipse.jdt.internal.ui.refactoring.binary.BinaryRefactoringHistoryWizard.createNecessarySourceCode(BinaryRefactoringHistoryWizard.java:473) at org.eclipse.jdt.internal.ui.refactoring.binary.BinaryRefactoringHistoryWizard.aboutToPerformRefactoring(BinaryRefactoringHistoryWizard.java:350) at org.eclipse.ltk.ui.refactoring.history.RefactoringHistoryWizard.createRefactoring(RefactoringHistoryWizard.java:587) at org.eclipse.ltk.ui.refactoring.history.RefactoringHistoryWizard.access$12(RefactoringHistoryWizard.java:584) at org.eclipse.ltk.ui.refactoring.history.RefactoringHistoryWizard$8.run(RefactoringHistoryWizard.java:835) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) The problem is that for the default package the method to populate the Java model with an IPackageFragment is not called which leads to the NPE above. Attaching patch...
|
2006-05-05 07:00:29
| 1,146,830,000
|
verified fixed
|
2b6af12
| 1,147,340,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/binary/AbstractCodeCreationOperation.java
|
JDT
|
2,332
| 140,755
|
Bug 140755 [refactoring] Updated artwork for Refactor->History...
|
3.2 RC3 The dialog to show the workspace refactoring history needs a title icon. Attaching patch...
|
2006-05-09 05:04:39
| 1,147,170,000
|
verified fixed
|
980b826
| 1,147,290,000
|
org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/RefactoringPluginImages.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/scripting/ShowRefactoringHistoryWizard.java
|
JDT
|
2,333
| 140,548
|
Bug 140548 [junit] NPE when opening history menu after removing launch configuration
|
I20060505-1306 Steps: - run a JUnit Test - delete the launch configuration - open JUnit view history menu or click on the toolbar button The user can only get rid of the NPEs by restarting Eclipse or by clicking on the history toolbar button, confirming the error dialog, and then removing the launches from the list. The bug is in TestRunSession: public String getTestRunName() { return fLaunch.getLaunchConfiguration().getName(); } Since the launch configuration can become null, we should store the original name. java.lang.NullPointerException at org.eclipse.jdt.internal.junit.model.TestRunSession.getTestRunName(TestRunSession.java:121) at org.eclipse.jdt.internal.junit.ui.TestRunnerViewPart$RunnerViewHistory.getText(TestRunnerViewPart.java:359) at org.eclipse.jdt.internal.ui.viewsupport.HistoryDropDownAction$HistoryAction.<init>(HistoryDropDownAction.java:36) at org.eclipse.jdt.internal.ui.viewsupport.HistoryDropDownAction$HistoryMenuCreator.addEntryMenuItems(HistoryDropDownAction.java:91) at org.eclipse.jdt.internal.ui.viewsupport.HistoryDropDownAction$HistoryMenuCreator.getMenu(HistoryDropDownAction.java:64) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:514) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:441) 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:143) 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) !ENTRY org.eclipse.ui 4 4 2006-05-08 10:03:04.215 !MESSAGE Unhandled event loop exception !ENTRY org.eclipse.ui 4 0 2006-05-08 10:03:04.215 !MESSAGE java.lang.NullPointerException !STACK 0 java.lang.NullPointerException at org.eclipse.jdt.internal.junit.model.TestRunSession.getTestRunName(TestRunSession.java:121) at org.eclipse.jdt.internal.junit.ui.TestRunnerViewPart$RunnerViewHistory.getText(TestRunnerViewPart.java:359) at org.eclipse.jdt.internal.ui.viewsupport.HistoryDropDownAction$HistoryAction.<init>(HistoryDropDownAction.java:36) at org.eclipse.jdt.internal.ui.viewsupport.HistoryDropDownAction$HistoryMenuCreator.addEntryMenuItems(HistoryDropDownAction.java:91) at org.eclipse.jdt.internal.ui.viewsupport.HistoryDropDownAction$HistoryMenuCreator.getMenu(HistoryDropDownAction.java:64) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:514) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:441) 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:143) 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-05-08 08:49:18
| 1,147,090,000
|
verified fixed
|
8b76973
| 1,147,290,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
|
2,334
| 139,933
|
Bug 139933 [CommonNavigator][Java] Deleting multiple projects does not remove them from project explorer
|
To reproduce: -Create an enterprise application with a default ejb and web module. -select those three -delete, choose option "delete content on file system". What happens: only the first of the three projects is removed from the project explorer, the other two seem to be left. But they are removed in the file system, and a restart of eclipse shows the right project explorer. I will attach a screenshot. To the left you will find the three projects before deletion, to the right the project explorer after deletion. Two phantom projects are left.
|
2006-05-03 08:48:40
| 1,146,660,000
|
closed fixed
|
1332160
| 1,147,290,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaNavigatorContentProvider.java
|
JDT
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.