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 |
|---|---|---|---|---|---|---|---|---|---|---|
735
| 287,049
|
Bug 287049 [actions] 'Add Import' always marks the editor as if it has unsaved changes
|
Build ID: I20090611-1540 Steps To Reproduce: 1. Save the Java source file. 2. Put the cursor to any class name which already has an appropriate 'import' statement or doesn't need it, press Shift-Ctrl-M or use corresponding menu item for 'Add Import'. The editor will be marked by an asterisk as if it has unsaved changes, and the 'Save' button on the toolbar will become available, but no text is really changed. More information: Example: import java.util.Map; public class AddImport { Map map; String s; } Pressing Shift-Ctrl-M on either 'Map' or 'String' causes the described things to happen.
|
2009-08-19 08:08:31
| 1,250,680,000
|
resolved fixed
|
2467883
| 1,250,690,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/AddImportsOperation.java
|
JDT
|
736
| 286,845
|
Bug 286845 Added new IProblem id UnresolvedVariable
| null |
2009-08-17 13:46:19
| 1,250,530,000
|
resolved fixed
|
f384f51
| 1,250,590,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/dom/LinkedNodeFinder.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/QuickFixProcessor.java
|
JDT
|
737
| 286,221
|
Bug 286221 [move method] Move refactoring can produce duplicate methods [refactoring]
|
Build ID: I20090611-1540 Steps To Reproduce: Steps To Reproduce: 1. Create the following classes: public class O { private S _s; public void m(){} } public class S { public void m(){} } 2. Now use the move refactoring to move method O.m to S. 3. The refactoring performs and produces the compile error without indicating an error status: Duplicate method m() in type S S.java More information:
|
2009-08-11 07:26:19
| 1,249,990,000
|
resolved fixed
|
90e5a54
| 1,250,530,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInstanceMethodProcessor.java
|
JDT
|
738
| 286,406
|
Bug 286406 [build path] File -> New Java Project not identifying source files correctly
| null |
2009-08-12 12:05:52
| 1,250,090,000
|
resolved fixed
|
9973883
| 1,250,520,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/ClassPathDetector.java
|
JDT
|
739
| 285,523
|
Bug 285523 [actions] Error by open a .js file
|
What steps will reproduce the problem? 1. I switch to the web perspective 2. choose a .js file in my project 3. double klick to open this file -- Error Details -- Date: Tue Aug 04 08:25:42 CEST 2009 Message: Beim Aufrufen des Codes vom Plug-in sind Fehler aufgetreten: "org.eclipse.jface". Severity: Fehler Product: Eclipse 1.2.0.20090618-0925 (org.eclipse.epp.package.php.product) Plugin: org.eclipse.jface Session Data: eclipse.buildId=I20090611-1540 java.version=1.6.0_14 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE Framework arguments: -product org.eclipse.epp.package.php.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.php.product Exception Stack Trace: org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) at org.eclipse.jface.viewers.AbstractTreeViewer.getExpandedState(AbstractTreeViewer.java:1196) at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.expand(OpenAndExpand.java:265) at org.eclipse.jdt.internal.ui.navigator.OpenAndExpand.run(OpenAndExpand.java:51) at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:221) at org.eclipse.ui.navigator.CommonNavigatorManager$3.open(CommonNavigatorManager.java:202) at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:842) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.runtime.Platform.run(Platform.java:888) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:840) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1101) at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:467) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1205) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:264) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:258) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:298) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
|
2009-08-04 02:23:35
| 1,249,370,000
|
resolved fixed
|
7e19513
| 1,250,520,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/OpenAndExpand.java
|
JDT
|
740
| 283,413
|
Bug 283413 [content assist] Package-level javadoc requires fully-qualified refs for @see and @link tags
|
Currently, eclipse will auto-complete class names in the current package, but they are not fully qualified. This produces warnings when running javadoc, and the hyperlinks are not generated.
|
2009-07-14 09:41:26
| 1,247,580,000
|
verified fixed
|
e63162b
| 1,250,510,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/LazyJavaTypeCompletionProposal.java
|
JDT
|
741
| 285,854
|
Bug 285854 [build path] javadoc location can't be changed to domain name if ip is given
| null |
2009-08-06 08:46:06
| 1,249,560,000
|
resolved fixed
|
26dd526
| 1,249,990,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocWizard.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavadocConfigurationPropertyPage.java
|
JDT
|
742
| 285,852
|
Bug 285852 [build path] Validating Javadoc url seems to have no effect
| null |
2009-08-06 08:39:33
| 1,249,560,000
|
resolved fixed
|
69f7dff
| 1,249,920,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavadocConfigurationBlock.java
|
JDT
|
743
| 285,573
|
Bug 285573 [quick fix] Wrong quickfix proposal for operations involving double and Integer
|
Build ID: I20090803-1800 Steps To Reproduce: Integer value = 4711; double test = 47d; value = value + test; //Line3: Error Line 3 is marked with a compilation error (Type mismatch: cannot convert from double to Integer) and one of the quick fixes suggest "Add a cast to 'Integer'". However, this is wrong and will not fix the compilation error as double to Integer cast is not allowed. More information:
|
2009-08-04 08:47:07
| 1,249,390,000
|
resolved fixed
|
59ec55d
| 1,249,590,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedMethodsQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/dom/Bindings.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/TypeMismatchSubProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/UnresolvedElementsSubProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/CastCorrectionProposal.java
|
JDT
|
744
| 100,593
|
Bug 100593 [quick fix] proposes wrong cast from Object to primitive int
|
I20050617-0010 void m(Object obj) { int i= obj; } In a 5.0 project, a quick fix proposes 'Add cast to (int)', which is wrong. The right cast here would be to (Integer), which would then be autounboxed. In a 1.4 project, no 'Add cast ..' quick fix is proposed, which is correct.
|
2005-06-17 11:27:04
| 1,119,020,000
|
resolved fixed
|
be6845e
| 1,249,570,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/TypeMismatchQuickFixTests.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/TypeMismatchSubProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/CastCorrectionProposal.java
|
JDT
|
745
| 181,040
|
Bug 181040 [actions] Consider removing "Create New Java Project" as default from toolbar
|
3.3 M6 In an effort to reduce the number of toolbar items to allow space for other plugins: We should consider removing "Create New Java Project" as being present by default in the toolbar. Generally speaking, toolbar items should be used to represent frequently accessed items (e.g. see MS Vista guidelines). Creation of Java projects is not a frequent task, because project creation is inherently infrequent as they are long lived, second because in Eclipse people tend to create them via PDE and lastly via download from say CVS.
|
2007-04-04 15:15:09
| 1,175,710,000
|
resolved fixed
|
ada51e5
| 1,249,560,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaPerspectiveFactory.java
|
JDT
|
746
| 285,558
|
Bug 285558 [misc] Source attached shows blank untill reopened in the editor
| null |
2009-08-04 07:11:54
| 1,249,380,000
|
verified fixed
|
c3ad319
| 1,249,470,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ClassFileEditor.java
|
JDT
|
747
| 285,645
|
Bug 285645 [navigation] 'Open Implementation' doesn't detect method after last character
|
Put the cursor behind a valid method name and hit "Open Implementation". It says that you need to selected a overridable method. As other features like Open Call Hierarchy, mark occurences, etc allow to span the selection backwards, it should be consistent. public class A { protected void foo|() { } } Pipe marks the cursor.
|
2009-08-04 18:10:18
| 1,249,420,000
|
verified fixed
|
9ffee04
| 1,249,460,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementImplementationHyperlink.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenImplementationAction.java
|
JDT
|
748
| 50,607
|
Bug 50607 [extract method] Name ambiguous return value in error message
|
Sometimes a get an error message about ambigous return values, when I want to extract a method. This message is correct, but not very comforable. It would be better to explicitly name all variables that are ambigous to be able to decide which variables must be refactored first. best regards Thorsten van Ellen P.S.: Of course, it would be much better, if the refactoring could refactor those variables, too. One simplistic way could be, to use "PrimitiveVariable"-classes as "value by reference", e.g. ObjectVariable and IntVariable: class ObjectVariable { public Object value; public ObjectVariable(Object value) { this.value = value; } } class IntVariable { public int value; public ObjectVariable(int value) { this.value = value; } }
|
2004-01-26 09:45:43
| 1,075,130,000
|
verified fixed
|
5e1c430
| 1,249,330,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodAnalyzer.java
|
JDT
|
749
| 152,004
|
Bug 152004 [extract method] should declare method static if extracted from anonymous in static method
|
I20060725-0800 public class Try { public static void main(String[] args) { new Runnable() { public void run() { //extract method on "xx", extract to class Try System.out.println("xx"); } }; } } The extracted method is nonstatic, which results in a compile error.
|
2006-07-27 10:28:53
| 1,154,010,000
|
verified fixed
|
2d9832b
| 1,249,320,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_in/A_test1052.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_in/A_test1053.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_out/A_test1052.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_out/A_test1053.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ExtractMethodTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodRefactoring.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/code/ExtractMethodInputPage.java
|
JDT
|
750
| 284,769
|
Bug 284769 [Extract Superclass] IOOBE extracting superclass
|
Build ID: M20090211-1700 Steps To Reproduce: 1. Run 'Refactor > Extract Superclass' on the included class. 2. Select target, defaultTarget, enroll(), cancel() as elements to pull up. Name the new class MultiplexingStream 3. Hit next until the IOOBE is thrown. Marking as 'major' since I can't refactor. More information: eclipse.buildId=I20090618-1753 java.fullversion=J2RE 1.5.0 IBM J9 2.3 Linux x86-32 j9vmxi3223ifx-20090422 (JIT enabled) J9VM - 20090421_34076_lHdSMr JIT - 20081112_1511ifx6_r8 GC - 200811_07 BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_CA Command-line arguments: -os linux -ws gtk -arch x86 -console Error Mon Jul 27 11:16:01 EDT 2009 Internal Error java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:934) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.createChange(RefactoringWizard.java:584) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.computeUserInputSuccessorPage(RefactoringWizard.java:423) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.computeSuccessorPage(UserInputWizardPage.java:75) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.getNextPage(UserInputWizardPage.java:115) at org.eclipse.jdt.internal.ui.refactoring.PullUpMethodPage.getNextPage(PullUpMethodPage.java:446) at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:813) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:144) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:156) at org.eclipse.jdt.internal.ui.refactoring.actions.RefactoringStarter.activate(RefactoringStarter.java:37) at org.eclipse.jdt.internal.corext.refactoring.RefactoringExecutionStarter.startExtractSupertypeRefactoring(RefactoringExecutionStarter.java:302) at org.eclipse.jdt.internal.ui.actions.ExtractSuperClassAction.run(ExtractSuperClassAction.java:141) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) Caused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: -1 at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeConstraintsModel.createMethodParameterVariable(SuperTypeConstraintsModel.java:386) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeConstraintsCreator.endVisit(SuperTypeConstraintsCreator.java:405) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeConstraintsCreator.endVisit(SuperTypeConstraintsCreator.java:243) at org.eclipse.jdt.core.dom.ClassInstanceCreation.accept0(ClassInstanceCreation.java:337) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2525) at org.eclipse.jdt.core.dom.VariableDeclarationFragment.accept0(VariableDeclarationFragment.java:225) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2548) at org.eclipse.jdt.core.dom.FieldDeclaration.accept0(FieldDeclaration.java:287) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2548) at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2548) at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:214) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeRefactoringProcessor.performFirstPass(SuperTypeRefactoringProcessor.java:734) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeRefactoringProcessor$3.acceptAST(SuperTypeRefactoringProcessor.java:1210) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:721) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:474) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:736) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeRefactoringProcessor.solveSuperTypeConstraints(SuperTypeRefactoringProcessor.java:1206) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.access$0(PullUpRefactoringProcessor.java:1) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor$1.acceptAST(PullUpRefactoringProcessor.java:1899) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:721) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:474) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:736) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.rewriteTypeOccurrences(PullUpRefactoringProcessor.java:1881) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.createChangeManager(PullUpRefactoringProcessor.java:1225) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.checkFinalConditions(PullUpRefactoringProcessor.java:746) at org.eclipse.jdt.internal.corext.refactoring.structure.ExtractSupertypeProcessor.checkFinalConditions(ExtractSupertypeProcessor.java:237) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:225) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Root exception: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: -1 at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeConstraintsModel.createMethodParameterVariable(SuperTypeConstraintsModel.java:386) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeConstraintsCreator.endVisit(SuperTypeConstraintsCreator.java:405) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeConstraintsCreator.endVisit(SuperTypeConstraintsCreator.java:243) at org.eclipse.jdt.core.dom.ClassInstanceCreation.accept0(ClassInstanceCreation.java:337) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.core.dom.ASTNode.acceptChild(ASTNode.java:2525) at org.eclipse.jdt.core.dom.VariableDeclarationFragment.accept0(VariableDeclarationFragment.java:225) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2548) at org.eclipse.jdt.core.dom.FieldDeclaration.accept0(FieldDeclaration.java:287) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2548) at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2548) at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:214) at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2478) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeRefactoringProcessor.performFirstPass(SuperTypeRefactoringProcessor.java:734) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeRefactoringProcessor$3.acceptAST(SuperTypeRefactoringProcessor.java:1210) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:721) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:474) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:736) at org.eclipse.jdt.internal.corext.refactoring.structure.constraints.SuperTypeRefactoringProcessor.solveSuperTypeConstraints(SuperTypeRefactoringProcessor.java:1206) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.access$0(PullUpRefactoringProcessor.java:1) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor$1.acceptAST(PullUpRefactoringProcessor.java:1899) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:721) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:474) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:736) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.rewriteTypeOccurrences(PullUpRefactoringProcessor.java:1881) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.createChangeManager(PullUpRefactoringProcessor.java:1225) at org.eclipse.jdt.internal.corext.refactoring.structure.PullUpRefactoringProcessor.checkFinalConditions(PullUpRefactoringProcessor.java:746) at org.eclipse.jdt.internal.corext.refactoring.structure.ExtractSupertypeProcessor.checkFinalConditions(ExtractSupertypeProcessor.java:237) at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:225) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
|
2009-07-27 11:27:09
| 1,248,710,000
|
verified fixed
|
feaf7d0
| 1,249,310,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/constraints/SuperTypeConstraintsModel.java
|
JDT
|
751
| 285,437
|
Bug 285437 [extract superclass] action not enabled any more when class is selected
|
3.5 'Refactor > Extract Superclass' action is not enabled any more when a class is selected.
|
2009-08-03 09:43:35
| 1,249,310,000
|
verified fixed
|
d443bb6
| 1,249,310,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringAvailabilityTester.java
|
JDT
|
752
| 280,333
|
Bug 280333 [refactoring] enhance Javadoc of RefactoringWizard.performFinish() (was: Refactoring wizard remains open with enabled buttons after refactoring operation completes)
|
Refactoring wizard remains open with enabled buttons after refactoring operation completes. When an extension of the org.eclipse.ltk.ui.refactoring.RefactoringWizard performs steps after the call to org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish() in the <subclass>.performFinish() method, the refactoring wizard remains open with the Finish/Next buttons enabled until the <subclass>.performFinish() method terminates. Steps to reproduce: 1) Create a extension of the org.eclipse.ltk.ui.refactoring.RefactoringWizard. 2) In the <subclass>.performFinish() method, call org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish() and then: try { Thread.sleep(5000); } catch (Exception e) { e.printStackTrace(); } 3) Open the refactoring wizard and finish the operation (click Finish). 4) Note the Next/Finish buttons remain disabled until the refactoring operation terminates and then enable for the 5 second sleep before the refactoring wizard is closed.
|
2009-06-15 15:34:44
| 1,245,090,000
|
closed fixed
|
56b557e
| 1,249,300,000
|
org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/RefactoringWizard.java
|
JDT
|
753
| 267,369
|
Bug 267369 [navigation] 'Open Implementation' should also be available as command
|
I20090304-0834 'Open Implementation' should also be available as a command, so I can assign a key binding like for 'Open Super Implementation'.
|
2009-03-06 09:31:09
| 1,236,350,000
|
verified fixed
|
fa93d0c
| 1,249,290,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/IJavaHelpContextIds.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/ActionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementImplementationHyperlink.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/IJavaEditorActionDefinitionIds.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/JdtActionConstants.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenImplementationAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenSuperImplementationAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenViewActionGroup.java
|
JDT
|
754
| 48,966
|
Bug 48966 [preferences] Should be able to export from 'Formatter' preference page
|
I200312162000 I am used that I can press Export and Import on the preference dialog and get the formatter prefs as well. We now introduced another page where the user has to do this manually. This might change with the new settings story. In addition, I cannot export my formatter prefs at once: I have to export every single profile manually.
|
2003-12-17 05:00:27
| 1,071,660,000
|
verified fixed
|
acfa974
| 1,249,030,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/FormatterMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/ProfileConfigurationBlock.java
|
JDT
|
755
| 285,024
|
Bug 285024 [ltk] Cannot run PerformChangeOperation in "null" ISchedulingRule
|
It is not fair for the PerformChangeOperation#setSchedulingRule() API call to not allow a "null" scheduling rule. There are some TextChange's that do not require any rules at all to run, like DocumentChange. Please loosen the API restrictions to allow a null scheduling rule.
|
2009-07-29 11:51:03
| 1,248,880,000
|
resolved fixed
|
74f6e04
| 1,248,960,000
|
org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/PerformChangeOperation.java
|
JDT
|
756
| 284,793
|
Bug 284793 [quick assist] convert anonymous type fails silently if a class of the destination name already exists
|
Build ID: I20090611-1540 Steps To Reproduce: 1. Paste the class below into a new project. 2. Invoke Ctrl+1 -> "Convert anonymous to nested class" on first Runnable (accept the default class name) 3. Invoke Ctrl+1 -> "Convert anonymous to nested class" on the second Runnable. 4. Observe that no refactoring is performed for the second invocation. (It works if you either change the class name or use the Refactor menu for the second refactoring instead of the quickfix) public class MultiAnonymous { Runnable x = new Runnable() { public void run() { System.out.println(0); } }; Runnable y = new Runnable() { public void run() { System.out.println(42); } }; }
|
2009-07-27 14:41:17
| 1,248,720,000
|
resolved fixed
|
2cc7ae0
| 1,248,790,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AssistQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/QuickAssistProcessor.java
|
JDT
|
757
| 283,891
|
Bug 283891 [JUnit] Add camel case support in TestSelectionDialog
|
The Test Selection Dialog doesn't have the powerful camel case support that the Open Type dialog has. Can you add it?
|
2009-07-17 15:51:18
| 1,247,860,000
|
resolved fixed
|
e916ac3
| 1,248,720,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/launcher/TestSelectionDialog.java org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/launcher/JUnitLaunchConfigurationTab.java
|
JDT
|
758
| 283,851
|
Bug 283851 Very Minor cleanup in JUnitLaunchConfigurationTab
|
Build ID: M20090211-1700 Steps To Reproduce: private void setTestMethodLabel(String testMethodName) { if (!"".equals(testMethodName)) { fTestMethodLabel.setText(JUnitMessages.JUnitLaunchConfigurationTab_label_method+fOriginalTestMethodName); } else { fTestMethodLabel.setText(""); } } This method is only used once, accepts the test method name, and yet still uses the class variable. Minor nit, but you should consistently use the parameter. More information:
|
2009-07-17 10:03:32
| 1,247,840,000
|
resolved fixed
|
6618d8f
| 1,247,850,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/launcher/JUnitLaunchConfigurationTab.java
|
JDT
|
759
| 283,304
|
Bug 283304 [JUnit] ITestRunSession should return launched project
|
Please add access for getLaunchedProject() of org.eclipse.jdt.internal.junit.model.TestRunSession in org.eclipse.jdt.junit.model.ITestRunSession. My problem is that i need the launched project to reproduce and analyse the testCases (ITestCaseElement). The only "data" i get is the testClassName and testMethodName but that is not unique in the workspace. If you make getLaunchedProject() public over ITestRunSession, i will find the correct testCase everytime correct. Workaround is so cast the org.eclipse.jdt.junit.model.ITestRunSession object into org.eclipse.jdt.internal.junit.model.TestRunSession and invoke getLaunchedProject(). But this is the bad way cause TestRunSession is internal.
|
2009-07-13 07:55:31
| 1,247,490,000
|
resolved fixed
|
55d8be4
| 1,247,850,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestRunSession.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/junit/model/ITestRunSession.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/TestRunSession.java org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/model/ITestRunSession.java
|
JDT
|
760
| 283,697
|
Bug 283697 [quick fix] Add missing @Override should be first on suggestions
|
When using JDK 1.5, and I press control-1 on an elem with a missing override warning, the "Add missing @Override" is last on the list, after a bunch of (most of the time) useless suggestions about renaming or creating methods. Adding the @Override is what is wanted almost all of the time.
|
2009-07-16 08:37:09
| 1,247,750,000
|
resolved fixed
|
8f6662e
| 1,247,750,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/ModifierCorrectionSubProcessor.java
|
JDT
|
761
| 239,490
|
Bug 239490 [working sets][package explorer] Newly created incompatible working sets appear in Package Explorer
|
Build ID: I20080617-2000 Steps To Reproduce: 1.Create a plugin project working set. 2.Add a plugin project to this working set. 3.Create a Java project working set. 4.Add a Java project to this working set. 5.Try to add a plugin project working set -> Only Java project working sets are now allowed to be created! Where are the plugin project working sets now? 6. After here only Java project working sets are showed in the Package Explorer. More information:
|
2008-07-03 13:16:35
| 1,215,110,000
|
resolved fixed
|
c16c6a3
| 1,247,650,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/WorkingSetConfigurationDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/WorkingSetModel.java
|
JDT
|
762
| 97,413
|
Bug 97413 [extract method] missing return type when code can throw exception
|
I20050527-1300 Extracting code that can return a value and ends with throwing an exception results in a new method with no return type - and therefore compile errors. No other errors or exceptions. Before: class Foo { int bar(int bar) { if (bar > 0) return bar - 1; throw new IllegalArgumentException(); } } After: class Foo { int bar(int bar) { foo(bar); } private void foo(int bar) { if (bar > 0) return bar - 1; throw new IllegalArgumentException(); } } Swapping the return and the throw statements works. Before: class Foo { int bar(int bar) { if (bar > 0) throw new IllegalArgumentException(); return bar - 1; } } After: class Foo { int bar(int bar) { return foo(bar); } private int foo(int bar) { if (bar > 0) throw new IllegalArgumentException(); return bar - 1; } }
|
2005-05-31 06:10:09
| 1,117,530,000
|
verified fixed
|
ca0caf4
| 1,247,510,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_in/A_test733.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_in/A_test734.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_out/A_test733.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_out/A_test734.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ExtractMethodTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/FlowInfo.java
|
JDT
|
763
| 213,519
|
Bug 213519 [extract method] Missing return value, while extracting code out of a loop
|
Build ID: M20071023-1652 Steps To Reproduce: There is a curious behavior of extract method when extracting a code snippet out of a loop after a for(Class var : Colection) construction. More information: Sample Code: ------------------------------------ Line of code to extract: list.add(a++); ------------------------------------ Code where Extract Method returns an int as return value of the extracted snippet: Good Code: ------------------------------------ ArrayList<Integer> list = new ArrayList<Integer>(); int a = 0; for (int c = 0; c < 10; c++) { list.add(a++); } System.out.println(list.toString()); ------------------------------------ Method signature: private static int someMethodName(ArrayList<Integer> list,int a) After adding a for loop in front of the counting loop, the Extract Method return value is void. Bad Code: ------------------------------------ ArrayList<Integer> list = new ArrayList<Integer>(); for (Integer var: list) {} int a = 0; for (int c = 0; c < 10; c++) { list.add(a++); } System.out.println(list.toString()); ------------------------------------ Method signature: private static void someMethodName(ArrayList<Integer> list,int a)
|
2007-12-19 14:53:37
| 1,198,090,000
|
verified fixed
|
a9ead9f
| 1,247,500,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_in/A_test729.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_in/A_test730.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_in/A_test731.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_in/A_test732.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_out/A_test729.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_out/A_test730.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_out/A_test731.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/return_out/A_test732.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ExtractMethodTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/InputFlowAnalyzer.java
|
JDT
|
764
| 160,853
|
Bug 160853 [extract method] Does not replace similar code in parent class of anonymous class
|
I20061010-0800 Given: package a.b; public class Foo { public void foo() { Object obj= new Object() { public String toString() { return "foo." + getName(); } }; String s= "foo." + getName(); } private String getName() {return "bar";} } 1. Select _second_ expression "foo." + getName() 2. Refactor>Extract Method... 3. extract method 'qualifiedName' Is: both expressions "foo." + getName() are replaced by a call to qualifiedName, correct. 4. Undo 5. Select first expression "foo." + getName() 6. Refactor>Extract Method... 7. Select 'Foo' as destination type 8. extract method 'qualifiedName' Is: Only first expression is replaced by call Should: Both expression should be replaced, at least I can't see no difference...
|
2006-10-13 09:04:24
| 1,160,740,000
|
verified fixed
|
c5b435d
| 1,247,500,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/duplicates_in/A_test971.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/duplicates_in/A_test972.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/duplicates_out/A_test971.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/duplicates_out/A_test972.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ExtractMethodTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodRefactoring.java
|
JDT
|
765
| 280,755
|
Bug 280755 [working sets] Check out into new working set results into strange working set
|
3.5 but not 3.4.x. Not directly a regression because in 3.4.x it was not possible to create a working set in the Check Out dialog. Steps to reproduce: 0. start new workspace 1. select project 'org.eclipse.core.expressions' in the CVS Repositories view 2. context menu > Check Out As... 3. in the dialog choose to add project to a Java working set (create it now) 5. click 'Finish' 6. open the Project Explorer 7. in the Project Explorer select 'Working Sets' as 'Top Level Element' 8. select the working set from step 3 9. expand the working set ==> two nodes one being a org.eclipse.team.internal.ccvs.core.resources.RemoteFolder resulting in label error. Step 3 where the new working set is created is the culprit: it has the remote project/folder preselected.
|
2009-06-18 07:53:07
| 1,245,330,000
|
verified fixed
|
d12677d
| 1,245,400,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/JavaWorkingSetPage.java
|
JDT
|
766
| 279,425
|
Bug 279425 [organize imports] MultiElementListSelectionDialog has wrong button layout
|
3.5 RC4. MultiElementListSelectionDialog has wrong button layout if Display.getDismissalAlignment() == SWT.RIGHT, e.g. Mac or Linux.
|
2009-06-08 05:02:04
| 1,244,450,000
|
verified fixed
|
c7f46a8
| 1,245,320,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/MultiElementListSelectionDialog.java
|
JDT
|
767
| 279,715
|
Bug 279715 [inline] Inline Constant and Inline Local Variable are missing parentheses for extended '-' chains
|
I20090605-1444 Inline Constant and Inline Local Variable are missing parentheses for extended '-' chains: public class Try { public static final int B= 12; public static final int C= B - 1; //inline C public static final int K= 99; public static void main(String[] args) { // int B= 12; // int C= B - 1; //inline C // int K= 99; int f1= K - 1 - C; int f2= K - C - C - C; int x1= K + C; int x2= K - C; int x3= K + 1 - C; int x4= K - 1 + C; int x5= K + 1 + C - C - C; } }
|
2009-06-09 18:36:18
| 1,244,590,000
|
verified fixed
|
c37e6e1
| 1,245,170,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/InlineConstant/canInline/test33/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineConstant/canInline/test33/out/A.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/InlineConstantTests.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/dom/ASTNodes.java
|
JDT
|
768
| 279,924
|
Bug 279924 [toString] toString() generator: Fields in declaration order
|
toString() generator adding the fields in alphabetical order. It would be better if it adds in the order whatever the order fields declared in the class.
|
2009-06-11 07:12:35
| 1,244,720,000
|
resolved fixed
|
086c6ad
| 1,245,170,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaUIMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/GenerateToStringDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/GenerateMethodAbstractAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/GenerateToStringAction.java
|
JDT
|
769
| 280,123
|
Bug 280123 [typing] BadLocationException when pasting word "default" outside of class
|
- copy the word "default" (without the quotes) to the clipboard - create a new class, it will look like public class Test2 { } - put the caret on the line following the class' closing brace and press Ctrl+V -> an internal error is logged with the stack below org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.TreeLineTracker.fail(TreeLineTracker.java:1061) at org.eclipse.jface.text.TreeLineTracker.getLineInformationOfOffset(TreeLineTracker.java:1157) at org.eclipse.jface.text.AbstractLineTracker.getLineInformationOfOffset(AbstractLineTracker.java:145) at org.eclipse.jface.text.AbstractDocument.getLineInformationOfOffset(AbstractDocument.java:902) at org.eclipse.core.internal.filebuffers.SynchronizableDocument.getLineInformationOfOffset(SynchronizableDocument.java:353) at org.eclipse.jdt.internal.ui.text.java.JavaAutoIndentStrategy.smartPaste(JavaAutoIndentStrategy.java:663) at org.eclipse.jdt.internal.ui.text.java.JavaAutoIndentStrategy.customizeDocumentCommand(JavaAutoIndentStrategy.java:1224) at org.eclipse.jface.text.TextViewer.customizeDocumentCommand(TextViewer.java:3734) at org.eclipse.jface.text.TextViewer.handleVerifyEvent(TextViewer.java:3764) at org.eclipse.jface.text.source.projection.ProjectionViewer.handleVerifyEvent(ProjectionViewer.java:1276) at org.eclipse.jface.text.TextViewer$TextVerifyListener.verifyText(TextViewer.java:433) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:828) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:849) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:835) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:607) at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:6602) at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:7442) at org.eclipse.swt.custom.StyledText.paste(StyledText.java:6690) at org.eclipse.jface.text.TextViewer.paste(TextViewer.java:4026) at org.eclipse.jface.text.TextViewer.doOperation(TextViewer.java:3970) at org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:921) at org.eclipse.jface.text.source.projection.ProjectionViewer.doOperation(ProjectionViewer.java:1533) at org.eclipse.jdt.internal.ui.javaeditor.JavaSourceViewer.doOperation(JavaSourceViewer.java:186) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:199) at org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction.doPasteWithImportsOperation(ClipboardOperationAction.java:501) at org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction.internalDoOperation(ClipboardOperationAction.java:287) at org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction$1.run(ClipboardOperationAction.java:258) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction.run(ClipboardOperationAction.java:256) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:470) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:824) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:880) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:569) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:510) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:125) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:904) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:827) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:849) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:835) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:941) at org.eclipse.swt.widgets.Widget.XKeyPress(Widget.java:1166) at org.eclipse.swt.widgets.Composite.XKeyPress(Composite.java:1437) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1112) at org.eclipse.swt.widgets.Display.windowProc(Display.java:3773) at org.eclipse.swt.internal.motif.OS._XtDispatchEvent(Native Method) at org.eclipse.swt.internal.motif.OS.XtDispatchEvent(OS.java:5099) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2829) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
|
2009-06-12 14:44:58
| 1,244,830,000
|
resolved fixed
|
40d20b1
| 1,245,160,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JavaAutoIndentStrategyTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaAutoIndentStrategy.java
|
JDT
|
770
| 101,233
|
Bug 101233 [extract method] remember selected access modifier
|
In subsequence calling the Refactor-ExtractCommand one has to set the access modifier always if the default selection ("private") is not desired. It would be nice if the editor can memorise the selected modifier as the editor do with the checkbox "Qualify constant references with class name"
|
2005-06-22 08:16:59
| 1,119,440,000
|
verified fixed
|
6fb0eaf
| 1,245,080,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/code/ExtractMethodInputPage.java
|
JDT
|
771
| 280,193
|
Bug 280193 [quick fix] NPE on "add type arguments"
| null |
2009-06-14 07:32:47
| 1,244,980,000
|
resolved fixed
|
4ceae83
| 1,245,080,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/Java50Fix.java
|
JDT
|
772
| 280,245
|
Bug 280245 [nls tooling] Properties file editor screws selection on double-click
|
I20090611-1540 (had it on Cocoa and WinXP) The properties file editor screws the selection on double-click for certain properties: - Have a.properties with content: 123.ch: Hello - double-click before '2' => selection is '23.c' => expected: whole property 'abc.ch' selected or just 'abc' (like in 3.4.2)
|
2009-06-15 05:32:09
| 1,245,060,000
|
resolved fixed
|
443bbc1
| 1,245,060,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesFileSourceViewerConfiguration.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/PartitionDoubleClickSelector.java
|
JDT
|
773
| 277,968
|
Bug 277968 [inline] Inline local variable gets type parameters on static methods wrong
|
Build ID: I20090522-1710 java.version=1.6.0_13 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB Command-line arguments: -os win32 -ws win32 -arch x86_64 Steps To Reproduce: 1. Create a class like: class InlineMethodParam { String foo() { String t = bar(); return t; } static <T> T bar() { return null; } } 2. Attempt to inline t. 3. You'll get: return <String>bar(); To be legal, you need return InlineMethodParam.<String>bar();.
|
2009-05-26 19:26:28
| 1,243,380,000
|
resolved fixed
|
a7a5505
| 1,244,830,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/InlineTemp/canInline/A_test37_in.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineTemp/canInline/A_test37_out.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineTemp/canInline/A_test38_in.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineTemp/canInline/A_test38_out.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineTemp/canInline/A_test39_in.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineTemp/canInline/A_test39_out.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/InlineTempTests.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/InlineTempRefactoring.java
|
JDT
|
774
| 277,031
|
Bug 277031 [rename] Renaming type parameter also renames arguments of the same name
|
Build ID: I20090515-1143 java.version=1.6.0_13 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB Command-line arguments: -os win32 -ws win32 -arch x86_64 Steps To Reproduce: 1. Create a class like: class Badger<Queue> { void bar(Queue Queue) { Queue.notify(); } } 2. Place the cursor in <Queue> and trigger a rename (alt+shift+r 3. Change it to "Foo". Note that, in the preview, the method declaration line reads: void bar(Bar Queue) 4. Press enter to apply it. 5. All instances of Queue in the file will have been replaced with Bar, so it will now read: class Badger<Bar> { void bar(Bar Bar) { Bar.notify(); } } Surely only the ones shown in the preview should be renamed?
|
2009-05-19 19:03:56
| 1,242,770,000
|
resolved fixed
|
efaeb43
| 1,244,830,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/RenameTypeParameter/test15/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/RenameTypeParameter/test15/out/A.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/RenameTypeParameterTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameTypeParameterProcessor.java
|
JDT
|
775
| 279,981
|
Bug 279981 Constructor inlining produces illegal result.
|
Build ID: I20090605-1444 (3.5RC4) Please select identifier "Local" on LINE 4 and try to inline. The result won't compile. class Bug { { class Local { Local(int x){ //LINE 4 } } new Local(hashCode()); } }
|
2009-06-11 13:31:18
| 1,244,740,000
|
resolved fixed
|
ad72ff3
| 1,244,830,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/TargetProvider.java
|
JDT
|
776
| 276,111
|
Bug 276111 [JUnit] classpath container doesn't pick up JUnit jars in shared installations
| null |
2009-05-13 11:08:42
| 1,242,230,000
|
closed fixed
|
395b94c
| 1,244,810,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/P2Utils.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/buildpath/P2Utils.java
|
JDT
|
777
| 277,812
|
Bug 277812 [call hierarchy] [working sets] Add F1 Help for Call Hierarchy Filters, Expand With Constructors Dialog, Working Set Configuration Dialog , Working Set Assignments Dialog
| null |
2009-05-26 04:46:48
| 1,243,330,000
|
verified fixed
|
2728168
| 1,243,520,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/IJavaHelpContextIds.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/ExpandWithConstructorsDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/ConfigureWorkingSetAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/ConfigureWorkingSetAssignementAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/WorkingSetConfigurationDialog.java
|
JDT
|
778
| 277,556
|
Bug 277556 [preferences] Syntax Coloring Preview Window is showing colors to incorrect char set for classes element
|
Build ID: I20090515-1143 Steps To Reproduce: 1.Go to preference page [Window->Preferences] 2.Select Syntax Coloring [Java -> Editor -> Syntax Coloring] 3.Enable coloring for Classes [check enable and provide new color other than black [more visible color will be good to identify in one shot] 4. Check Preview, you will find that "ame<St" will be colored as you selected instead of "String". public class ClassName<E> implements InterfaceName<String> { More information: I think parsing start index is problem, because total number of colored chars are correct.
|
2009-05-22 18:08:04
| 1,243,030,000
|
verified fixed
|
d977efc
| 1,243,270,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaEditorColoringConfigurationBlock.java
|
JDT
|
779
| 276,486
|
Bug 276486 [content assist] anonymous type completion does not add method implementation stubs when type already imported
|
I20090514-2000 Content assist: Anonymous type completion does not add method implementation stubs when type already imported. Example: import java.util.AbstractCollection; public class Runner { private void foo() { new AbstractColl } } => Content assist after 'new AbstractColl' only gives: new AbstractCollection<E>() { }; => Expected: Method implementation stubs are added, like when the 'import java.util.AbstractCollection;' is not there.
|
2009-05-15 08:47:06
| 1,242,390,000
|
verified fixed
|
1682386
| 1,242,760,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/AnonymousTypeCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/CompletionProposalLabelProvider.java
|
JDT
|
780
| 276,708
|
Bug 276708 [content assist] code assist in file of simple project logs exception
|
I20090515-1143. Broken since 3.3 but fix would be very simple. Markus, what do you think?
|
2009-05-18 09:58:05
| 1,242,660,000
|
verified fixed
|
ca1c1e5
| 1,242,740,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/JavaContentAssistInvocationContext.java
|
JDT
|
781
| 276,364
|
Bug 276364 [content assist] Anonymous constructor completion adds a ')' too much
|
I20090513-2000 Anonymous constructor completion adds a ')' too much: public class Try { void method(Runnable r) { method(new Run) } } - set prefs > Content Assist > Completion inserts - put caret after 'new Run' - content assist, choose 'Runnable() Anonymous Inner Type' => result: method(new Runnable() { public void run() { // TODO Auto-generated method stub } })) => expected: only 1 closing parenthesis at the end
|
2009-05-14 14:44:22
| 1,242,330,000
|
verified fixed
|
e004fdf
| 1,242,740,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/AnonymousTypeCompletionProposal.java
|
JDT
|
782
| 276,744
|
Bug 276744 [hashcode/equals] New 3.5 feature not working: [hashcode/equals] Wizard should allow to specify that blocks should always be used
| null |
2009-05-18 12:17:05
| 1,242,660,000
|
verified fixed
|
603d6ef
| 1,242,740,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/GenerateHashCodeEqualsAction.java
|
JDT
|
783
| 274,511
|
Bug 274511 [call hierarchy] improve context menu
|
I20090429-1800. The Call Hierarchy's context menu is confusing: the 'Copy Expanded Hierarchy' should be together with the other copy/paste actions. The confusion is now more prominent with the new 'Expand with Constructors'.
|
2009-04-30 09:41:05
| 1,241,100,000
|
verified fixed
|
a66d26b
| 1,242,290,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/PasteAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java
|
JDT
|
784
| 276,102
|
Bug 276102 [quick assist] 'convert to enhanced for loop' unnecessarily blocked for multiple-assigned variable
| null |
2009-05-13 10:50:40
| 1,242,230,000
|
verified fixed
|
0364db2
| 1,242,240,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/ConvertForLoopOperation.java
|
JDT
|
785
| 274,199
|
Bug 274199 [quick assist] convert to enhanced for loop changes semantics for multiple-assigned variable
| null |
2009-04-28 18:34:21
| 1,240,960,000
|
verified fixed
|
18845e6
| 1,242,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/ConvertForLoopOperation.java
|
JDT
|
786
| 275,859
|
Bug 275859 [package explorer] Package Explorer not updated after resource reorgs in Working Sets mode
|
Eclipse 3.5M7 1. Select file(s) in the Package Explorer 2. Press Ctrl-Insert 3. Select a different project 4. Press Shift-Insert The copied file(s) won't be visible in the package explorer unless you manually refresh the destination project.
|
2009-05-12 08:30:34
| 1,242,130,000
|
verified fixed
|
8e03c79
| 1,242,140,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerContentProvider.java
|
JDT
|
787
| 275,308
|
Bug 275308 [JUnit] @RunWith(Parameterized) results don't navigate
|
Build ID: 3.5M7 ** This is trivial and safe (a 1 liner). Can you please get it in 3.5 before release ** Steps To Reproduce: 1. Compile and run the test below in with JUnit4, JDK5+ 2. Double-click on the failed test in the JUnit view Expected result: Should open the testIsFirst() method Actual result: "Method 'testIsFirst[1]' not found" Proposed (quick, safe) solution: trim to first "[" if search for the method fails, and try again. Could prob trim to first "[" straight away, but I'm no expert on what chars are allowed in function names by the JVM. ---- import static org.junit.Assert.assertEquals; import java.util.Collection; import org.junit.Test; import org.junit.runner.RunWith; import org.junit.runners.Parameterized; import org.junit.runners.Parameterized.Parameters; @RunWith(Parameterized.class) public class SimpleParamTest { @Parameters public static Collection<?> data() { return Parameterized.eachOne("First", "Second"); } private final String o; public SimpleParamTest(String o) { this.o = o; } @Test public void testIsFirst() throws Exception { assertEquals("First", o); } }
|
2009-05-07 10:33:13
| 1,241,710,000
|
verified fixed
|
39850a8
| 1,242,060,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/OpenTestAction.java
|
JDT
|
788
| 275,668
|
Bug 275668 [open type] revert using new API to open several editors at once
| null |
2009-05-11 10:54:55
| 1,242,050,000
|
verified fixed
|
ee22c39
| 1,242,060,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/OpenTypeAction.java
|
JDT
|
789
| 275,286
|
Bug 275286 [compare] createStructure is called three times for both sides when opening compare editor
| null |
2009-05-07 07:31:13
| 1,241,700,000
|
verified fixed
|
393c216
| 1,242,060,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/compare/JavaStructureDiffViewer.java
|
JDT
|
790
| 275,370
|
Bug 275370 [toString] Generator uses wrong suffixes and prefixes
|
Steps To Reproduce: When "Limit number of items..." option is selected, the maxLen variable in generated toString() method has parameter prefix and suffix appended instead of local variable ones.
|
2009-05-07 16:10:37
| 1,241,730,000
|
verified fixed
|
33295df
| 1,242,050,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/source/GenerateToStringTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/AbstractToStringGenerator.java
|
JDT
|
791
| 275,360
|
Bug 275360 [toString] Wrong code generated with String concatenation
|
When String concatenation style is used, wrong code is generated, for example: public class A { String ss[]; @Override public String toString() { final int maxLen = 10; return "A [ss=" + ss != null ? Arrays.asList(ss).subList(0, Math.min(ss.length, maxLen)) : null + "]"; } } The "ss != null ? .. : null" fragments should be enclosed in parenthesis, otherwise there's a compilation error or unexpected behavior.
|
2009-05-07 15:15:49
| 1,241,720,000
|
verified fixed
|
13822b2
| 1,242,040,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/source/GenerateToStringTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/StringConcatenationGenerator.java
|
JDT
|
792
| 274,474
|
Bug 274474 [call hierarchy] Expand With Constructors action should cancel all other current jobs running
|
Build ID: I20090427-1800 Steps To Reproduce: 1.Invoke call hierarchy in callers mode on any method that takes time to search for callers 2.open the context menu and click on "Expand With Constructors" Both jobs are running concurrently and both results are displayed => Should cancel all the searches that are happening on the same node when the action is invoked, and display only the new results. More information:
|
2009-04-30 03:23:24
| 1,241,080,000
|
verified fixed
|
df71dda
| 1,241,800,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/callhierarchy/MethodWrapper.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyContentProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyLabelProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/DeferredMethodWrapper.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/ExpandWithConstructorsAction.java
|
JDT
|
793
| 97,228
|
Bug 97228 [navigation] NLSKeyHyperlink to reveal/goto the key in the properties file editor
|
if you go to the key in the properties file editor in NLSKeyHyperlink, when the user klicks on a key in the java editor, you work with "hard coded" code! this is very bad because plugins like Jinto(which support a own properties file editor) have no chance to goto the right line in its editor! please go over IAdaptable(IGoToMarker???) and let make the editor do its job!!!
|
2005-05-30 08:32:05
| 1,117,460,000
|
verified fixed
|
9186068
| 1,241,770,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/NLSKeyHyperlink.java
|
JDT
|
794
| 273,615
|
Bug 273615 [Help][Context] NPE when trying to open help (F1) in drop-down.
| null |
2009-04-24 12:54:11
| 1,240,590,000
|
verified fixed
|
b5b7cc3
| 1,241,710,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/breadcrumb/BreadcrumbItemDropDown.java
|
JDT
|
795
| 275,291
|
Bug 275291 [clean up] clean up on save does too much if 'Additional actions' is unchecked
|
I20090506-2000. Clean up on save does too much if 'Additional actions' is unchecked: instead of just creating the import and format clean ups it creates and loops over all of them (but with disabled options). This can lead to nasty side effects up to executing other clean ups. Test Case: 1. import the attached project into your workspace 2. start target workspace 3. open a CU 4. change it 5. save ==> bad clean up is executed (see first line ;-)
|
2009-05-07 08:21:49
| 1,241,700,000
|
verified fixed
|
a3035ec
| 1,241,700,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CleanUpPostSaveListener.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CleanUpRegistry.java
|
JDT
|
796
| 274,412
|
Bug 274412 [toString] custom toString builder dialog should offer help
|
The "Configure custom toString builder" dialog should offer a help icon to directly jump to the "toString() Generator: Code Styles" page.
|
2009-04-29 15:59:52
| 1,241,040,000
|
verified fixed
|
85d700a
| 1,241,700,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/IJavaHelpContextIds.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/GenerateToStringDialog.java
|
JDT
|
797
| 133,518
|
Bug 133518 [JUnit] Wording of new 'enable assertions JUnit preference
|
I20060328-0010. We normally avoid to use 'Enable xyz' after a checkbox. In addition we should not use "JUnit launch configurations" because this could be misinterpreted: the preference also affects the 'JUnit Plug-in Test' launch config. Better might be: "Add '-ea' to VM arguments when creating new launch configuration".
|
2006-03-28 08:32:19
| 1,143,550,000
|
verified fixed
|
ae05c7f
| 1,241,610,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitMessages.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/JUnitPreferencePage.java
|
JDT
|
798
| 267,776
|
Bug 267776 [content assist] Wrong post-qualification for constructor and anonymous type completion
|
I20090309-0100. The post-qualification should not include the type and in the default package it looks strange.
|
2009-03-10 03:51:59
| 1,236,670,000
|
verified fixed
|
5613e27
| 1,241,530,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/CompletionProposalLabelProvider.java
|
JDT
|
799
| 274,364
|
Bug 274364 [quick fix] NPE in ASTNodeFactory when method return type is missing
|
I20090428-0100 Invoking quick fix on "foo" results in an NPE: public class Snippet { abstract foo(); } If Snippet is declared as interface the quick fix works fine.
|
2009-04-29 14:19:05
| 1,241,030,000
|
verified fixed
|
d61e47b
| 1,241,530,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/ModifierCorrectionSubProcessor.java
|
JDT
|
800
| 274,833
|
Bug 274833 [content assist] inserting anonymous type proposal not correctly formatted
|
3.5 M7. 1. type "new Runnable(" 2. content assist ==> new Runnable(){ ==> there's a missing space This is not a regression introduced by the new proposal kind but was already an issue in 3.4. The reason is that the string used to format is not always correct.
|
2009-05-04 10:09:36
| 1,241,450,000
|
verified fixed
|
b1b749c
| 1,241,520,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/CodeCompletionTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/AnonymousTypeCompletionProposal.java
|
JDT
|
801
| 274,473
|
Bug 274473 [call hierarchy] callers and constructor color updating broken
|
I20090429-1800. 1. open Call Hierarchy with some expanded constructors 2. change the 'Inherited Members' color 3. click 'Apply' or 'OK' ==> most of the time nothing happens i.e. the color is not updated but sometimes all nodes collapse. Expected: the color is updated on 'Apply' and 'OK' and no nodes are collapsed.
|
2009-04-30 02:54:03
| 1,241,070,000
|
verified fixed
|
a3b0576
| 1,241,460,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/ColoredViewersManager.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/ColoringLabelProvider.java
|
JDT
|
802
| 274,091
|
Bug 274091 [call hierarchy] Wrong behavior of Expand With Constructors on multi-selection with parent/child
|
I20090428-0100. When having a multi-selection of children (not siblings) in the Call Hierarchy the behavior of 'Expand With Constructors' is wrong: it only applies it on the first selected item. Either we should not offer the action in this case or we apply the state to all selected elements, so that when I later expand one of the callers I get the constructors as well. NOTE: multi-selection on siblings works as expected.
|
2009-04-28 11:39:46
| 1,240,930,000
|
verified fixed
|
9ce9ace
| 1,241,010,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/ExpandWithConstructorsAction.java
|
JDT
|
803
| 274,269
|
Bug 274269 [tostring] 'Configure...' button is clipped at the bottom
|
I20090429-0100. The 'Configure...' button is clipped at the bottom in the toString dialog.
|
2009-04-29 06:07:24
| 1,241,000,000
|
verified fixed
|
6ecdcfc
| 1,241,010,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/GenerateToStringDialog.java
|
JDT
|
804
| 271,436
|
Bug 271436 Reminder: mark activate editor tests gray if Platform UI does not fix the regression
| null |
2009-04-07 07:07:55
| 1,239,100,000
|
verified fixed
|
15d806d
| 1,241,010,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/ActivateTextEditorTest.java
|
JDT
|
805
| 274,041
|
Bug 274041 [JUnit] unable to add JUnit library to build path if eclipse install has space in path
| null |
2009-04-28 10:07:21
| 1,240,930,000
|
verified fixed
|
af117b2
| 1,241,010,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/P2Utils.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/buildpath/P2Utils.java
|
JDT
|
806
| 274,086
|
Bug 274086 [call hierarchy] blue constructor label decoration confusing/noisy
|
I20090428-0100. The blue [constructor] label decoration is noisy when there are more than the usual 1 constructor and it's confusing with the [callers] root node which is also rendered in blue. I would remove that.
|
2009-04-28 11:25:46
| 1,240,930,000
|
verified fixed
|
859692c
| 1,241,010,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyLabelProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/ColoringLabelProvider.java
|
JDT
|
807
| 271,446
|
Bug 271446 [call hierarchy] cannot restart canceled search for callers
|
I20090401-1325 - Call Hierarchy in Callers mode - expand a node where the search for references takes a long time (e.g. Object#hashCode()) - click 'Cancel Current Search' in view toolbar => expanded node gets a child 'The search was canceled' Now, there's no way to restart the canceled search again without refreshing the whole view. I don't think we need the 'The search was canceled' node at all. The cancel button should just collapse the node again, and when the user expands the node again, we should start the search as if the node had never been touched before.
|
2009-04-07 08:31:22
| 1,239,110,000
|
resolved fixed
|
cd58a9b
| 1,240,780,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/callhierarchy/MethodWrapper.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyContentProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/DeferredMethodWrapper.java
|
JDT
|
808
| 270,462
|
Bug 270462 [toString] toString wizard generates wrong code
|
I20090325-1135 + plug-in export. Generating toString using MessageFormat produces wrong result: public String toString() { return MessageFormat.format("a [i={1}, j={2}, k={3}]", new Object[] { Integer.valueOf(i), Integer.valueOf(j), Integer.valueOf(k) }); } Pattern starts with 0. Please also verify all other generated code.
|
2009-03-30 10:51:23
| 1,238,420,000
|
verified fixed
|
895934b
| 1,240,760,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/source/GenerateToStringTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/StringFormatGenerator.java
|
JDT
|
809
| 267,710
|
Bug 267710 [toString] finish toString() builder wizard
| null |
2009-03-09 15:23:00
| 1,236,630,000
|
resolved fixed
|
d8b937a
| 1,240,760,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/source/GenerateToStringTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/CodeGenerationMessages.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/ApacheBuilderSpringCreatorGenerator.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/CustomBuilderGenerator.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/GenerateToStringOperation.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/ToStringGenerationContext.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/ToStringGenerationSettings.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaUIMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/GenerateToStringDialog.java
|
JDT
|
810
| 246,003
|
Bug 246003 [clean up] Save action error dialog should link to project-specific preferences
| null |
2008-09-02 15:07:59
| 1,220,380,000
|
resolved fixed
|
0807be6
| 1,240,580,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/CleanUpPreferenceUtil.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitEditor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorMessages.java
|
JDT
|
811
| 264,421
|
Bug 264421 [quick assist] convert to enhanced for loop applied incorrectly
|
Build ID: M20080911-1700 Steps To Reproduce: Perhaps this isn't the prettiest code in the world, but it was encountered in real code. I can happily point to a public svn repo to prove it :-). Anyway, this is the original code public class ForLoopTest { public static void main(String[] args) { String[] src = new String[] { "1", "2", "3", "4" }; for (int i = 0; i < src.length; i++) { String path = src[i]; String output = path; if (output.length() == 1) { output = output + "-XXX"; } System.err.println("path="+ path + ",output="+output); } } } After applying the logic to convert the for loop, this is the result: public class ForLoopTest { public static void main(String[] args) { String[] src = new String[] { "1", "2", "3", "4" }; for (String path : src) { if (path.length() == 1) { path = path + "-XXX"; } System.err.println("path="+ path + ",output="+path); } } } Running the two versions of the program produce different output :-( Output before: path=1,output=1-XXX path=2,output=2-XXX path=3,output=3-XXX path=4,output=4-XXX Output after: path=1-XXX,output=1-XXX path=2-XXX,output=2-XXX path=3-XXX,output=3-XXX path=4-XXX,output=4-XXX More information:
|
2009-02-10 16:23:02
| 1,234,300,000
|
verified fixed
|
b2ef680
| 1,240,570,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/ConvertForLoopOperation.java
|
JDT
|
812
| 269,595
|
Bug 269595 [clean up] Clean-Up of For-Each plus use final produces extra 'final' modifier
|
The Clean-Up option 'Convert for loops to enhanced for loops' produce an extra 'final' modifier if the loop-variable was defined as final, resulting in two final modifiers on the same variable after clean-up. Example: Before Clean-Up: int[] array = new int[] { 1, 2, 3 }; for( int i = 0; i < array.length; i++ ) { final int value = array[i]; System.out.println( value ); } After Clean-Up: final int[] array = new int[] { 1, 2, 3 }; for( final final int value : array ) { System.out.println( value ); }
|
2009-03-21 11:42:08
| 1,237,650,000
|
verified fixed
|
5f45db6
| 1,240,570,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/ConvertForLoopOperation.java
|
JDT
|
813
| 273,440
|
Bug 273440 [implementation] NPE from Java editor
|
eclipse.buildId=I20090421-0930 java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20070201 (JIT enabled) J9VM - 20070131_11312_lHdSMR JIT - 20070109_1805ifx1_r8 GC - 200701_09 BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 Noticed these in my log. Not sure exactly what triggers it. org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:3881) at org.eclipse.swt.SWT.error(SWT.java:3796) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2401) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2365) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2217) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1287) at org.eclipse.equinox.launcher.Main.main(Main.java:1263) Caused by: java.lang.NullPointerException at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.selectionChanged(JavaEditor.java:2214) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$4.run(CompilationUnitEditor.java:1613) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 23 more
|
2009-04-23 10:31:36
| 1,240,500,000
|
resolved fixed
|
c9b164b
| 1,240,550,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java
|
JDT
|
814
| 260,865
|
Bug 260865 [compare] Clicking on the structure view breaks the compare editor viewers
|
Build id: N20090110-2000 Steps: 1) Create a java project and two classes inside (A.java and B.java). They can be very simple, e.g. public class A { // class A } 2) Compare them using Compare With > Each Other 3) In the compare editor, change something in A.java, e.g. // comment public class A { // class A } 4) Double click on a node in the structure view 5) Notice that the content of the viewer with A.java changed to // comment public class A { // 6) Save, still the content is wrong 7) Open A.java in the java editor, it looks ok
|
2009-01-13 10:59:38
| 1,231,860,000
|
resolved fixed
|
89cd507
| 1,240,500,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/compare/JavaStructureDiffViewer.java
|
JDT
|
815
| 272,465
|
Bug 272465 [jar exporter] DBCS3.5: Runnable JAR file can not find class names wiith non-ascii characters
| null |
2009-04-16 05:25:00
| 1,239,870,000
|
closed fixed
|
f15441b
| 1,240,490,000
|
org.eclipse.jdt.ui/jar in jar loader/org/eclipse/jdt/internal/jarinjarloader/RsrcURLConnection.java
|
JDT
|
816
| 272,366
|
Bug 272366 [ltk] LTK RefactoringWizardOpenOperation opens window with no window title text
|
If your wizard does not have any user input pages, but performs changes that have a preview, the preview window is opened automatically. However, this preview window does not contain the text that was set using RefactoringWizard#setWindowTitle(). If a user page was specified, it does contain work.
|
2009-04-15 15:01:16
| 1,239,820,000
|
resolved fixed
|
e9e2837
| 1,240,420,000
|
org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/RefactoringWizardDialog2.java
|
JDT
|
817
| 266,962
|
Bug 266962 JUnit to consume hamcrest.core from orbit.
| null |
2009-03-03 21:22:56
| 1,236,130,000
|
resolved fixed
|
ea8ff25
| 1,240,400,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitPreferencesConstants.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/BuildPathSupport.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/JUnitContainerInitializer.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/JUnitHomeInitializer.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/P2Utils.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/buildpath/BuildPathSupport.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/buildpath/JUnitContainerInitializer.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/buildpath/JUnitHomeInitializer.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/buildpath/P2Utils.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/JUnitPreferencesConstants.java
|
JDT
|
818
| 272,836
|
Bug 272836 [implementation][content assist] Broken extension point XSD and UI: proposalSorter is missing activate attribute
|
Build ID: M20080911-1700 Steps To Reproduce: 1. Add javaCompletionProposalSorters extension point 2. Add proposalSorter 3. Implement your proposal sorter 4. Test sorter: Open preferences and choose your sorter (Java->Editor->Content Assist->Sort proposals) 5. Even though it is chosen, your sorter will not execute and you can see NPE in log: org.eclipse.jdt.internal.ui.text.java.ProposalSorterHandle.sortProposals(ProposalSorterHandle.java:191) More information: The reason why it doesn't work is that ProposalSorterHandle instance has "activate" field set to false. To fix this, you must manually edit your plugin.xml and add activate="true" attribute to proposalSorter element. XSD should be enhanced to contain 'activate' attribute and UI should be enhanced to offer activate combo with true/false as other extensions do (e.g. javaCompletionProposalComputer).
|
2009-04-19 16:46:28
| 1,240,170,000
|
resolved fixed
|
eccb581
| 1,240,330,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ProposalSorterHandle.java
|
JDT
|
819
| 102,281
|
Bug 102281 [call hierarchy] shouldn't be stopped by anonymous inner classes
|
Here's a common scenario for me: I have a method deep in the innards of Eclipse, and I'm curious about the paths through which it might be called. I open call hierarchy on it, and search through the tree at leisure. At some point, I get stopped, because I come across a method like TestRunnerViewPart.showFailure: private void showFailure(final TestRunInfo failure) { postSyncRunnable(new Runnable() { public void run() { if (!isDisposed()) fFailureTrace.showFailure(failure); } }); } the caller of fFailureTrace.showFailure is Runnable.run. However, it's useless to expand that call hierarchy node, because it will show me every possible invocation of Runnable.run in the whole system (there are 88, of which only one is actually relevant). What I'm really wanting to do is to continue my search up through TestRunnerViewPart.showFailure. To do so, I must open up a new call hiearchy search, which consigns my old, carefully built-up search tree to the History List. One solution would be to actually employ some context-sensitivity in the call hierarchy analysis. This is probably not a good idea in terms of cost/benefit analysis. A better solution, for my money, would be to have a new option on the context menu on a node in the Call Hierarchy: "Expand with constructors". This would let me expand thusly (edited for clarity, I hope) showFailure(TestRunInfo) - ...FailureTrace run() - ...TestRunnerViewPart.showFailure(...).new Runnable() {...} [constructors] Runnable() {...} showFailure(TestRunInfo) - ...TestRunnerViewPart testReran(...) - ...TestRunnerViewPart handleTestSelected(TestRunInfo) - ...TestRunnerViewPart (2 matches)
|
2005-06-30 05:16:56
| 1,120,120,000
|
verified fixed
|
ca2d947
| 1,240,310,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/callhierarchy/CallerMethodWrapper.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/callhierarchy/MethodWrapper.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/callhierarchy/RealCallers.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/IJavaHelpContextIds.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyContentProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyLabelProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/ExpandWithConstructorsAction.java
|
JDT
|
820
| 272,583
|
Bug 272583 [Dialogs] OK button is in the wrong position if dialog explicitly calls layout() before initializeBounds()
|
Select a project in the Package Explorer and hit delete. When the Delete Resources dialog pops up for confirmation, the 3 buttons are displayed in the following order: Preview, OK, Cancel. On the Mac this should be: Preview, Cancel, OK. Appears to be a problem on both Cocoa and Carbon on Eclipse 3.5 Version: 3.5.0 Build id: I20090414-0800
|
2009-04-16 17:10:34
| 1,239,920,000
|
verified fixed
|
68f9be8
| 1,240,260,000
|
org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/RefactoringWizardDialog2.java
|
JDT
|
821
| 272,742
|
Bug 272742 ImagesOnFileSystemRegistry is not thread safe
| null |
2009-04-17 14:23:52
| 1,239,990,000
|
resolved fixed
|
c663b21
| 1,240,220,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/ImagesOnFileSystemRegistry.java
|
JDT
|
822
| 272,737
|
Bug 272737 [working sets] 'Other Projects' keeps label when starting with another locale
|
I20090416-1053 The 'Other Projects' working set keeps the label in the original language when I start the same workspace with another locale.
|
2009-04-17 14:05:15
| 1,239,990,000
|
resolved fixed
|
742df83
| 1,239,990,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/workingsets/WorkingSetModel.java
|
JDT
|
823
| 165,434
|
Bug 165434 [Structure Viewers] Reconcile structure upon document changes
|
I20061121-1845 I often get confused when using the compare views by the stale information in the structure comparison which only updates on safe. I'd like to have the option that the structure compare updates when the content changes, e.g. when I move a change from right to left or the other way around.
|
2006-11-22 05:36:23
| 1,164,190,000
|
verified fixed
|
f72a1bb
| 1,239,980,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/compare/JavaStructureDiffViewer.java
|
JDT
|
824
| 271,375
|
Bug 271375 [nls tooling] Externalize Strings wizard always defaults to the "legacy" mechanism
|
The Externalize Strings wizard offers the option "Use Eclipse's string externalization mechanism" which is a superior choice. However, it does not default to that option when available nor does it remember the user's selection of that option for future invocations of the wizard. It should be encouraging use of the newer mechanism, especially since converting form the old to the new is a tedious manual process.
|
2009-04-06 16:13:17
| 1,239,050,000
|
resolved fixed
|
060cc11
| 1,239,960,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/nls/NLSRefactoring.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/ExternalizeWizardPage.java
|
JDT
|
825
| 272,567
|
Bug 272567 [javadoc][hovering] Rendered Javadoc should strip out * at beginning of line
|
I20090415-1348 Rendered Javadoc should strip out * at beginning of line. This works mostly fine, but there are people who put the * at the very beginning of the line, i.e. without any space before, e.g. com.ibm.icu.text.Collator. The result in Javadoc hover and view is a text with * measles.
|
2009-04-16 15:58:21
| 1,239,910,000
|
resolved fixed
|
7cc73ad
| 1,239,910,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavadocContentAccess2.java
|
JDT
|
826
| 272,354
|
Bug 272354 [JUnit] NPE while initializing Java tooling
|
Got that while launching an Eclipse workspace in debug mode. Version: 3.5.0 Build id: I20090407-1430 java.lang.NullPointerException at org.eclipse.jdt.internal.junit.buildpath.P2Utils.findBundle(P2Utils.java:166) at org.eclipse.jdt.internal.junit.buildpath.P2Utils.findBundle(P2Utils.java:142) at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport.getJUnitLibraryEntry(BuildPathSupport.java:81) at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport.getJUnit3LibraryEntry(BuildPathSupport.java:67) at org.eclipse.jdt.internal.junit.buildpath.JUnitContainerInitializer.getNewContainer(JUnitContainerInitializer.java:100) at org.eclipse.jdt.internal.junit.buildpath.JUnitContainerInitializer.initialize(JUnitContainerInitializer.java:90) at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2609) at org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2515) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2555) at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1774) at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3407) at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:35) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
|
2009-04-15 14:21:02
| 1,239,820,000
|
resolved fixed
|
fce2509
| 1,239,870,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/P2Utils.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/buildpath/P2Utils.java
|
JDT
|
827
| 271,757
|
Bug 271757 TextMergeViewer.createSourceViewer(...) should return SourceViewer
| null |
2009-04-09 08:55:59
| 1,239,280,000
|
resolved fixed
|
1d99309
| 1,239,780,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/compare/JavaMergeViewer.java
|
JDT
|
828
| 36,595
|
Bug 36595 [templates] 'systrace' template produces incorrect string in anonymous classes
|
public class Test { public static void main(String[] args) { Object test = new Object() { public String toString() { // systrace: Expected "Object.toString()", got: System.out.println("Bug.main()"); return null; } }; } }
|
2003-04-16 15:17:37
| 1,050,520,000
|
resolved fixed
|
3923d4b
| 1,239,040,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/CompilationUnitContextType.java
|
JDT
|
829
| 19,027
|
Bug 19027 [javadoc wizard] Ok after validating Javadoc location pref page opens browser [javadoc]
| null |
2002-06-04 09:11:12
| 1,023,200,000
|
verified fixed
|
3d9bc28
| 1,238,660,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavadocConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java
|
JDT
|
830
| 268,950
|
Bug 268950 [Commands] New APIs in IWorkbenchCommandConstants are missing '_' separators
|
3.5 M6. The new constants in IWorkbenchCommandConstants are missing '_' separators which make them hard to read and which make them differ from the action constant. Examples: - action is called CLOSE_ALL but constant is FILE_CLOSEALL instead of FILE_CLOSE_ALL - action is called CLOSE_PERSPECTIVE but constant is WINDOW_CLOSEPERSPECTIVE instead of WINDOW_CLOSE_PERSPECTIVE I'm sorry I did not notice before the API freeze. I suggest to ask the PMC to change that for final 3.5.
|
2009-03-17 07:33:17
| 1,237,290,000
|
verified fixed
|
f5a4040
| 1,238,600,000
|
org.eclipse.jdt.astview/src/org/eclipse/jdt/astview/views/ASTView.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/browsing/JavaBrowsingPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.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/JavaOutlinePage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/OccurrencesSearchResultPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/AbstractInformationControl.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/typehierarchy/TypeHierarchyViewPart.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/BuildActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/GenerateActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenViewActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ProjectActionGroup.java
|
JDT
|
831
| 125,296
|
Bug 125296 [JUnit] Eclipse shows only one failure or error from the JUnit test result
| null |
2006-01-26 04:14:04
| 1,138,270,000
|
resolved fixed
|
2a877dd
| 1,238,430,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestElement.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/model/TestElement.java
|
JDT
|
832
| 267,918
|
Bug 267918 [toString] dialog should center widgets
|
I20090310-0100. The dialog should center its widgets.
|
2009-03-10 13:14:13
| 1,236,710,000
|
verified fixed
|
345c82d
| 1,238,420,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaUIMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/GenerateToStringDialog.java
|
JDT
|
833
| 267,904
|
Bug 267904 [toString] toString template variable proposals info should start with uppercase
|
I20090310-0100. toString template variable proposals info should start with uppercase.
|
2009-03-10 12:35:22
| 1,236,700,000
|
verified fixed
|
3373a62
| 1,238,410,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/CodeGenerationMessages.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/tostringgeneration/ToStringTemplateParser.java
|
JDT
|
834
| 56,576
|
Bug 56576 [navigation] Quick outline: first member not selected when switching to inherited mode
|
3.0M8: Quick outline: first member not selected when switching to inherited mode - open type org.eclipse.swt.widgets.Text - press Ctrl+O - type "getM" (-> list becomes empty) - press Ctrl+O again -> expected: "getMenu()" is selected in the background; Enter key should go to it -> was: no item selected; Enter key does nothing
|
2004-03-29 10:09:13
| 1,080,570,000
|
resolved fixed
|
558da3f
| 1,238,410,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaOutlineInformationControl.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/HierarchyInformationControl.java
|
JDT
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.