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 |
|---|---|---|---|---|---|---|---|---|---|---|
435
| 314,076
|
Bug 314076 [rename] Incorrect message while 'Rename' when CU not on Build path
|
Build I20100520-1744 - New workspace - Open a Java file placed anywhere on the file system (but is not on build path) Use following snippet package q; public class B { int a; void foo() { System.out.println(); System.out.println(); } } - Select field 'a' OR method 'foo' - From the Menu bar 'Refactor' -> Rename => Dialog saying 'Operation unavailabe on the current selection. Select a field Java project, field, method.... etc' comes up. However dialog saying 'the CU is not on the build path' should come up.
|
2010-05-24 05:09:18
| 1,274,690,000
|
verified fixed
|
b04c07e
| 1,283,940,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/actions/RenameJavaElementAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/RenameAction.java
|
JDT
|
436
| 314,077
|
Bug 314077 [move member type] Incorrect message while 'Move Type to New File' when CU not on Build path
|
Build I20100520-1744 - New workspace - Open a Java file placed anywhere on the file system (but is not on build path) Use following snippet package q; public class B { void foo() { System.out.println(); } } class A{ } - Select class 'A' - From the Menu bar 'Refactor' -> Move Type to New File => Dialog saying ' To activate this refactoring, please select the name of a member type or a secondary type' comes up. However dialog saying 'the CU is not on the build path' should come up.
|
2010-05-24 05:16:45
| 1,274,690,000
|
verified fixed
|
3760f57
| 1,283,930,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ConvertNestedToTopAction.java
|
JDT
|
437
| 314,075
|
Bug 314075 [encapsulate field] Incorrect message/Exception while 'Encapsulate field' when CU not on Build path
|
Build I20100520-1744 - New workspace - Open a Java file placed anywhere on the file system (but is not on build path) Use following snippet package q; public class B { int a; void foo() { System.out.println(); System.out.println(); } } - Select field 'a' - From the Menu bar 'Refactor' -> Encapsulate field => Dialog saying ' The operation is not applicable to the current selection. Select a field of a class or a enum' comes up. However dialog saying 'the CU is not on the build path' should come up.
|
2010-05-24 05:02:29
| 1,274,690,000
|
verified fixed
|
71c3148
| 1,283,780,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/SelfEncapsulateFieldAction.java
|
JDT
|
438
| 314,069
|
Bug 314069 [introduce parameter] NPE while 'Introduce Parameter Object' when CU not on Build path
|
I20100520-1744 - New workspace - Open a Java file placed anywhere on the file system (but is not on build path) (OR can open a file from CVS repository ) Use the following snippet package q; public class B { void foo() { System.out.println(); } } - Select 'foo' - From the Menu bar 'Refactor' -> Introduce Parameter Object => NPE in error log java.lang.NullPointerException at org.eclipse.jdt.internal.ui.actions.IntroduceParameterObjectAction.getSingleSelectedMethod(IntroduceParameterObjectAction.java:165) at org.eclipse.jdt.internal.ui.actions.IntroduceParameterObjectAction.run(IntroduceParameterObjectAction.java:113) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:278) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:230) at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:234) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
|
2010-05-24 04:29:02
| 1,274,690,000
|
verified fixed
|
03c14c3
| 1,283,780,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/IntroduceParameterObjectAction.java
|
JDT
|
439
| 314,063
|
Bug 314063 [extract interface] NPE while 'Extract Interface', 'Use SuperType', 'Extract class' when CU not on Build path
|
Build I20100520-1744 - New workspace - CVS Repositories view -> Navigate to a Java file stored in a CVS repository -> Right click, select 'Open' from the context menu (I used org.eclipse.jdt.ui.tests.AutomatedSuite) OR Open a Java file placed anywhere on the file system (but is not on build path) - Select a line of code - From the Menu bar 'Refactor' -> Extract interface => following NPE in error log java.lang.NullPointerException at org.eclipse.jdt.internal.ui.refactoring.actions.RefactoringActions.convertToEnclosingOrPrimaryType(RefactoringActions.java:53) at org.eclipse.jdt.internal.ui.refactoring.actions.RefactoringActions.getEnclosingOrPrimaryType(RefactoringActions.java:46) at org.eclipse.jdt.ui.actions.ExtractInterfaceAction.run(ExtractInterfaceAction.java:138) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:278) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:230) at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:234) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
|
2010-05-24 04:12:44
| 1,274,690,000
|
verified fixed
|
1521bfe
| 1,283,770,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ExtractClassAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ExtractInterfaceAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/UseSupertypeAction.java
|
JDT
|
440
| 139,197
|
Bug 139197 [refactoring] 'Introduce Indirection' do nothing when right-clicking on method name in .class file
|
I20060428-0010 1. Open an external .java fil using File > Open File... 2. Refactor > Introduce indirection... Observe: You get no dialog (as you can expect because of the ellipsis)
|
2006-04-28 11:17:08
| 1,146,240,000
|
verified fixed
|
84c9229
| 1,283,770,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/IntroduceIndirectionAction.java
|
JDT
|
441
| 305,255
|
Bug 305255 [preferences] Accept jsr14 as a build target
| null |
2010-03-09 17:31:55
| 1,268,170,000
|
resolved fixed
|
e5acb8c
| 1,283,600,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ComplianceConfigurationBlock.java
|
JDT
|
442
| 324,429
|
Bug 324429 [navigation] Quick Hierarchy fails when selected element is type parameter
|
HEAD Quick Hierarchy fails when the selected element is a type parameter: !ENTRY org.eclipse.jdt.ui 4 10001 2010-09-03 16:26:04.762 !MESSAGE Element unsupported by the hierarchy: class org.eclipse.jdt.internal.core.TypeParameter Test case: package api; public class Bongo<Element> { Element fElement; public Element getElement() { return fElement; } public void setElement(Element element) { fElement = element; } public static void main(String[] args) { } }
|
2010-09-03 10:34:34
| 1,283,520,000
|
resolved fixed
|
c6c3bc1
| 1,283,530,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaElementProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/HierarchyInformationControl.java
|
JDT
|
443
| 324,391
|
Bug 324391 [content assist] Still too many semicolons after constructor completion
| null |
2010-09-03 06:49:01
| 1,283,510,000
|
verified fixed
|
364e3a3
| 1,283,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
|
444
| 319,532
|
Bug 319532 [preference][typing] Allow to disable smart auto-indent on return
| null |
2010-07-12 07:01:06
| 1,278,930,000
|
verified fixed
|
19a57eb
| 1,283,510,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/SmartTypingConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaAutoIndentStrategy.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/PreferenceConstants.java
|
JDT
|
445
| 298,426
|
Bug 298426 [content assist] constructor completion with package prefix fails
|
Build Identifier: M20090917-0800 I have some code that uses JAXB. There are several places where I instantiate an ObjectFactory to create some related objects. As I'm using more than one ObjectFactory in a class, I specify the FQCN for the ObjectFactory, which is a little annoying. So, I figure I should be able to use completion to save some keystrokes. I enter "new" followed by the beginning of the package path, and that nicely lets me complete the rest of the package path. I then enter "." (period) and that brings up the completion menu at that point. The menu has three items, consisting of "ObjectFactory()", the class name the ObjectFactory would be creating, and the constructor for the class name. In any case, "ObjectFactory" is the first one in the list, and it's highlighted, so I just press Enter, as that's the one I want. What I get with that is ... nothing. When I pressed Enter on the menu, it didn't insert "ObjectFactory()". It didn't insert anything. I then manually enter "ObjectFactory()" and then ".". It then brings up the completion menu for the methods of that ObjectFactory. I select the one I want and it inserts it. I've tried this numerous times, and it never inserts "ObjectFactory()". I tried a similar scenario with a class that I wrote (in a related package to the class I'm referencing it from), so I enter "new", followed by the initial piece of the package path, followed by Ctrl-space. I select the package I want from the menu, and it inserts the rest of the package path. I then enter ".", and that brings up the completion menu listing the constructors for the classes in that package. I select the one I want and it inserts it, no problem. I don't know what could be different about the ObjectFactory class that could cause this symptom. It's a class name that would occur multiple times in the classpath, but obviously only once in each package. I don't have the source for it, but I do have the source for the other completion test case I tried. Reproducible: Always
|
2009-12-22 13:38:54
| 1,261,510,000
|
verified fixed
|
346ddb8
| 1,283,440,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaMethodCompletionProposal.java
|
JDT
|
446
| 287,374
|
Bug 287374 [extract method] Allows extracting lhs of full qualified expression
| null |
2009-08-23 06:57:12
| 1,251,030,000
|
resolved fixed
|
aad3069
| 1,283,360,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/invalidSelection/A_test124.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/ExtractMethodAnalyzer.java
|
JDT
|
447
| 322,538
|
Bug 322538 [call hierarchy] "Expand with Constructors" should auto-expand single constructor
|
The "Expand with Constructors" action in the Call Hierarchy should auto-expand the "[constructor] ..." node if there is only one. There's a 99% chance that the user wants to expand this constructor after choosing the action. I would also try how it feels if we do the same when a node is automatically expanded with constructors due to the view settings. I think it could be convenient too, but it could also become confusing.
|
2010-08-12 10:37:12
| 1,281,620,000
|
verified fixed
|
8252280
| 1,283,230,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/ExpandWithConstructorsAction.java
|
JDT
|
448
| 261,498
|
Bug 261498 [spell checking] Locales without country code don't work.
| null |
2009-01-19 08:13:41
| 1,232,370,000
|
verified fixed
|
41e3642
| 1,283,180,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/spelling/SpellCheckEngine.java
|
JDT
|
449
| 312,014
|
Bug 312014 content of tree view (projects and folders) to export to a jar is not read by some screen readers
|
Build Identifier: N20100505-2000 I tested it with JAWS and NVDA and they gave me the same result. The workaround is to use the JAWS cursor to do the mapping between the project/folder names and their selected state, but it's a boring task. There are tree views in eclipse that are well red by JAWS, such as window > customize perstective... Reproducible: Always Steps to Reproduce: 1. Create one or two projects to exercise this test. 2. go to file > export > java > jar file and press next. 3. You are now focused on the tree view which displays projects and folders to select. 4. Press up and down arrows. Expected results: screen reader should say something like: "<project name|folder name> <state of tree view item (closed|opened)> <state of checkbox>" Actual results: screen reader says: "select projects and folders to export <state of tree view item (closed|opened)> <state of checkbox>"
|
2010-05-07 04:04:16
| 1,273,220,000
|
resolved fixed
|
2eeef51
| 1,282,930,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/util/SWTUtil.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/RefactoringStatusViewer.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/util/SWTUtil.java
|
JDT
|
450
| 322,331
|
Bug 322331 [introduce parameter] IntroduceParameterRefactoring wrong assurance ICompilationUnit => IMethod
|
Build Identifier: M20090917-0800 I'm trying to create a refactoring using RefactoringDescriptor class. I'm generate the necessary arguments of the argument Map<String, String> to get an instance of the class "RefactoringDescriptor". Then a create refactoring object, that already parametrezed. Here I land in the method "private RefactoringStatus initialize(JavaRefactoringArguments arguments) of the class org.eclipse.jdt.internal.corext.refactoring.code.IntroduceParameterRefactoring. In this method, at line 564 is the wrong test, see Source: if (element == null | |! element.exists () | | element.getElementType ()! = IJavaElement.COMPILATION_UNIT) JavaRefactoringDescriptorUtil.createInputFatalStatus return (element getName (), IJavaRefactorings.INTRODUCE_PARAMETER); else fSourceCU = ((IMethods) element). getCompilationUnit (); In the "if" question is assured that variable is to be "element" ICompilationUnit type. Is expected, but IMethods! Reproducible: Always Steps to Reproduce: 1.Try to create an Refactoring using LTK API. Something like that! 2. public Refactoring createRefactoring(String project, String description, String comment) throws CoreException { final JavaRefactoringDescriptor descriptor = (JavaRefactoringDescriptor) RefactoringCore .getRefactoringContribution( IJavaRefactorings.INTRODUCE_PARAMETER) .createDescriptor(IJavaRefactorings.INTRODUCE_PARAMETER, project, description, comment, getAttributes(), getFlags()); Assert.isNotNull(descriptor); return descriptor.createRefactoring(descriptor.validateDescriptor()); } 3.
|
2010-08-11 06:17:54
| 1,281,520,000
|
verified fixed
|
fc088b4
| 1,282,730,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceParameterRefactoring.java
|
JDT
|
451
| 323,134
|
Bug 323134 [JUnit] JUnit view loses several action states on restart
| null |
2010-08-19 08:52:19
| 1,282,220,000
|
verified fixed
|
7748890
| 1,282,570,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitCorePlugin.java
|
JDT
|
452
| 317,755
|
Bug 317755 [JUnit] JUnit -> Activate on Error/Failure Only not working
|
Build Identifier: 20100617-1415 in Helios, JUnit's "Activate on Error/Failure Only" no longer works. Instead, the JUnit tab is always activated. This happens whether in Fast View or not. This happens with JUnit 3 and 4. Expected: when "Activate on Error/Failure Only" is checked and the tests pass, the JUnit dialog should not get focused. If in Fast View, the panel should not be displayed. Reproducible: Always Steps to Reproduce: 1. in the JUnit UI, in the upper right corner click the 'down arrow' icon, and check "Activate on Error/Failure Only" 2. Run a JUnit test where every test passes 3. see the JUnit UI activates (a.k.a. gets focus, displays)
|
2010-06-23 18:59:55
| 1,277,330,000
|
verified fixed
|
62aedcd
| 1,282,210,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/JUnitPlugin.java
|
JDT
|
453
| 312,189
|
Bug 312189 [quick assist] BadLocationException when applying proposal while preview is computed
| null |
2010-05-09 15:58:16
| 1,273,440,000
|
verified fixed
|
469e07d
| 1,282,060,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/ChangeCorrectionProposal.java
|
JDT
|
454
| 322,812
|
Bug 322812 [JUnit] JUnit library container can't resolve binary-imported org.hamcrest.core
| null |
2010-08-16 12:00:55
| 1,281,970,000
|
resolved fixed
|
ab3ba75
| 1,281,970,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/BuildPathSupport.java
|
JDT
|
455
| 202,566
|
Bug 202566 [nls tooling] Exernalize Strings Wizard always imports accessor class
|
I was externalizing strings in some new files yesterday and noticed that I was just internalizing everything because these were strings that didn't need to be externalized (ie., HTML tags). When I ran through the wizard, it gave me an unused import on my access class. The wizard should probably be more intelligent in when it decides to add the import.
|
2007-09-06 23:33:17
| 1,189,140,000
|
resolved fixed
|
d2b3b49
| 1,281,960,000
|
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/nls/NlsRefactoringCreateChangeTest.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/nls/NLSSourceModifier.java
|
JDT
|
456
| 322,253
|
Bug 322253 [Widgets] Context menu does not go away after setVisible(false)
|
3.5, 3.6 and latest 3.7 build. Happens on MacOSX 10.5.6 and 10.5.8 but not 10.6. Our org.eclipse.jdt.ui.tests.leaks.JavaLeakTest.testJavaEditorContextMenu() test ('org.eclipse.jdt.ui.tests' bundle) waits forever on Mac Cocoa because the menu doesn't get closed using setVisible(false). The result is that the test runs 2 hours before it gets killed. This works on all other platforms and also on the latest Mac version, hence filing against SWT. The relevant code is in JavaLeakTest.openContextMenu(Menu). Should be easy to extract a snippet from that.
|
2010-08-10 12:37:42
| 1,281,460,000
|
resolved fixed
|
f6b653a
| 1,281,900,000
|
org.eclipse.jdt.ui.tests/leaks/org/eclipse/jdt/ui/tests/leaks/JavaLeakTest.java
|
JDT
|
457
| 321,818
|
Bug 321818 [preferences] 'Errors/Warnings' page: allow to filter a section for a value
|
I20100804-1800. The 'Errors/Warnings' page should allow to filter a category for a value, e.g. ~warn code style code style ~error
|
2010-08-05 03:00:45
| 1,280,990,000
|
verified fixed
|
915e0e4
| 1,281,600,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.java
|
JDT
|
458
| 302,831
|
Bug 302831 [quick assist] Assigning a parameter to an existing field allows incomplete linked mode
|
Build Identifier: I20100129-1300 Assume the following example: public class Foo { int existing; public Foo(int existingVal) { } void existingReference() { existing++; } } 1) on the constructor, move the cursor on the existingVal parameter. 2) Use quick fix to assign the parameter to the field existing observe: the editor is now in linked mode, but only with the field declaration and the assignment 3) change the name of the field observe: a compile error results expected: the linked mode should include the field's references as well Reproducible: Always
|
2010-02-14 17:21:42
| 1,266,190,000
|
verified fixed
|
b700499
| 1,281,450,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/AssignToVariableAssistProposal.java
|
JDT
|
459
| 314,407
|
Bug 314407 [inline] IndexOutOfBoundsException in inline method refactoring with compile error
|
What steps will reproduce the problem? 1. Edit the attached file (it has compile errors) 2. Selected getImage() in line 31 3. Select Inline Method Refactoring 4. Select Replace all invocations 5. Error occurs 6. After saving the file, the error still remains -- Error Details -- Date: Wed May 26 09:58:21 CEST 2010 Message: Internal Error Severity: Error Product: Eclipse SDK 3.6.0.v201005201744 (org.eclipse.sdk.ide) Plugin: org.eclipse.ltk.ui.refactoring Session Data: eclipse.buildId=I20100520-1744 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Framework arguments: --launcher.XXMaxPermSize=256m Command-line arguments: -os linux -ws gtk -arch x86 -debug /home/hafner/Documents/eclipse.debug -data /home/hafner/Workspaces/Faktor-Logik --launcher.XXMaxPermSize=256m Exception Stack Trace: java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:330) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.internalPerformFinish(RefactoringWizard.java:573) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.performFinish(UserInputWizardPage.java:153) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.performFinish(RefactoringWizard.java:646) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.okPressed(RefactoringWizardDialog2.java:454) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1234) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3159) 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:180) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:192) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:115) at org.eclipse.jdt.internal.ui.refactoring.actions.RefactoringStarter.activate(RefactoringStarter.java:38) at org.eclipse.jdt.internal.corext.refactoring.RefactoringExecutionStarter.startInlineMethodRefactoring(RefactoringExecutionStarter.java:330) at org.eclipse.jdt.internal.ui.refactoring.actions.InlineMethodAction.tryInlineMethod(InlineMethodAction.java:143) at org.eclipse.jdt.ui.actions.InlineAction.run(InlineAction.java:122) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:278) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.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:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1525) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1233) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1243) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1270) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:729) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:2833) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:707) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1719) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4783) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4358) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8163) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1239) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2224) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3157) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.eclipse.jdt.core.dom.ASTNode$NodeList.get(ASTNode.java:1211) at org.eclipse.jdt.internal.corext.refactoring.code.SourceProvider.getParameterData(SourceProvider.java:301) at org.eclipse.jdt.internal.corext.refactoring.code.CallInliner.computeRealArguments(CallInliner.java:507) at org.eclipse.jdt.internal.corext.refactoring.code.CallInliner.initialize(CallInliner.java:290) at org.eclipse.jdt.internal.corext.refactoring.code.InlineMethodRefactoring.checkFinalConditions(InlineMethodRefactoring.java:306) 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.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:209) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) 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.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.eclipse.jdt.core.dom.ASTNode$NodeList.get(ASTNode.java:1211) at org.eclipse.jdt.internal.corext.refactoring.code.SourceProvider.getParameterData(SourceProvider.java:301) at org.eclipse.jdt.internal.corext.refactoring.code.CallInliner.computeRealArguments(CallInliner.java:507) at org.eclipse.jdt.internal.corext.refactoring.code.CallInliner.initialize(CallInliner.java:290) at org.eclipse.jdt.internal.corext.refactoring.code.InlineMethodRefactoring.checkFinalConditions(InlineMethodRefactoring.java:306) 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.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:209) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
|
2010-05-26 04:10:58
| 1,274,860,000
|
verified fixed
|
e30cc05
| 1,281,270,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/bugs_in/Test_314407_1.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/bugs_in/Test_314407_2.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/bugs_out/Test_314407_1.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/bugs_out/Test_314407_2.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/invalid/Test_314407.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/InlineMethodTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/CallInliner.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/TargetProvider.java
|
JDT
|
460
| 321,550
|
Bug 321550 [navigation] Open Hyperlink > Open Implementation does not work for external files
|
Build id : I20100802-1800 (same behavior in 3.6) Open Implementation does nothing on files not on build path Steps: - Create a java file with the following snippet on the file system and open it in eclipse class A { void foo() { String s=""; System.out.println(""); System.out.append('a'); s.compareTo(""); s.equals(""); s.substring(1).equals(""); } } - Ctrl+click or use the command on 'println' or 'append' > Select 'Open Implementation' => nothing happens. 'Open Declaration' works correctly.
|
2010-08-03 02:00:40
| 1,280,820,000
|
verified fixed
|
db1272c
| 1,280,920,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementHyperlinkDetector.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementHyperlinkImplementationDetector.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementImplementationHyperlink.java
|
JDT
|
461
| 321,574
|
Bug 321574 [call hierarchy] Remove Hierarchy scope for Call Hierarchy
|
I2010070802-1800. Search In dialog: "Note:" should be bold like in the preference dialog.
|
2010-08-03 06:43:04
| 1,280,830,000
|
verified fixed
|
5dd410e
| 1,280,920,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/SearchInDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/SearchScopeActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/SearchScopeHierarchyAction.java
|
JDT
|
462
| 321,558
|
Bug 321558 [preferences] problem filtering should allow to combine name with value search
|
I20100802-1800. I tried to search a certain set of options (by name) along with a given value but failed. We should support name~value patterns, e.g. "param~warn"
|
2010-08-03 04:44:51
| 1,280,830,000
|
verified fixed
|
871e52c
| 1,280,910,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.java
|
JDT
|
463
| 320,983
|
Bug 320983 [hovering] Javadoc does not display properly on classes with a generic type that's also an HTML element name
|
Build Identifier: M20090917-0800 Using the following code: public abstract class Test<T> { public static void main(String[] args) { new Test<Button>() { void foo() { } }; new Test<Strike>() { void foo() { } }; } } When you hover over the name of either foo() method, the Javadoc rendering that shows is wrong: The first one displays an HTML button element containing everything after the class name, the second one strikes through that text. See attached screenshot. Reproducible: Always Steps to Reproduce: 1. Create an anonymous instance of a class with a generic type 2. Implement a method in that class 3. View the javadoc on that method
|
2010-07-27 04:41:54
| 1,280,220,000
|
resolved fixed
|
abc1f09
| 1,280,770,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementLabelComposer.java
|
JDT
|
464
| 155,828
|
Bug 155828 [JUnit] Update test suite wizard for JUnit 4: @RunWith(Suite.class)...
|
JUnit plugin is not working as described. Follow the "Writing and running JUnit tests" help section and after you create JUnit test case with the wizzard, the new Test Suit is not detecting the newly created Test Case as an available Test Case to be added to the suite. Before closing the bug down and bouncing it back (as ~I noticed you tend to do it here) just follow the steps and see it repeated.
|
2006-08-31 10:31:24
| 1,157,030,000
|
verified fixed
|
35db915
| 1,280,770,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/wizards/SuiteClassesContentProvider.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/wizards/UpdateTestSuite.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/wizards/WizardMessages.java org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/wizards/NewTestSuiteWizardPage.java
|
JDT
|
465
| 308,199
|
Bug 308199 JavaElementAdapterFactory loads Team UI
|
I20100406-0800. JavaElementAdapterFactory loads Team UI because it references IHistoryPageSource. We could use a lazy approach like for ISearchPageScoreComputer.
|
2010-04-06 09:31:26
| 1,270,560,000
|
resolved fixed
|
7d25658
| 1,280,760,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaElementAdapterFactory.java
|
JDT
|
466
| 321,385
|
Bug 321385 SearchLeakTestWrapper#testRemoveSearchQueries() fails on build machine
|
SearchLeakTestWrapper#testRemoveSearchQueries() fails on build machine when running AllZRHTests. No problem when run by itself. Reverting the last change in SearchView makes the test green again.
|
2010-07-30 13:09:48
| 1,280,510,000
|
resolved fixed
|
f62e075
| 1,280,730,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/search/SearchLeakTest.java
|
JDT
|
467
| 78,522
|
Bug 78522 [navigation] All Ctrl+Click link targets should also be available under one command/action
|
I200411100800 All Ctrl+Click link targets should also work with Open (F3)
|
2004-11-12 11:41:04
| 1,100,280,000
|
verified fixed
|
02a1a30
| 1,280,400,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/BasicJavaEditorActionContributor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesFileEditorActionContributor.java
|
JDT
|
468
| 305,103
|
Bug 305103 [refactoring] Comment deleted on 'Move type to new file' refactoring
|
For each code snippet below - Move X to new file (problem is independent creating an instance variable) - The comment gets deleted. Its neither in new file nor the old file. - There can be some empty lines between the comment and class X, the comment will still be deleted However if the comment is a javadoc (begins with /**) then its moved to new file. Marking as major as there is loss of data and the user may not realize it right away. Also I do not see any junits which test these (comments) cases. 1) package p; class A { /* * A very important comment. */ class X { } } 2) package p; class A { /* * A very important comment. */ class X { } } 3) package p; class A { // A very important comment. class X { } } 4) package p; class A { class X { } // A very important comment. } 5) package p; class A { class X { } /* A very important comment.*/ } 6) package p; class A { class X { } /** A very important comment.*/ } Things that work fine - Javadoc comment before Class X Empty lines between Class X and the comment when comment occurs after the class 1) package p; class A { /** * A very important comment. */ class X { } } 2) package p; class A { class X { } // A very important comment. } 3) package p; class A { class X { } /* A very important comment.*/ } 4) package p; class A { class X { } /** A very important comment.*/ }
|
2010-03-09 01:21:28
| 1,268,120,000
|
verified fixed
|
b026ae5
| 1,280,390,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test35/out/Inner.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test36/out/Inner.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_45/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_45/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_45/out/B.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_46/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_46/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_46/out/B.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_47/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_47/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_47/out/B.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_48/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_48/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_48/out/B.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_10/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_10/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_10/out/Secondary.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_11/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_11/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_11/out/Secondary.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_12/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_12/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_12/out/Secondary.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_13/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_13/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_13/out/Secondary.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_9/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_9/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_secondary_9/out/Secondary.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/MoveInnerToTopLevelTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInnerToTopRefactoring.java
|
JDT
|
469
| 319,689
|
Bug 319689 Invalid thread access in ProblemMarkerManager
|
I've just got this exception while shuting down my 4.0 SDK but my guess from the stacktrace is that this not really a problem solely in 4.0 --------8<-------- org.eclipse.swt.SWTException: Invalid thread access at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.widgets.Display.error(Display.java:1027) at org.eclipse.swt.widgets.Display.createDisplay(Display.java:794) at org.eclipse.swt.widgets.Display.create(Display.java:777) at org.eclipse.swt.graphics.Device.<init>(Device.java:130) at org.eclipse.swt.widgets.Display.<init>(Display.java:668) at org.eclipse.swt.widgets.Display.<init>(Display.java:659) at org.eclipse.swt.widgets.Display.getDefault(Display.java:1303) at org.eclipse.jdt.internal.ui.util.SWTUtil.getStandardDisplay(SWTUtil.java:63) at org.eclipse.jdt.internal.ui.viewsupport.ProblemMarkerManager.fireChanges(ProblemMarkerManager.java:201) at org.eclipse.jdt.internal.ui.viewsupport.ProblemMarkerManager.resourceChanged(ProblemMarkerManager.java:144) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:327) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1181) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:157) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) --------8<--------
|
2010-07-13 07:51:35
| 1,279,020,000
|
resolved fixed
|
b81ec58
| 1,280,320,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/util/SWTUtil.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/ImageDescriptorRegistry.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/ProblemMarkerManager.java
|
JDT
|
470
| 318,797
|
Bug 318797 [implementation] Deadlock in SharedASTProvider.getAST() (on breakpoint creation)
| null |
2010-07-03 16:03:05
| 1,278,190,000
|
verified fixed
|
b942db6
| 1,280,240,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ASTProvider.java
|
JDT
|
471
| 320,133
|
Bug 320133 [nls tooling] externalize strings escapes ISO 8859-1
|
Build Identifier: 20100218-1602 The externalize strings capability of eclipse escapes ISO 8859-1 characters, even if that is not necessary (since properties files are ISO 8859-1). E.g. "" becomes "\u00FC". This makes both the properties files less readable and might (in special cases) produce some different behavior depending on the encoding settings of your JVM Reproducible: Always Steps to Reproduce: 1. write code using a string that uses some special (but still ISO 8859-1) characters like "" 2. select "source/externalize strings" 3. see the messages.properties files and notice that the characters have been escaped
|
2010-07-16 13:24:47
| 1,279,300,000
|
verified fixed
|
04bdb33
| 1,280,140,000
|
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/nls/PropertyFileDocumentModellTest.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/nls/PropertyFileDocumentModel.java
|
JDT
|
472
| 320,511
|
Bug 320511 [infer type arguments] NPE in InferTypeArgumentsConstraintsSolver#getNonTaggingInterfaces()
| null |
2010-07-21 09:59:12
| 1,279,720,000
|
resolved fixed
|
9f5733c
| 1,279,720,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/generics/InferTypeArgumentsConstraintsSolver.java
|
JDT
|
473
| 312,054
|
Bug 312054 [preferences] UserLibraryPreferencePage: After renaming a user library the Up, Down, Remove buttons do not work until dialog is reopened
|
Build Identifier: 20100218-1602 When you open the user library preference page and rename a library, you won't be able to remove jar files from it (or change the order) until you close and reopen the dialog. I am sorry that I do not have the time to dive into the code and search for a fix but I wanted to report it anyways. Reproducible: Always Steps to Reproduce: 1. Open or create a workspace with at least one User Library that has jar files in it 2. Go to the "User Libraries" dialog (e.g. Preferences -> Java -> Build Path -> User Libraries 3. Select a User Library, click Edit and rename it (e.g. Test -> Test2) 4. Try to use the Up/Down/Remove button on one of the jar files inside the user library. The click has no result.
|
2010-05-07 09:06:35
| 1,273,240,000
|
verified fixed
|
14fd31e
| 1,279,690,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/CPListElement.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/CPUserLibraryElement.java
|
JDT
|
474
| 320,199
|
Bug 320199 [preferences] UserLibraryPreferencePage Edit/Remove do not work as expected when same jar is contained in 2 or more libs
| null |
2010-07-18 15:09:17
| 1,279,480,000
|
verified fixed
|
0be9881
| 1,279,610,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/UserLibraryPreferencePage.java
|
JDT
|
475
| 319,860
|
Bug 319860 [organize imports] Unused import added for reference to nested type from Javadoc
|
R3.6 - works in R3.5.x. 1. start with new workspace 2. enable Javadoc processing 3. paste this: --------- %< --------- package p; /** * {@link I}. * @see C */ public class Main { public interface I { } public class C {} } --------- %< --------- 4. Organize Imports (Ctrl+Shift+O) ==> the following unnecessary imports are added and flagged ad unused: import p.Main.C; import p.Main.I; For me this is major as we report unused imports as errors.
|
2010-07-14 10:29:17
| 1,279,120,000
|
verified fixed
|
5281489
| 1,279,560,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/ImportOrganizeTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/dom/Bindings.java
|
JDT
|
476
| 319,854
|
Bug 319854 [search] wrong condition for warning about references to inlined constant
| null |
2010-07-14 09:38:39
| 1,279,110,000
|
resolved fixed
|
995dea0
| 1,279,110,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/SearchUtil.java
|
JDT
|
477
| 240,690
|
Bug 240690 [quick assist] selecting "x.equals(y)" should show the 'Invert equals' quick assist
|
R3.4. Selecting "x.equals(y)" should show the 'Invert equals' quick assist
|
2008-07-14 11:20:15
| 1,216,050,000
|
resolved fixed
|
58137da
| 1,279,040,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
|
478
| 318,772
|
Bug 318772 [build path] help button on "Inclusion and Exclusion Patterns" wizard page does not work
|
The help button shown as a question mark icon on the "Inclusion and Exclusion Patterns" page of the "Edit source folder" wizard does not work when clicked. However, the previous page titled, "Source Folder" does work. Steps to duplicate: * Create a new Java project. * Open the project's properties. * Navigate to Java Build Path. * Click "Add Folder". * Choose a path and click next. * On the "Inclusion and Exclusion Patterns" page, click the help button in the lower-left corner. Actual behavior: * Nothing happens. Expected behavior: * Help side-bar panel opens on the right side of the page. Version: Helios Release Build id: 20100617-1415
|
2010-07-02 19:34:57
| 1,278,110,000
|
resolved fixed
|
11a3256
| 1,278,350,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/SetFilterWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/SourceContainerWorkbookPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/UserLibraryWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/dialogfields/ListDialogField.java
|
JDT
|
479
| 318,661
|
Bug 318661 [breadcrumb] Pressing the 'Open Context Menu' key or Shift+F10 opens the context menu twice
|
R3.4 and latest 3.7 build. Pressing the 'Open Context Menu' key or Shift+F10 opens the context menu twice.
|
2010-07-02 02:45:19
| 1,278,050,000
|
resolved fixed
|
0cd293f
| 1,278,090,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/breadcrumb/BreadcrumbItemDetails.java
|
JDT
|
480
| 318,734
|
Bug 318734 [perfs] Comments applied for JDT/Text performance tests are obsolete
| null |
2010-07-02 10:29:08
| 1,278,080,000
|
resolved fixed
|
958d2cc
| 1,278,080,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/CodeCompletionPerformanceTest.java org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/ContentTypeTest.java org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/OpenJavaEditorStartupTest.java org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/OpenTextEditorStartupTest.java
|
JDT
|
481
| 318,731
|
Bug 318731 [perfs] Comments applied for JDT/UI performance tests are obsolete
| null |
2010-07-02 10:27:30
| 1,278,080,000
|
resolved fixed
|
91b6dd5
| 1,278,080,000
|
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/reorg/MoveStaticMembersPerfTests1.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/reorg/MoveStaticMembersPerfTests2.java org.eclipse.jdt.ui.tests/performance/org/eclipse/jdt/ui/tests/performance/views/CleanUpPerfTest.java
|
JDT
|
482
| 318,607
|
Bug 318607 [ltk] RefactoringParticipant methods declare throws OperationCanceledExeption: exception gets logged
|
org.eclipse.ltk.core.refactoring.participants.RefactoringParticipant.checkConditions() has a throws clause of OperationCanceledException. In my implementation of checkConditions() I check progressMonitor.isCanceled() and then throw the OperationCanceledException. ProcessorBasedRefactoring catches it and logs it, which just seems wrong to me. Of course the workaround is just to return null instead of throwing the OperationCanceledException. RefactoringParticipant.createChange() has the same problem but worse. In this case my participant gets removed from the framework as a result of throwing the OperationCanceledException. I assume createPreChange() has the same issue.
|
2010-07-01 10:26:55
| 1,277,990,000
|
resolved fixed
|
a7fe945
| 1,278,070,000
|
org.eclipse.ltk.core.refactoring.tests/src/org/eclipse/ltk/core/refactoring/tests/participants/CancelingParticipantTests.java org.eclipse.ltk.core.refactoring.tests/src/org/eclipse/ltk/core/refactoring/tests/participants/ParticipantTests.java org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/participants/ProcessorBasedRefactoring.java
|
JDT
|
483
| 318,609
|
Bug 318609 [extract method] Doesn't consider enum type as static
| null |
2010-07-01 10:28:00
| 1,277,990,000
|
verified fixed
|
d292a2f
| 1,277,990,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_in/A_test1058.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_out/A_test1058.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
|
484
| 318,127
|
Bug 318127 [extract method] "Extract Method" into an enclosing class fails when the inner class has a method of the same name
|
Build Identifier: 20100218-1602 When using "Extract Method" on an expression in an inner class to extract it into a method in the enclosing class, and the name of the new method is the same as the name of some method of the inner class, the refactoring fails although there is no name clash. Reproducible: Always Steps to Reproduce: 1. package sandbox; import java.util.HashSet; import java.util.Set; public class A { private class B { private void g() {} private int f() { return 2 + 3; } } } 2. Use Extract Method on the expression "2 + 3" choosing the function name g and destination type A. 3. The refactoring fails with message "Method 'g' already exists in type 'B'."
|
2010-06-27 10:57:06
| 1,277,650,000
|
verified fixed
|
e370b5f
| 1,277,970,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_in/A_test1054.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_in/A_test1055.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_in/A_test1056.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_in/A_test1057.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_out/A_test1054.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_out/A_test1055.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_out/A_test1056.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/destination_out/A_test1057.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/ExtractMethodAnalyzer.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodRefactoring.java
|
JDT
|
485
| 318,388
|
Bug 318388 Replace "org.eclipse.jdt.launching.jreContainerMarker" with JavaRuntime.JRE_CONTAINER_MARKER
| null |
2010-06-29 18:07:11
| 1,277,850,000
|
resolved fixed
|
7aac4b7
| 1,277,850,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/ProblemsLabelDecorator.java
|
JDT
|
486
| 318,255
|
Bug 318255 [rename] RenameMethodProcessor.checkNewElementName(..) should allow _ at beginning
|
Build Identifier: 3.6 At my company, it is a common naming practice to use underscores in front of methods that are "logically protected" -- that is, they have to be public to support cross-package calling, but should be considered protected or discouraged API. This is a convention brought over from Objective-C and WebObjects. RenameMethodProcess.checkNewElementNames when you refactor a method to have a leading underscore because it has a hardcoded "only lowercase names should be used" check. It would actually be nice if this check was either a configuration option or possible leading-underscore could be a case that doesn't trip this check. Reproducible: Always Steps to Reproduce: 1. Create a method named "test" 2. Refactor=>rename the method to "_test" 3. Warning points out that this is discouraged naming in Java
|
2010-06-28 17:40:08
| 1,277,760,000
|
resolved fixed
|
e2d8f0c
| 1,277,830,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/Checks.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameMethodProcessor.java
|
JDT
|
487
| 251,200
|
Bug 251200 [breadcrumb] Remember maximal drop-down height
|
I20081014-1600 Breadcrumb dropdowns should remember their maximal height. It's nice that the default size of the dropdown is as small as possible, but if the list gets long, the height is currently constrained to about 17 items. The dropdown should store the height when the user resized the dropdown, and use the user-specified height as maximal height.
|
2008-10-17 07:05:54
| 1,224,240,000
|
verified fixed
|
fb053dd
| 1,277,470,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/breadcrumb/BreadcrumbItemDropDown.java
|
JDT
|
488
| 310,470
|
Bug 310470 [breadcrumb] Should have "Hide Breadcrumb" in context menu
|
I20100425-2000 The only visible way to hide the breadcrumb again is to click the toolbar button. We should add a "Hide Breadcrumb" item to the context menu (and bind it to the "Toggle Breadcrumb" command). Like "Hide Toolbar".
|
2010-04-26 11:25:18
| 1,272,300,000
|
verified fixed
|
bcb2fed
| 1,277,400,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorBreadcrumbActionGroup.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ToggleBreadcrumbAction.java
|
JDT
|
489
| 231,329
|
Bug 231329 [decorators] decorator for native methods
|
It would be good to have a decoration in the Outline view etc.. showing if a method is native. If there is no remaining real-estate for this, then maybe applying a filter to the entire icon so it appears in grayscale would be the way to go.
|
2008-05-09 11:44:12
| 1,210,350,000
|
resolved fixed
|
d690716
| 1,277,390,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaPluginImages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/BindingLabelProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementImageProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/JavaElementImageDescriptor.java
|
JDT
|
490
| 98,025
|
Bug 98025 [content assist] Code assist should decorate final fields with 'F'
|
Code assist currently shows if members are static, but not if they are final. It's logical to not indicate final methods and classes, since that information is relevant only to subclasses, but whether a field is final or not affects any code that uses it.
|
2005-06-01 18:02:47
| 1,117,660,000
|
resolved fixed
|
1863a04
| 1,277,390,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/CompletionProposalLabelProvider.java
|
JDT
|
491
| 314,283
|
Bug 314283 [package explorer][render] Decorator on CUs for deprecated and package-visible
|
Build Identifier: 20100318-1801 In the Preferences window (General->Appearance->Label Decorations) user can set a check-box "Java Type Indicator". If the box is checked, small icons appear in the Package Explorer: I (interface), A (abstract), E (enum). I propose the following extensions: 1) (more important). Add check-box "Java Deprecated Decorator" which means that deprecated classes will be highlighted somehow in Package Explorer. At once I can imagine 3 variants a) strike-out; b) italic; c) diagonal line like in Outline. As for me, (a) strike-out is the best variant (if the name of a class remains readable). 2) (less important). Add the check-box "Java Throwable Indicator/Decorator" for Throwable and possibly for abstract Throwable (because Throwable can be abstract also). It can be a) Indicator, so small icon will be shown for Throwable (maybe letter "T" and letters "AT" for abstract one). Or b) Decorator and the name of the class become italic for example (if deprecated decorator is not italic) or something like this. Reproducible: Always Steps to Reproduce: 1. Open Package Explorer.
|
2010-05-25 10:40:38
| 1,274,800,000
|
resolved fixed
|
bd8c050
| 1,277,310,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/InterfaceIndicatorLabelDecorator.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaPluginImages.java
|
JDT
|
492
| 313,943
|
Bug 313943 [hovering] Java source hovers not readable using Ubuntu 10.04 (white-on-black tooltips)
| null |
2010-05-21 13:01:03
| 1,274,460,000
|
verified fixed
|
7e2ae03
| 1,277,300,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaEditorAppearanceConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/SourceViewerInformationControl.java
|
JDT
|
493
| 316,199
|
Bug 316199 [JUnit][API] Expose JUnitModel.exportTestRunSession(...) as API
|
There is currently no API that allows plug-ins to make use of the export methods in org.eclipse.jdt.internal.junit.model.JUnitModel: - exportTestRunSession(TestRunSession, File) - exportTestRunSession(TestRunSession, OutputStream) Without a public API, plug-ins that wish to programatically save JUnit test reports or need to feed the XML data into some other process have to register their own TestRunListener and need to duplicate all the business logic that converts test results into the standard XML format. This affects all plug-ins that need to integrate with Eclipse's JUnit support or build additional functionality on top of it. A possible solution for exposing the existing methods as API would be to add them as static methods to JUnitCore and simply delegate to the implementations in JUnitModel. The API methods would use ITestRunSession instead of TestRunSession in their signatures. This would be a fairly simple API addition that would be useful to many technologies that depend on or interact with JUnit.
|
2010-06-08 15:49:04
| 1,276,030,000
|
resolved fixed
|
928f8ec
| 1,277,230,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/ModelMessages.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/junit/JUnitCore.java
|
JDT
|
494
| 312,204
|
Bug 312204 [api][JUnit] Allow changing the default superclass in NewTestCaseWizardPageOne
|
Build Identifier: 20100506-2000 Groovy Eclipse is subclassing from NewTestCaseWizardPageOne to create JUnit wizard for Groovy. It is hard to change the default superclass used for a JUnit3 style testcase. Using setSuperClass doesn't quite work because there is a call to a private method "internalSetJUnit4" which will reset it when a user clicks the JUnit radio buttons. I've attached a patch with a proposed solution that makes a minimal change NewTestCaseWizardPageOne class. The change is behavior preserving, but it delegates the choice of the default superclass for JUnit 3 tests to a protected method which can easily be overriden. Reproducible: Always Steps to Reproduce: NA
|
2010-05-10 00:49:00
| 1,273,470,000
|
resolved fixed
|
c2a6d6f
| 1,277,220,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/wizards/NewTestCaseWizardPageOne.java
|
JDT
|
495
| 308,672
|
Bug 308672 [api] Make JavaElementImageDescriptor.BUILDPATH_ERROR API
| null |
2010-04-09 13:03:15
| 1,270,830,000
|
resolved fixed
|
cd04b95
| 1,277,220,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerProblemsDecorator.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/JavaElementImageDescriptor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/ProblemsLabelDecorator.java
|
JDT
|
496
| 317,474
|
Bug 317474 [render] Javadoc view has 'Open Declaration' tooltip but image is not a link
| null |
2010-06-21 11:42:40
| 1,277,130,000
|
resolved fixed
|
81ec81b
| 1,277,130,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
497
| 313,478
|
Bug 313478 [JUnit] New Test Case wizard: Browse... does nothing
|
Broken since R3.0. 1. make sure the Package Explorer is active but has no selection 2. File > New > JUnit Test Case 3. try to enter 'Class under test' by clicking on 'Browse...' ==> nothing happens
|
2010-05-19 04:21:03
| 1,274,260,000
|
verified fixed
|
d6ca54d
| 1,277,120,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/wizards/NewTestCaseWizardPageOne.java
|
JDT
|
498
| 303,617
|
Bug 303617 [extract constant] Refactoring not available on pop-up if selected string is an annotation
|
Build Identifier: 3.5.1 If I select a string that is the value for an annotation, "Extract constant..." is available on the Refactor menu, but not on the Shift-Alt-T quick menu. This is inconsistent, as it is on that menu for string constants outside of annotations. Reproducible: Always Steps to Reproduce: 1. Select a string constant within @Annotation("string constant") 2. Press Shift-Alt-T 3. Menu item is not available
|
2010-02-23 08:53:23
| 1,266,930,000
|
resolved fixed
|
1a89b9b
| 1,276,880,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringAvailabilityTester.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaTextSelection.java
|
JDT
|
499
| 317,068
|
Bug 317068 [breadcrumb] BreadcrumbItems not disposed when editor closed
|
HEAD BreadcrumbItems are leaked (not disposed) when a Java editor is closed. Found that by adding the following to org.eclipse.swt.widgets.Widget: // --- Find undisposed widgets: --- private Error creation; { creation = new Error("Widget not disposed before finalized! Created at:"); } protected void finalize() throws Throwable { if (!isDisposed()) { creation.printStackTrace(); } } //--- End find undisposed widgets. --- From looking at the code, I think there are more leaks in the breadcrumb: BreadcrumbViewer does not extend handleDispose(), never disposes of the fToolTipLabelProvider (which installs global listeners), etc.
|
2010-06-16 12:19:31
| 1,276,710,000
|
verified fixed
|
4a4bb4a
| 1,276,860,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/breadcrumb/BreadcrumbViewer.java
|
JDT
|
500
| 311,283
|
Bug 311283 [navigation] Open Declaration should work like hyperlink in .java file not on classpath
|
I20100429-1549 Open Declaration (F3) should work like hyperlink (Ctrl+click) in a .java file that is not on the classpath. Use case: I have SWT from CVS, and I'm in Control.java from another platform. Ctrl+click works perfectly for members that are declared in the same file, and it works reasonably well when I Ctrl+click other references (only opens types that are on the classpath, but that's OK and expected). F3 always shows a 'Cannot Perform Operation' dialog, which is unnecessary, since the implementation in the hyperlink could and should be used.
|
2010-05-01 10:17:58
| 1,272,720,000
|
verified fixed
|
ce7cdd8
| 1,276,790,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenAction.java
|
JDT
|
501
| 277,862
|
Bug 277862 [navigate] Show hand pointer for single-click tables and trees
| null |
2009-05-26 10:21:05
| 1,243,350,000
|
verified fixed
|
4cc989a
| 1,276,780,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/breadcrumb/BreadcrumbItemDropDown.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/AbstractInformationControl.java
|
JDT
|
502
| 317,066
|
Bug 317066 [breadcrumb] Exception on clicking folders contained in jars
|
Breadcrumb pop-up throws the following exception when clicking on folders contained in jars, e.g the META-INF folder contained in rt.jar org.eclipse.ui.PartInitException: Could not get an editor input for the given element at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.throwPartInitException(EditorUtility.java:385) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:176) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:152) at org.eclipse.jdt.internal.ui.javaeditor.JavaEditorBreadcrumb.openInNewEditor(JavaEditorBreadcrumb.java:889) at org.eclipse.jdt.internal.ui.javaeditor.JavaEditorBreadcrumb.open(JavaEditorBreadcrumb.java:846) at org.eclipse.jdt.internal.ui.javaeditor.breadcrumb.EditorBreadcrumb.doOpen(EditorBreadcrumb.java:350) at org.eclipse.jdt.internal.ui.javaeditor.breadcrumb.EditorBreadcrumb.doRevealOrOpen(EditorBreadcrumb.java:335) at org.eclipse.jdt.internal.ui.javaeditor.breadcrumb.EditorBreadcrumb.access$8(EditorBreadcrumb.java:332) at org.eclipse.jdt.internal.ui.javaeditor.breadcrumb.EditorBreadcrumb$3.open(EditorBreadcrumb.java:254) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:845) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:843) at org.eclipse.jdt.internal.ui.javaeditor.breadcrumb.BreadcrumbViewer.fireMenuSelection(BreadcrumbViewer.java:541) at org.eclipse.jdt.internal.ui.javaeditor.breadcrumb.BreadcrumbItemDropDown.openElement(BreadcrumbItemDropDown.java:502) at org.eclipse.jdt.internal.ui.javaeditor.breadcrumb.BreadcrumbItemDropDown.access$4(BreadcrumbItemDropDown.java:497) at org.eclipse.jdt.internal.ui.javaeditor.breadcrumb.BreadcrumbItemDropDown$4.mouseUp(BreadcrumbItemDropDown.java:359) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:213) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) 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:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
|
2010-06-16 12:15:30
| 1,276,700,000
|
resolved fixed
|
317b290
| 1,276,710,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorBreadcrumb.java
|
JDT
|
503
| 317,057
|
Bug 317057 [create on paste] Paste to Working Set should work
|
Pasting a source snippet to a working set in the the Package Explorer should paste the snippet to a new project and add the project to the working set.
|
2010-06-16 11:21:27
| 1,276,700,000
|
resolved fixed
|
d0106f8
| 1,276,700,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/PasteAction.java
|
JDT
|
504
| 316,155
|
Bug 316155 JUnit View: can't open source for test classes in fragments
| null |
2010-06-08 11:07:19
| 1,276,010,000
|
resolved fixed
|
6c10486
| 1,276,530,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/OpenEditorAction.java
|
JDT
|
505
| 316,756
|
Bug 316756 [nls tooling] Hover resolution of NLS references is thrown off by unused, incorrect 'BUNDLE_NAME'
|
I sort of stumbled on this. If a client has an NLS class where the (a) the .properties file is named after the NLS class (b) the NLS class passes Messages.class.getName() to the NLS.initializeMessages() method, and (c) the NLS has an unused BUNDLE_NAME definition that is incorrect ...the support to show the NLS string value by hovering over the reference is unnecessarily confused. The resolution logic appears to give precedence to using the BUNDLE_NAME over what is passed to the NLS.initializeMessages() method. Clearly, the latter is a more accurate source and should be given precedence. To reproduce: 1. Import the attached project into a workspace 2. Open SampleAction.java and hover over "SampleAction_0". You will see the hover popup show "Hello World". This is expected, working behavior. 3. Open Messages.java. Uncomment the definition of BUNDLE_NAME. 4. Repeat step 2. You will see "The properties file could not be detected", even though BUNDLE_NAME is unused.
|
2010-06-14 09:26:47
| 1,276,520,000
|
resolved fixed
|
f170568
| 1,276,520,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/nls/NLSHintHelper.java
|
JDT
|
506
| 316,627
|
Bug 316627 [refactoring] Refactoring does not give warning about modifying derived resources
|
Build Identifier: M20100211-1343 The first time I try to edit a derived resource, Eclipse gives a warning about the resource being derived. However, when some refactoring would change that same resource, no warning is issued. Reproducible: Always Steps to Reproduce: 1. Generate some Java classes with some tool like ANTLR 2. Mark the generated sources as derived 3. Create a normal class that refers to one of the generated classes 4. Rename the generated class by changing its name in the class that refers it 5. Eclipse will complete the refactor without any warning, but once you regenerate your ANTLR code, you will have compile errors
|
2010-06-11 11:18:30
| 1,276,270,000
|
resolved fixed
|
5cf3a33
| 1,276,520,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/ActionUtil.java org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/AbstractChangeNode.java
|
JDT
|
507
| 103,450
|
Bug 103450 [quick assist] Quick fix to remove synchronized block
|
I would like a Quick Fix option to "remove surrounding 'synchronized' statement", just like you can do with an "if" statement.
|
2005-07-12 02:13:14
| 1,121,150,000
|
resolved fixed
|
0b13a78
| 1,276,270,000
|
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/QuickAssistProcessor.java
|
JDT
|
508
| 314,777
|
Bug 314777 New Source folder wizard enables finish without valid project
|
Steps: 1. Start with clean workspace 2. Right click in package explorer 3. Select New > Source Folder 4. Click Finish The error below is logged. -- Configuration Details -- Product: Eclipse 1.3.0.20100526-1935 (org.eclipse.epp.package.java.product) eclipse.buildId=I20100520-1744 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product -data ws Error Thu May 27 13:51:44 PDT 2010 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:1008) at org.eclipse.jdt.internal.ui.wizards.NewElementWizard.performFinish(NewElementWizard.java:133) at org.eclipse.jdt.internal.ui.wizards.NewSourceFolderCreationWizard.performFinish(NewSourceFolderCreationWizard.java:54) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:811) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:430) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1234) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3159) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:135) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1234) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3159) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) Caused by: java.lang.NullPointerException at org.eclipse.jdt.internal.ui.wizards.NewSourceFolderWizardPage.createPackageFragmentRoot(NewSourceFolderWizardPage.java:478) at org.eclipse.jdt.internal.ui.wizards.NewSourceFolderCreationWizard.finishPage(NewSourceFolderCreationWizard.java:47) at org.eclipse.jdt.internal.ui.wizards.NewElementWizard$2.run(NewElementWizard.java:117) at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:4777) at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
|
2010-05-27 17:02:34
| 1,274,990,000
|
verified fixed
|
6943bb3
| 1,276,250,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewSourceFolderWizardPage.java
|
JDT
|
509
| 313,339
|
Bug 313339 Remove unused internal deprecated code
|
I20100518-0800. Remove unused internal deprecated code.
|
2010-05-18 08:50:51
| 1,274,190,000
|
resolved fixed
|
dfe220d
| 1,276,160,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/ClasspathModifierQueries.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/newsourcepage/LinkFolderDialog.java
|
JDT
|
510
| 312,659
|
Bug 312659 Remove unused NLS keys
| null |
2010-05-12 12:03:37
| 1,273,680,000
|
resolved fixed
|
710969c
| 1,276,160,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMessages.java
|
JDT
|
511
| 314,354
|
Bug 314354 [common navigator] Project Explorer does not refresh on adding/removing library to a project
|
I20100520-1744 Steps - New Workspace - New Java project - In 'Project Explorer' right click on the java project -> Build Path -> Configure Build Path - 'Libraries' tab -> 'Add Library' -> add JUnit 3 and click Ok to close the dialog => The newly added library does not show up in Project Explorer - Manually refresh the project (F5) => Library added in last step shows up Auto refresh also does not happen when the library is removed.
|
2010-05-25 16:20:33
| 1,274,820,000
|
verified fixed
|
5d6e440
| 1,275,510,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/navigator/JavaNavigatorContentProvider.java
|
JDT
|
512
| 313,972
|
Bug 313972 [projection] Java editor randomly crashes when opening certain Java files (throws IllegalStateException)
| null |
2010-05-21 15:30:54
| 1,274,470,000
|
verified fixed
|
2cfdc43
| 1,275,400,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/folding/DefaultJavaFoldingStructureProvider.java
|
JDT
|
513
| 314,585
|
Bug 314585 [hovering] NPE in JavadocHover when annotation value is a primitive type
|
Build Identifier: I20100429-1549 From within the java editor, hovering over the interface (Service1Soap) of an implementation such as: "public class Service1_Service1SoapImpl implements Service1Soap {..." Produces the following stack trace: java.lang.NullPointerException at org.eclipse.jdt.internal.ui.viewsupport.JavaElementLabelComposer.appendElementLabel(JavaElementLabelComposer.java:263) at org.eclipse.jdt.internal.ui.viewsupport.JavaElementLinks.getElementLabel(JavaElementLinks.java:514) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.addValue(JavadocHover.java:1013) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.addValue(JavadocHover.java:1040) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.addAnnotation(JavadocHover.java:1003) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getAnnotations(JavadocHover.java:980) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.addAnnotations(JavadocHover.java:928) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo(JavadocHover.java:595) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.internalGetHoverInfo(JavadocHover.java:546) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo2(JavadocHover.java:538) at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:141) at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo2(JavaEditorTextHoverProxy.java:82) at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166) The interface class is contained within a jar. Reproducible: Always Steps to Reproduce: 1.Create a Dynamic Web Project 2.Import a jar with a webservice endpoint interface 3.Create a service implementation that references this interface 4.Hover over the interface name from the implementation (I have a jar and implementation available let me know thxs)
|
2010-05-26 18:48:59
| 1,274,910,000
|
verified fixed
|
bd8d455
| 1,274,980,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
514
| 313,586
|
Bug 313586 [preferences] Expose new preference in the UI
| null |
2010-05-19 13:34:47
| 1,274,290,000
|
verified fixed
|
a286949
| 1,274,350,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/LineWrappingTabPage.java
|
JDT
|
515
| 312,966
|
Bug 312966 [hovering] Some text in Javadoc hover/view not visible using Ubuntu 10.04
|
I20100513-1500 I am using the default colors on Ubuntu 10.04 and some of the tooltips display black text on black background. Will attach a screenshot.
|
2010-05-14 15:16:22
| 1,273,860,000
|
verified fixed
|
1eb46da
| 1,274,350,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/SourceViewerInformationControl.java
|
JDT
|
516
| 313,680
|
Bug 313680 [nls tooling][spell checking] Typing in Properties File editor removes all spelling errors
|
R3.5 and N20100519-2000. Typing in Properties File editor removes all spelling errors.
|
2010-05-20 05:24:40
| 1,274,350,000
|
verified fixed
|
81eacda
| 1,274,350,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesFileSourceViewerConfiguration.java
|
JDT
|
517
| 312,074
|
Bug 312074 The "Link Source' wizard in the Build Path property page does not show Project Path Variables
|
Reproducible: Always Steps to Reproduce: * In the Java perspective, right click a Java project, goto Build Path > Link Source... * Select Variables... Notice that none of the project path variables are listed (to see the project path variable list, see the property page "Resource / Linked Resources"). This is done by adding in 'AddSourceFolderWizardPage.java" line 171: PathVariableSelectionDialog dialog = new PathVariableSelectionDialog(getShell(), variableTypes); dialog.setResource(fParent); Note that internally, the resolution of that Path (if done manually) must call IResource.getPathVariableManager() instead of IWorkspace.getPathVariableManager().
|
2010-05-07 10:43:04
| 1,273,240,000
|
verified fixed
|
ceffa58
| 1,274,260,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/AddSourceFolderWizardPage.java
|
JDT
|
518
| 312,867
|
Bug 312867 [extract method] NPE when trying to "Extract Method"
|
Build Identifier: I20100312-1448 eclipse.buildId=I20100312-1448 java.version=1.6.0_18 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE Command-line arguments: -os win32 -ws win32 -arch x86 Error Fri May 14 09:44:30 GMT+01:00 2010 Internal Error java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:330) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.createChange(RefactoringWizard.java:599) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.computeUserInputSuccessorPage(RefactoringWizard.java:438) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.computeSuccessorPage(UserInputWizardPage.java:74) at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.getNextPage(UserInputWizardPage.java:114) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.nextOrPreviewPressed(RefactoringWizardDialog2.java:495) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.access$2(RefactoringWizardDialog2.java:492) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2$1.widgetSelected(RefactoringWizardDialog2.java:691) 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:1050) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4037) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3628) 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:180) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:192) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:115) at org.eclipse.jdt.internal.ui.refactoring.actions.RefactoringStarter.activate(RefactoringStarter.java:38) at org.eclipse.jdt.ui.actions.ExtractMethodAction.run(ExtractMethodAction.java:87) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:278) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1050) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4037) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3628) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2416) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2380) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2229) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:504) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:497) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) 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:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1406) Caused by: java.lang.NullPointerException at org.eclipse.jdt.internal.corext.refactoring.util.SelectionAwareSourceRangeComputer.initializeRanges(SelectionAwareSourceRangeComputer.java:94) at org.eclipse.jdt.internal.corext.refactoring.util.SelectionAwareSourceRangeComputer.computeSourceRange(SelectionAwareSourceRangeComputer.java:47) at org.eclipse.jdt.internal.core.dom.rewrite.RewriteEventStore$NodeRangeInfo.updatePlaceholderSourceRanges(RewriteEventStore.java:189) at org.eclipse.jdt.internal.core.dom.rewrite.RewriteEventStore.processListWithRanges(RewriteEventStore.java:756) at org.eclipse.jdt.internal.core.dom.rewrite.RewriteEventStore.prepareNodeRangeCopies(RewriteEventStore.java:737) at org.eclipse.jdt.internal.core.dom.rewrite.RewriteEventStore.prepareMovedNodes(RewriteEventStore.java:686) at org.eclipse.jdt.core.dom.rewrite.ASTRewrite.internalRewriteAST(ASTRewrite.java:268) at org.eclipse.jdt.core.dom.rewrite.ASTRewrite.rewriteAST(ASTRewrite.java:260) at org.eclipse.jdt.internal.corext.refactoring.code.ExtractMethodRefactoring.createChange(ExtractMethodRefactoring.java:531) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Reproducible: Always Steps to Reproduce: 1.I want to extract a method from following code snippet: try { String absoluteFileName = file.getAbsolutePath(); String urlEncodedFileName = URLEncoder.encode(absoluteFileName, "UTF-8"); //$NON-NLS-1$ URL url = new URL("file://" + urlEncodedFileName); //$NON-NLS-1$ ResourceLocatorTool.addResourceLocator(ResourceLocatorTool.TYPE_TEXTURE, new SimpleResourceLocator(url)); exporter.save(spatial, file); return true; } catch (IOException e) { ... I wanted to extract line 2-4 (inclusive) to an extra method an I got the exception.
|
2010-05-14 03:52:18
| 1,273,820,000
|
verified fixed
|
adba2ac
| 1,274,200,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/validSelection_in/A_test374.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/validSelection_out/A_test374.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/util/SelectionAwareSourceRangeComputer.java
|
JDT
|
519
| 313,080
|
Bug 313080 SpellCheckingTest#test() runs very fast
|
SpellCheckingTest#test() seems to run very fast on all platforms since it was added in Jan 2010. I suspect something is wrong as this test takes about 300ms on my machine.
|
2010-05-17 04:27:00
| 1,274,080,000
|
verified fixed
|
b18d7e5
| 1,274,180,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/PerformanceTestSuite.java org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/SpellCheckingTest.java
|
JDT
|
520
| 310,641
|
Bug 310641 [refactoring] Refactoring history doesn't seem to be formatting strings properly
|
I20100426-0852 1. Create a Java project. 2. Make a class in the source folder. 3. Delete it. 4. Access the project's properties > Refactoring history 5. Keep expanding, you'll see a 'Delete element' entry, select it. 6. I get the following in the details text box. Delete element from {1} - Original project: 'Test' - Original element: 'Main.java'
|
2010-04-27 10:31:06
| 1,272,380,000
|
verified fixed
|
2a5fe25
| 1,273,690,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/JavaDeleteProcessor.java
|
JDT
|
521
| 310,396
|
Bug 310396 [implementation] Deadlock in SharedASTProvider.getAST()
| null |
2010-04-25 17:43:38
| 1,272,230,000
|
verified fixed
|
e447d77
| 1,273,680,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ASTProvider.java
|
JDT
|
522
| 310,903
|
Bug 310903 [hovering] Javadoc hovers don't show annotations on constructors
| null |
2010-04-28 16:17:57
| 1,272,490,000
|
verified fixed
|
e4c4eb8
| 1,273,680,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
523
| 310,982
|
Bug 310982 [hovering] Improve rendering of class references in annotation hovers
|
HEAD See e.g. hover for org.junit.tests.running.classes.SuiteTest.All: - type links should not be fully qualified - type links should not be rendered in 'header' style (should show underlines)
|
2010-04-29 05:46:17
| 1,272,530,000
|
verified fixed
|
a62c40d
| 1,273,670,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
524
| 105,668
|
Bug 105668 [quick fix] place @SuppressWarnings on variables
|
3.1 add an option to place the @SuppressWarning annotation in the smallest scope you can. Currently, it never adds it to local variables or parameters but places them on the method which is potentially dangerous because it hides all warnings in the method
|
2005-08-01 09:57:58
| 1,122,900,000
|
verified fixed
|
70921e0
| 1,273,670,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/ModifierCorrectionsQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/SuppressWarningsSubProcessor.java
|
JDT
|
525
| 120,615
|
Bug 120615 [hovering] Javadoc Viewer doesn't display {@link ... } properly if text is just whitespace
|
I20051213-0010 While browsing doc using the viewer I noticed that the following java doc excerpt from the merge method in IMergeContext: * For two-way merging, clients can either accept changes using the * {@link #merge(IDiffNode[], boolean, IProgressMonitor) } method or reject * them using {@link #markAsMerged(IFile, boolean, IProgressMonitor) }. corresponds to the following output in the Javadoc viewer: For two-way merging, clients can either accept changes using the method or reject them using . It seems that this is only true for links to local methods.
|
2005-12-13 11:42:46
| 1,134,490,000
|
verified fixed
|
095d008
| 1,273,670,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavadocContentAccess2.java
|
JDT
|
526
| 310,993
|
Bug 310993 [hovering] {@value} resolution in Javadoc doesn't work if constant doesn't explicitly declare static final
| null |
2010-04-29 06:48:38
| 1,272,540,000
|
verified fixed
|
be62923
| 1,273,670,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavadocContentAccess2.java
|
JDT
|
527
| 285,137
|
Bug 285137 [content assist] Completing method from unresolved variable removes code in case of * import
|
Hello, apologies if this is filed in the wrong place. I use content assist extensively; I also use the Java -> Code Style -> Organize Imports "Number of imports needed for .*" feature with value of 2. I'm constantly running into an interaction between the two - when I use the completion of content assist (as in the following example), it deletes code after the insertion point (it deletes the number of characters saved by optimising the import). I can avoid this interaction by changing the "Number of imports needed for .*" to 9999 In my example I'm talking about KeyPair, which is in com.amazonaws.ec2.model; I don't have an import for it but I do have an import for "TerminatingInstance", also in that package (I have Number of imports needed for .* set to 2) import com.amazonaws.ec2.model.TerminatingInstance; public class Test { public static void main(String[] args) { KeyPair kp = null; kp.toStr } public void bufferMethodToBeEatenByBug() { } } When I press control+space at "kp.toStr" to get the completion for toString and accept the default, the code changes to the following (which, as you can see, has toString() but has deleted a lot of code following it) import com.amazonaws.ec2.model.*; public class Test { public static void main(String[] args) { KeyPair kp = null; kp.toString() bufferMethodToBeEatenByBug() { } } ---- Another thing I noticed while producing this simple testcase: If the number of characters that would be deleted is greater than the number of characters left in the file then I get some odd behaviour: the import is made and optimised but the method name completion fails, leaving me with "kp.toStr" again but "import com.amazonaws.ec2.model.*;" (to accomplish this I simply deleted bufferMethodToBeEatenByBug in my testcase): import com.amazonaws.ec2.model.TerminatingInstance; public class Test { public static void main(String[] args) { KeyPair kp = null; kp.toStr } } Which, after content assist, became... import com.amazonaws.ec2.model.*; public class Test { public static void main(String[] args) { KeyPair kp = null; kp.toStr } }
|
2009-07-30 06:51:17
| 1,248,950,000
|
verified fixed
|
81a3965
| 1,273,590,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/AbstractJavaCompletionProposal.java
|
JDT
|
528
| 295,429
|
Bug 295429 [package explorer] Adding resource filters causes grief
|
I20091117-1545. Adding resource filters to a container breaks the Package Explorer: the filtered element remains in the UI as '?'. Test Case: 1. create Java project 2. add second source folder 'src2' 3. add resource filter on project for 'src' ==> '?' in the UI plus exceptions in the .log Talking to Szymon: there's no special flag. Adding a filter triggers a delete delta which we seem not to handle correctly. !ENTRY org.eclipse.jdt.ui 4 10001 2009-11-18 12:48:02.786 !MESSAGE Internal Error !STACK 1 Java Model Exception: Java Model Status [src [in a] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238) at org.eclipse.jdt.internal.core.PackageFragmentRoot.getKind(PackageFragmentRoot.java:477) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:645) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:791) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:734) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.handleAffectedChildren(PackageExplorerContentProvider.java:791) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.processDelta(PackageExplorerContentProvider.java:734) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider.elementChanged(PackageExplorerContentProvider.java:124) at org.eclipse.jdt.internal.core.DeltaProcessor$3.run(DeltaProcessor.java:1557) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1547) at org.eclipse.jdt.internal.core.DeltaProcessor.firePostChangeDelta(DeltaProcessor.java:1381) at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1357) at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1958) at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:470) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:325) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1063) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) !SUBENTRY 1 org.eclipse.jdt.core 4 969 2009-11-18 12:48:02.786 !MESSAGE src [in a] does not exist
|
2009-11-18 06:45:38
| 1,258,540,000
|
verified fixed
|
f5ab282
| 1,273,590,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerContentProvider.java
|
JDT
|
529
| 298,951
|
Bug 298951 OpenTypePerfTest#testWarmException() perf tests results are not reliable
|
Verifying performance results for all 3.6M4 scenarios, it appears that results for OpenTypePerfTest#testWarmException() test are completely unreliable (on all test machines). It seems that something should be done to stabilize this test or remove it from the benchmark.
|
2010-01-06 10:01:16
| 1,262,790,000
|
resolved fixed
|
bf100f2
| 1,273,570,000
|
org.eclipse.jdt.ui.tests/performance/org/eclipse/jdt/ui/tests/performance/views/OpenTypePerfTest.java
|
JDT
|
530
| 310,551
|
Bug 310551 [render] UIEJB3Validator reports a build path problem
| null |
2010-04-26 17:55:50
| 1,272,320,000
|
verified fixed
|
e42c61d
| 1,273,570,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/JavaPluginImages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerProblemsDecorator.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/JavaElementImageDescriptor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/ProblemsLabelDecorator.java
|
JDT
|
531
| 311,835
|
Bug 311835 [preferences] Add option for FORMATTER_USE_ON_OFF_TAGS (bug 311582)
| null |
2010-05-06 04:48:03
| 1,273,140,000
|
verified fixed
|
bb07ae5
| 1,273,500,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/OffOnTagsTabPage.java
|
JDT
|
532
| 310,690
|
Bug 310690 [type wizards] New class wizard eagerly fills input text fields
|
I20100426-0852 1. Ctrl+3 > Add All Plug-ins to Java Search 2. File > New > Other... > Java > Class 3. The source folder is prepopulated with "External Plug-in Libraries" even though the 'Package Explorer' view is empty. I think the wizards should always respect the selection. If nothing is selected then nothing should be filled.
|
2010-04-27 14:37:11
| 1,272,390,000
|
verified fixed
|
2381e9a
| 1,273,150,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewContainerWizardPage.java
|
JDT
|
533
| 301,455
|
Bug 301455 [type hierarchy] AssertionFailedException pressing F4 by mistake
|
Using eclipse.buildId=I20100128-1731 java.version=1.6.0_18-ea java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_CA Command-line arguments: -os win32 -ws win32 -arch x86 -console, I got this exception by pressing F4 by mistake. I could not reproduce, but I think it is worth being reported anyway. org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: assertion failed: ContentViewer must have a content provider when input is set.) at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3959) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3580) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2407) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2371) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2220) 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:115) 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:367) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:611) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:566) at org.eclipse.equinox.launcher.Main.run(Main.java:1363) at org.eclipse.equinox.launcher.Main.main(Main.java:1339) Caused by: org.eclipse.core.runtime.AssertionFailedException: assertion failed: ContentViewer must have a content provider when input is set. at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:266) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1634) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyViewPart.setViewersInput(TypeHierarchyViewPart.java:1804) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle$3.run(TypeHierarchyLifeCycle.java:254) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 23 more
|
2010-02-01 14:38:13
| 1,265,050,000
|
verified fixed
|
147f1e3
| 1,273,040,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyLifeCycle.java
|
JDT
|
534
| 304,217
|
Bug 304217 [type hierarchy] Widget is disposed error on type hierarchy computation
|
Using I20100224-2242, it looks like background processing of type hierarchies can cause some issues when a widget is disposed. I don't have steps to reproduce. org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed) at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3989) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3608) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2408) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2372) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:501) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:494) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:611) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:566) at org.eclipse.equinox.launcher.Main.run(Main.java:1363) at org.eclipse.equinox.launcher.Main.main(Main.java:1339) Caused by: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.widgets.Widget.error(Widget.java:467) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340) at org.eclipse.swt.widgets.Label.setText(Label.java:387) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyViewPart.updateHierarchyViewer(TypeHierarchyViewPart.java:1163) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyViewPart.clearInput(TypeHierarchyViewPart.java:612) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyViewPart.access$13(TypeHierarchyViewPart.java:608) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyViewPart$20.run(TypeHierarchyViewPart.java:1779) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 23 more
|
2010-03-01 10:34:38
| 1,267,460,000
|
verified fixed
|
3a22874
| 1,273,040,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyViewPart.java
|
JDT
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.