issue_id
int64 2.03k
426k
| title
stringlengths 9
251
| body
stringlengths 1
32.8k
⌀ | status
stringclasses 6
values | after_fix_sha
stringlengths 7
7
| updated_files
stringlengths 29
34.1k
| project_name
stringclasses 6
values | repo_url
stringclasses 6
values | repo_name
stringclasses 6
values | language
stringclasses 1
value | issue_url
null | before_fix_sha
null | pull_url
null | commit_datetime
unknown | report_datetime
unknown |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
335,147 | Bug 335147 [breadcrumb] Breadcrumb does not honor package name abbreviation setting | null | resolved fixed | 82f644f | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorBreadcrumb.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-24T11:42:11Z" | "2011-01-24T06:20:00Z" |
334,876 | Bug 334876 [quick assist] Invert conditions generates incorrect code | Build Identifier: 20100917-0705 Let a and b be of Object type, the following expression: a == null ^ b == null is inverted incorrectly to: !a == null ^ b == null which does not compile (The operator ! is undefined for the argument type(s) Object). The correct result should be: a != null ^ b == null It seems, that left-hand side argument is simply prefixed with !, but it should be recursively inverted as a separate expression. Reproducible: Always | resolved fixed | 4f0aa93 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-22T06:49:59Z" | "2011-01-20T13:26:40Z" |
333,541 | Bug 333541 [preferences] "Show whitespace characters" gets toggled when "whitespace characters" dialog is opened | null | resolved fixed | e97d3c3 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-21T11:00:42Z" | "2011-01-05T09:33:20Z" |
334,690 | Bug 334690 [preferences] Add new formatter option for the new JDT/Core option added in bug 282988 | null | verified fixed | 09928bc | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/CommentsTabPage.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/FormatterMessages.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-20T15:39:37Z" | "2011-01-18T19:46:40Z" |
332,019 | Bug 332019 [quick assist] Exchange operands must add parentheses sometimes | I20101206-1800 Exchange operands quick assist must add parentheses sometimes, e.g. when invoked on the second != in these statements: static void foo(int a, long b) { System.out.println(b != 0 != (a == b)); System.out.println(b != 0 != true); } | resolved fixed | 12ccaea | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-19T18:33:27Z" | "2010-12-07T13:53:20Z" |
334,625 | Bug 334625 [jar exporter] Destination starting with '/' or '\' announced as being relative to the workspace | 3.7 M4 but broken since 3.0. When using a destination starting with '/' or '\' in the JAR exporter the wizard's descriptions says that it will be relative to the workspace. This is wrong, it will be in the root of the current working directory (user.dir). 1. in the JAR Export wizard's 'JAR file' field enter: "/foo.jar or \foo.jar ==> the wizard's description says: "The export destination will be relative to your workspace." 2. export ==> observe: the file will not be placed relative to the workspace. | verified fixed | 095f686 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/AbstractJarDestinationWizardPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-18T11:24:03Z" | "2011-01-18T11:26:40Z" |
333,803 | Bug 333803 [move member type] Move Type to New File creates compile error with parametrized outer type | HEAD The 'Move Type to New File' refactoring creates a compile error when the member type contains an array access expression: public class Outer { private final Object[] fSet= new Object[1]; class Inner { //Move Type to New File void foo() { System.out.println(fSet[0]); // broken // System.out.println(fSet); // OK } } } | resolved fixed | fdd2df1 | ["org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_49/in/A.java", "org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_49/out/A.java", "org.eclipse.jdt.ui.tests.refactoring/resources/MoveInnerToTopLevel/test_nonstatic_49/out/B.java", "org.eclipse.jdt.ui.tests.refactoring/test", "cases/org/eclipse/jdt/ui/tests/refactoring/MoveInnerToTopLevelTests.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/dom/Bindings.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInnerToTopRefactoring.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-18T08:17:10Z" | "2011-01-08T18:06:40Z" |
334,480 | Bug 334480 [quick fix] create method incorrectly makes static method when called from inner class in static method | Build Identifier: M20100909-0800 Consider Following Java class 'Foo' public class Foo { public static void bar(final Foo f) { new Object() { void foo() { f.foobar(); // invoke quick fix here } }; } } When you execute the quick fix "Create method 'foobar()' in type 'Foo'", eclipse makes a static method in Foo: protected static void foobar() { // TODO Auto-generated method stub } A non-static method would be correct as we are invoking foobar explicitly on an instance of Foo. So the correct method in Foo would be protected void foobar() { // TODO Auto-generated method stub } Note: If bar is non-static, the correct method is already made by the quick fix. Reproducible: Always Steps to Reproduce: 1. Create class Foo as given in the description 2. Invoke the create method quick fix | resolved fixed | 97a1d54 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedMethodsQuickFixTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/NewMethodCorrectionProposal.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-17T14:56:23Z" | "2011-01-16T15:00:00Z" |
332,053 | Bug 332053 [call hierarchy] Clearing history should clear the status bar | I20101025-1800 Steps - Open call hierarchy on a method - Call Hierarchy view > History > Clear History => the status bar still says displays the element name. | verified fixed | ef7e18a | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyViewPart.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-11T08:46:45Z" | "2010-12-07T16:40:00Z" |
333,654 | Bug 333654 AIOOBE in IdentityHashSet.getInsertionIndex(*) | On of the test teams reported intermittent failures from ArrayIndexOutOfBoundsExceptions on 64 bit JVMs in org.eclipse.jdt.ui.leaktest.reftracker.IdentityHashSet.getInsertionIndex(Object, Object[]). It seems System.identityHashCode(*) is returning an extremely large number, which results in the modulo being negative. It should probably be protected against numbers larger than 0x7FFFFFFF PW | resolved fixed | 135fdc5 | ["org.eclipse.jdt.ui.tests/leaks/org/eclipse/jdt/ui/leaktest/reftracker/IdentityHashSet.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-06T17:44:00Z" | "2011-01-06T13:20:00Z" |
333,631 | Bug 333631 [nls tooling] Rename properties key/field adds additional '=' | 3.4. Renaming a property key/field in the Java editor can result in an additional '=' being added to property value. Steps: 0. start with new workspace using 1.6 JRE 1. Import the attached ZIP as 'Existing Project into Workspace' 2. open type 'Test' 3. select the 'Test_0' 4. Refactor > Rename it to "Bug" ==> The entry in the properties file now has an additional '=': BUG== BUG | verified fixed | 80a31f2 | ["org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/nls/PropertyFileDocumentModel.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-06T09:19:37Z" | "2011-01-06T10:33:20Z" |
332,982 | Bug 332982 [hovering] Exception when showing JavaDoc hover | When hovering over a base Java class I don't get a tooltip but an exception is thrown instead java.lang.NullPointerException at org.eclipse.jdt.internal.corext.javadoc.JavaDocLocations.getBaseURL(JavaDocLocations.java:605) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo(JavadocHover.java:630) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.internalGetHoverInfo(JavadocHover.java:555) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo2(JavadocHover.java:547) 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) I've been checking my JavaDoc and source attachments for the JDK being used and they appear to be OK. | resolved fixed | 750bdb6 | ["org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/javadoc/JavaDocLocations.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/OpenBrowserUtil.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-04T16:57:19Z" | "2010-12-21T00:06:40Z" |
331,447 | Bug 331447 [preferences] UI for COMPILER_PB_UNAVOIDABLE_GENERIC_TYPE_PROBLEMS | null | resolved fixed | 7484f6e | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ProblemSeveritiesConfigurationBlock.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-04T14:23:13Z" | "2010-11-30T15:13:20Z" |
331,311 | Bug 331311 [syntax highlighting] Syntax coloring for abstract classes | Build Identifier: 20100917-0705 I find it very useful to colorizes interfaces and abstract classes with the same color with JDT built in syntax coloring. Unfortunately, it isn't possible to assign different colors for classes and abstract classes in preferences->java->syntax coloring->element->java. Reproducible: Always Steps to Reproduce: Open a java source file containing references to classes and abstract classes and try to assign different colors. | resolved fixed | 488c97e | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/SemanticHighlightingTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/SemanticHighlightings.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaEditorColoringConfigurationBlock.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-01-03T15:53:36Z" | "2010-11-29T11:26:40Z" |
332,271 | Bug 332271 [quick assist] Use ()+ icon for quick assists which add parentheses around expressions | null | resolved fixed | e45ec0e | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-15T07:09:34Z" | "2010-12-10T05:46:40Z" |
332,008 | Bug 332008 [quick fix] Quick fix can be improved in 1.4/1.5 mixed projects | null | resolved fixed | 3a75e93 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/TypeMismatchQuickFixTests.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility2.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/TypeMismatchSubProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-14T14:30:29Z" | "2010-12-07T11:06:40Z" |
332,034 | Bug 332034 [breadcrumb] Java Model Exceptions in log when opening Java Editor for nonexistent file | I20101206-1800, has probably been like this for a long time - create a Java class - show breadcrumb - delete the .java file - Navigate > Back => status editor opens with message "Resource .../C.java does not exist" => at the same time and shortly after, I get about 4 exceptions like the one below in the log Expected: Nothing in log !ENTRY org.eclipse.jdt.ui 4 10001 2010-12-07 16:35:38.507 !MESSAGE Internal Error !STACK 1 Java Model Exception: Java Model Status [C.java [in <default> [in src [in P]]] 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.JavaElement.getChildren(JavaElement.java:193) at org.eclipse.jdt.internal.core.JavaElement.getSourceElementAt(JavaElement.java:367) at org.eclipse.jdt.internal.core.CompilationUnit.getElementAt(CompilationUnit.java:701) at org.eclipse.jdt.internal.ui.actions.SelectionConverter.getElementAtOffset(SelectionConverter.java:285) at org.eclipse.jdt.internal.ui.javaeditor.JavaEditorBreadcrumb.getCurrentInput(JavaEditorBreadcrumb.java:791) at org.eclipse.jdt.internal.ui.javaeditor.JavaEditorBreadcrumb.setInput(JavaEditorBreadcrumb.java:763) at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.setBreadcrumbInput(JavaEditor.java:1985) at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.selectionChanged(JavaEditor.java:2241) at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor$EditorSelectionChangedListener.selectionChanged(JavaEditor.java:298) at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2746) at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2694) at org.eclipse.jface.text.TextViewer$5.run(TextViewer.java:2673) at org.eclipse.swt.widgets.Display.runTimers(Display.java:3933) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3445) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) !SUBENTRY 1 org.eclipse.jdt.core 4 969 2010-12-07 16:35:38.507 !MESSAGE C.java [in <default> [in src [in P]]] does not exist | verified fixed | eed33bb | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorBreadcrumb.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-14T09:02:42Z" | "2010-12-07T16:40:00Z" |
332,489 | Bug 332489 [quick assist] 'exchange left and right operands' for comparison operators changes semantics | null | resolved fixed | 56d0c83 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-14T03:58:39Z" | "2010-12-14T04:13:20Z" |
332,421 | Bug 332421 [nls tooling] Hyperlink on properties file key doesn't work across projects | N20101212-2000 - import org.eclipse.ui.ide and org.eclipse.ui.ide.application from CVS - open this file: /org.eclipse.ui.ide/src/org/eclipse/ui/internal/ide/messages.properties - Ctrl+Click on the key on line 952: IDEApplication_workspaceCannotLockTitle=Workspace Cannot Be Locked => just beeps but doesn't open the reference in IDEApplication#checkInstanceLocation(Shell). Problem is probably that the reference is in another plug-in. | resolved fixed | a3be9cc | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertyKeyHyperlink.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-14T02:48:56Z" | "2010-12-13T11:33:20Z" |
329,626 | Bug 329626 [quick assist] RFE: Quick fix to set all case statements in an Enum switch | Build Identifier: It would be nice if Eclipse would allow me to CTRL+SPACE inside a new switch statement for an Enum, and give me the option to populate all case statements for each value. And if you really want to get fancy, a dialog box where I can check/uncheck the values I desire. Reproducible: Always | resolved fixed | a292d36 | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-10T06:04:53Z" | "2010-11-07T03:20:00Z" |
327,079 | Bug 327079 [JUnit] Can't run single test with JUnit 4 launcher if there's a suite() method | I20101005-0800. Test Case: Try to run test1 from the following source with the JUnit 4 launcher. import junit.framework.Test; import junit.framework.TestCase; public class Sample extends TestCase { public void test1() { System.out.println("1"); } public static Test suite() { return null; } public void test2() { System.out.println("2"); } } | verified fixed | dd3c17d | ["org.eclipse.jdt.junit.runtime/src/org/eclipse/jdt/internal/junit/runner/junit3/JUnit3TestLoader.java", "org.eclipse.jdt.junit4.runtime/src/org/eclipse/jdt/internal/junit4/runner/JUnit4TestLoader.java", "org.eclipse.jdt.junit4.runtime/src/org/eclipse/jdt/internal/junit4/runner/JUnit4TestMethodReference.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-06T22:18:21Z" | "2010-10-06T10:13:20Z" |
267,178 | Bug 267178 [navigation] Add 'Open Super Implementation' as hyperlink | I20090304-0834 Now that we have 'Open Implementation' in most method hyperlinks, we should also offer the existing 'Navigate > Open Super Implementation' as hyperlink. 'Open Super Implementation' should be a bit smarter and not show up when we know that it will fail. Should piggyback on the override indicator calculation code. | verified fixed | 7ffc162 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementHyperlinkSuperImplementationDetector.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementSuperImplementationHyperlink.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-06T07:02:25Z" | "2009-03-05T10:46:40Z" |
331,864 | Bug 331864 [JUnit] Importing from URL should trim whitespace and skip line delimiters | HEAD Importing from URL should trim whitespace and skip line delimiters. | resolved fixed | 9df6f71 | ["org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/JUnitModel.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-05T10:44:33Z" | "2010-12-05T11:53:20Z" |
38,185 | Bug 38185 [typing] /** + Enter should do the same as "Add Javadoc" | public class X { /**<hit Enter> public static Object foo(int bar, Object baz) { return null; } } Will produce: public class X { /** * * @param bar * @param baz * @return */ public static Object foo(int bar, Object baz) { return null; } } @@@@ public class X { //comment /**<hit Enter> public static Object foo(int bar, Object baz) { return null; } } Will produce: public class X { //comment /** * */ public static Object foo(int bar, Object baz) { return null; } } | resolved fixed | f6360da | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavaDocAutoIndentStrategy.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-03T10:33:32Z" | "2003-05-28T11:06:40Z" |
258,072 | Bug 258072 [quick fix] Dead code detection quick fix leaves behind the curly braces | The quick fix for the dead code detection removes the code as well as the condition, which works in case of only 'if' block but if an 'if-else ' block is used it leaves behind the curly braces with the valid code. Try this simple test case: if (false){ x= 1; }else { x= 0; } then click on remove in the quick fix. It leaves this : { x= 0; } | resolved fixed | 53f2d6d | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-02T14:16:13Z" | "2008-12-09T13:40:00Z" |
311,603 | Bug 311603 [build path] editing user library properties drops classpath entry attributes | In the Java Persistence properties for a JPA project choose the JPA implementation type of User Library and select an appropriate library. Close and save the project properties. Right click on the library in the Project Explorer and choose 'Properties'. Select 'User Libraries...' and add/remove a jar from the user library. It can be any jar, doesn't have to be one that is needed for this library to be valid for the particular JPA platform. Now go back to the Project properties and view the Java Persistence page and you will see that the library has been unselected and there is an error. I can only get this to happen if I edit the library as described above. If you instead edit it through the Project properties 'Java Build Path' page, the JPA implementation library never gets unselected. | resolved fixed | 6aaf12f | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/UserLibraryWizardPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-01T20:31:17Z" | "2010-05-04T19:06:40Z" |
86,967 | Bug 86967 [1.5][dom] NPE in BindingKeyResolver for multi-level parameterized type binding | ASTParser.createASTs(..) cannot recreate the return type binding of HashMap#entrySet(): public Set<Map.Entry<K,V>> entrySet() ... from its binding key: Ljava/util/Map$Entry<Ljava/util/Map<TK;TV;>;:TK;Ljava/util/Map<TK;TV;>;:TV;>; Steps to reproduce: - Have this source in an editor: import java.util.HashMap; import java.util.Iterator; import java.util.Map; import java.util.Set; class A { void sets() { Map map= new HashMap(); map.put("key", new Integer(17)); Set entrySet= map.entrySet(); Iterator iter= entrySet.iterator(); Map.Entry entry= (Map.Entry) iter.next(); } } - run Refactor > Infer Generic Type Arguments..., press Preview The refactoring probably has another problem, but this bug makes it hard to debug. java.lang.NullPointerException at org.eclipse.jdt.internal.core.util.BindingKeyResolver.getTypeBinding(BindingKeyResolver.java:324) at org.eclipse.jdt.internal.core.util.BindingKeyResolver.consumeMemberType(BindingKeyResolver.java:141) at org.eclipse.jdt.internal.core.util.BindingKeyParser.parseInnerType(BindingKeyParser.java:531) at org.eclipse.jdt.internal.core.util.BindingKeyParser.parse(BindingKeyParser.java:435) at org.eclipse.jdt.internal.core.util.BindingKeyParser.parse(BindingKeyParser.java:419) at org.eclipse.jdt.internal.core.util.BindingKeyResolver.getCompilerBinding(BindingKeyResolver.java:317) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:684) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:441) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:651) at org.eclipse.jdt.internal.corext.refactoring.typeconstraints.types.TypeEnvironment.createTypeBindings(TypeEnvironment.java:104) at org.eclipse.jdt.internal.corext.refactoring.generics.InferTypeArgumentsRefactoring.rewriteConstraintVariable(InferTypeArgumentsRefactoring.java:329) at org.eclipse.jdt.internal.corext.refactoring.generics.InferTypeArgumentsRefactoring.rewriteDeclarations(InferTypeArgumentsRefactoring.java:237) at org.eclipse.jdt.internal.corext.refactoring.generics.InferTypeArgumentsRefactoring.checkFinalConditions(InferTypeArgumentsRefactoring.java:178) at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:84) at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:114) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1702) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:86) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:111) | verified fixed | 632aa86 | ["org.eclipse.jdt.ui.tests.refactoring/test", "cases/org/eclipse/jdt/ui/tests/refactoring/InferTypeArgumentsTests.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-01T18:15:06Z" | "2005-03-02T07:53:20Z" |
331,550 | Bug 331550 BreadcrumbViewer broken when Composite default size is 0,0 | null | resolved fixed | 0550036 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/breadcrumb/BreadcrumbViewer.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-12-01T15:11:09Z" | "2010-12-01T16:13:20Z" |
305,172 | Bug 305172 [common navigator] Project Explorer not fully updating with jar classpath container changes. | I found this problem while attempting to fix what appeared to a problem with the Web App Libraries classpath container defined in WTP. This container automatically automatically adds all jars residing in the project's WEB-INF/lib folder. There is also listening code which reacts to when jars are added or removed from this folder so the container is reset any time a user changes these jars. The problem I was digging into was if one of the existing jars was replaced (exact same name, but different contents), the container did not seem to update. Initially, I enhanced the listening code to catch the jar replace scenario and ensure the container was replaced (i.e calling JavaCore.setClasspathContainer with a new instance of the container), this did not fix the classpath problems. I observed the following when replacing jars handled by this container regardless of whether the container updated (i.e. I observed exactly the same behavior with and without my fixes). My testcase was to have two jars named "stuff.jar" one contained the class test.A, the other contained test.B. My Web App contained two classes, called NeedsA and NeedsB which each extended their respective classes in stuff.jar (so only one of these can actually compile at a time). Then, I simply dropped one of the stuff.jars in the WEB-INF/lib folder, and then replaced it with the other. First, the underlying JDT compile model seems to be correct. E.g. the markers view shows the correct errors or lack thereof and the package explorer's class label decorators also show those errors or lack thereof. Second, the editor's markers are stale and stay that way. Third, the contents of the classpath container's jar in the PackageExplorer when the container is expanded and the jar is expanded is also stale and stays that way. Unfortunately, there does not seem to be any workaround for the user, aside from removing and readding the container or closing and reopening the project to bring all aspects of the JDT model back in sync. JDT should treat jars added by containers exactly the same as jars added directly to the classpath (I performed the same sort of test of replacing stuff.jar when it was added directly to the classpath, and that always seemed to work). This is a major problem because an adopter built on top of WTP using this container has some tooling which generates/updates jars that reside in the WEB-INF/lib folder. | verified fixed | 661b3da | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/RefreshAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-30T18:21:54Z" | "2010-03-09T15:53:20Z" |
328,554 | Bug 328554 [move method] NPE during move method refactoring | Build Identifier: M20090917-0800 Manually (not using refactor assist) move a field F in class A to class B and this field is used by a method in class A. The method will show an error because it doesn't know . Then try to use refactor move method from class A to class B. You'll receive the error "an unhandled exception occurred while performing the refactoring." Reproducible: Always Steps to Reproduce: Manually (not using refactor assist) move a field F in class A to class B and this field is used by a method in class A. The method will show an error because it doesn't know . Then try to use refactor move method from class A to class B. You'll receive the error "an unhandled exception occurred while performing the refactoring." | resolved fixed | 9e5086c | ["org.eclipse.jdt.ui.tests.refactoring/resources/MoveInstanceMethod/canMove/test41/in/A.java", "org.eclipse.jdt.ui.tests.refactoring/resources/MoveInstanceMethod/canMove/test41/out/A.java", "org.eclipse.jdt.ui.tests.refactoring/test", "cases/org/eclipse/jdt/ui/tests/refactoring/MoveInstanceMethodTests.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInstanceMethodProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-29T18:22:05Z" | "2010-10-24T19:53:20Z" |
287,123 | Bug 287123 [quick assist] Join variable declaration quick fix should be proposed for initialized variables | The "join variable declaration" quick fix is offered for code like this: String something; something = "blah"; But it is not for initialized variables, like this: String something = null; something = "blah"; | verified fixed | 4352f71 | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-26T07:56:13Z" | "2009-08-19T22:13:20Z" |
330,241 | Bug 330241 [quick fix] 'Add unimplemented methods' adds two methods from its implementing interface when one is already there | I20101102-0800 1. Make a new Java 5 project. 2. Make one file. import java.util.List; public interface EModelService { public <T> List<T> findElements(Class<T> clazz, List<String> tagsToMatch); public <T> List<T> findPerspectiveElements(Class<T> clazz, List<String> tagsToMatch); } 3. Make another file. This one will have errors. import java.util.List; public class ModelServiceImpl implements EModelService { public <T> List<T> findElements(Class<T> clazz, List<String> tagsToMatch) { return null; } } 4. Use Ctrl+1 to ask JDT to add the unimplemented methods. 5. Now I have three methods. import java.util.List; public class ModelServiceImpl implements EModelService { public <T> List<T> findElements(Class<T> clazz, List<String> tagsToMatch) { return null; } public <T> List<T> findElements(Class<T> clazz, List<String> tagsToMatch) { // TODO Auto-generated method stub return null; } public <T> List<T> findPerspectiveElements(Class<T> clazz, List<String> tagsToMatch) { // TODO Auto-generated method stub return null; } } | resolved fixed | 83cd661 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/dom/Bindings.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-25T18:23:25Z" | "2010-11-15T14:06:40Z" |
330,754 | Bug 330754 [clean up] "Remove 'this' qualifier" erroneously removes explicit reference to containing instance within inner subclass of outer class | Build Identifier: I20100909-0800 public class Test { String label = "works"; class Nested extends Test { Nested() { label = "broken"; } @Override public String toString() { return Test.this.label; // this line gets altered by the clean up } } public static void main(String[] args) { System.out.println(new Test().new Nested()); } } This example should print "works", but this bug changes the expression `Test.this.label` to `label`, which is a different reference, and the altered program prints "broken" instead. Reproducible: Always | resolved fixed | d7de574 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/fix/CodeStyleFix.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-25T17:28:34Z" | "2010-11-21T17:20:00Z" |
331,115 | Bug 331115 Replace if-else with conditional removes comment right above if-else | If I apply the mentioned quick fix to an if-else block which has a comment above, the comment is removed. Please see the below class for an example. pre.. public class Bug { public static void main(String[] args) { boolean flag = false; String value; // this comment will be erased if ( flag ) value = "true"; else value = "false"; System.out.format("flag: %b, value: %s%n", flag, value); } } | resolved fixed | 61cde31 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-25T16:15:27Z" | "2010-11-25T13:00:00Z" |
330,680 | Bug 330680 Refactoring Signature Preview bg color is changed to default, hard to read with light syntax coloring | Build Identifier: M20100909-0800 ExtractMethodInputPage, line 314. This explicitly sets the background color of the signature preview text widget to be the same as the parent composite, which is going to the be standard gray. If the user has set up preference in such a way that they use light fg colors on top of a dark bg color for their Java syntax coloring, this makes the preview very hard to read. This particular "bug" is also in any other Refactoring action that provides a signature preview on the first page of the dialog. Reproducible: Always Steps to Reproduce: 1. Set a black bg and white fg in Preferences > General > Editors > Text Editors 2. Create a simple hello world Java file. 3. Try to Refactor > Extract Method a line of code. | resolved fixed | c1e6129 | ["org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/ChangeSignatureWizard.java", "org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/IntroduceParameterObjectWizard.java", "org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/IntroduceParameterWizard.java", "org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/code/ExtractMethodInputPage.java", "org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/code/ReplaceInvocationsInputPage.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaSourceViewer.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-25T15:29:49Z" | "2010-11-19T15:20:00Z" |
326,419 | Bug 326419 [painting] Add a performance test for the WhitespaceCharacterPainter | Add a performance test for the WhitespaceCharacterPainter. | verified fixed | 6022e56 | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/EventDrivenTestSuite.java", "org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/WhitespaceCharacterPainterTest.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-25T11:18:02Z" | "2010-09-28T13:20:00Z" |
331,053 | Bug 331053 [JUnit] Importing from URL doesn't show whether connection is working and doesn't cancel | null | resolved fixed | 6d22e66 | ["org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/JUnitModel.java", "org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/ModelMessages.java", "org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestRunHandler.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-24T19:03:21Z" | "2010-11-24T20:20:00Z" |
330,640 | Bug 330640 [preferences] SWTException in OptionsConfigurationBlock (Widget is disposed) | I got the following exception when closing the preference page for Errors/Warnings after changing the filter field. Eclipse SDK Version: 3.7.0 Build id: I20101028-1441 org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:4091) at org.eclipse.swt.SWT.error(SWT.java:4006) at org.eclipse.swt.SWT.error(SWT.java:3977) at org.eclipse.swt.widgets.Widget.error(Widget.java:468) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340) at org.eclipse.swt.widgets.Widget.getData(Widget.java:525) at org.eclipse.jdt.internal.ui.preferences.OptionsConfigurationBlock.getExpandableComposite(OptionsConfigurationBlock.java:1473) at org.eclipse.jdt.internal.ui.preferences.OptionsConfigurationBlock$FilteredPreferenceTree.updateUI(OptionsConfigurationBlock.java:628) at org.eclipse.jdt.internal.ui.preferences.OptionsConfigurationBlock$FilteredPreferenceTree.updateUI(OptionsConfigurationBlock.java:647) at org.eclipse.jdt.internal.ui.preferences.OptionsConfigurationBlock$FilteredPreferenceTree.access$2(OptionsConfigurationBlock.java:617) at org.eclipse.jdt.internal.ui.preferences.OptionsConfigurationBlock$3.runInUIThread(OptionsConfigurationBlock.java:655) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4059) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3678) 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(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:621) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:576) at org.eclipse.equinox.launcher.Main.run(Main.java:1409) | resolved fixed | a92288a | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-19T08:55:31Z" | "2010-11-19T09:46:40Z" |
329,614 | Bug 329614 [linked mode] Incorrect selection and caret position after rename in file | I20101028-1441 Steps - Select longName - Ctrl+1 > Rename in file - Rename the variable to 'name', press enter to exit linked mode - 'n' in 'name' is selected and the caret is also placed after 'n' Correct behavior: 'name' is selected and caret placed after 'name' package test1; public class E { private void foo() { int longName = 10; //select on this line longName++; longName--; --longName; ++longName; } } This works correctly with Ctrl+1 > Rename in Workspace. (Though if you notice carefully, for a split second it shows the same selection as Rename in File before it corrects itself.) | resolved fixed | 447233b | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/PropertiesFilePartitionerTest.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-18T20:23:51Z" | "2010-11-06T16:13:20Z" |
330,415 | Bug 330415 [inline] Refactor > Inline fails to parenthesize replaced arguments | Build Identifier: M20100211-1343 Inlining a subtracted expression produces the wrong result because the refactoring tool fails to parenthesize the arguments. Example: instead of x - (y + z), you can end up with x - y + z. (See attached test case). Reproducible: Always Steps to Reproduce: 1. Run the test case as-is. 2. Inline each of the functions in main(). 3. Run the test case again and observe the difference. | resolved fixed | fb1542c | ["org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_in/TestDiffDiff.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_in/TestDivideDivide.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_in/TestPlusDiff.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_in/TestTimesDivide.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_in/TestTimesTimes.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_out/TestDiffDiff.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_out/TestDivideDivide.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_out/TestPlusDiff.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_out/TestPlusPlus.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_out/TestTimesDivide.java", "org.eclipse.jdt.ui.tests.refactoring/resources/InlineMethodWorkspace/TestCases/operator_out/TestTimesTimes.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/SourceProvider.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-17T05:26:26Z" | "2010-11-16T23:26:40Z" |
317,497 | Bug 317497 [content assist] Overriding content assist suggestion immediately after closing brace generates invalid code | I20100603-1500 public class Test { public void v() { }//<-invoke CC here } Select the second option, the clone() method, and you will get... public class Test { public void v() { }protected Object clone() throws CloneNotSupportedException {};//<-invoke CC here } ...if you put a space first, you will get... public class Test { public void v() { } @Override protected Object clone() throws CloneNotSupportedException { // TODO Auto-generated method stub return super.clone(); }//<-invoke CC here } | resolved fixed | c7da83e | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/OverrideCompletionProposal.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-15T13:20:00Z" | "2010-06-21T17:06:40Z" |
149,803 | Bug 149803 [quick assist] 'exchange left and right operands' for all comparison types | Currently we have the quick fix 'exchange left and right operands for infix expression' that can be applied to == comparisons e.g., if(a == b) --> if(b == a) However, it would also be useful to have this quickfix for less-than, greater-than etc. - although obviously this is slightly more complex as it must take into account the change in the logic. I believe the following would be correct: if(a > b) --> if(b <= a) if(a >= b) --> if(b < a) if(a < b) --> if(b >= a) if(a <= b) --> if(b > a) | resolved fixed | a03dd09 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-12T04:29:29Z" | "2006-07-06T10:00:00Z" |
273,499 | Bug 273499 [quick assist] exchange operands: unavailable for infix != operator | Build ID: N20090422-2000 Steps To Reproduce: Using the code provided below in a JDT editor window: 1. Hilight the expression within the first if conditional (with == operator). 2. Open "Quick Fix" (I use Ctrl+1) 3. Note "Exchange left and right operands..." item is available and works as expected. 4. Hilight the expression within the second if conditional (with != operator). 5. Open "Quick Fix" 6. Note "Exchange left and right operands..." item is NOT available. Sample Code: Object o = new Object(); if (o == null) { } if (o != null) { } More information: I've thought about it a little (and searched for prior reported bugs on the issue) and can't think of a technical reason that exchanging operands around != would be different to doing so around ==, but there may be something I haven't thought of. For now, my workaround is to either edit manually or apply "Invert Conditions", "Exchange Operands" and "Invert Conditions" quick fixes, in that order. The first will of course convert != to == allowing Exchange Operands to be used. | resolved fixed | 1994884 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-12T04:04:51Z" | "2009-04-23T18:06:40Z" |
149,801 | Bug 149801 [quick assist] 'exchange left and right operands' incorrectly removes parentheses around logical operators | The 'exchange left and right operands for infix expression' incorrectly removes parentheses that can be necessary for the statement to evaluate correctly if it contains logical operators. e.g., private boolean isEnabled(byte[] masterBits) { return (0 == (masterBits[ENABLE_INDEX] & ENABLE_MASK)); } Applying the 'exchange left and right' operator, Eclipse removes the parantheses on the right and side and _incorrectly_ turns the method into: private boolean isEnabled(byte[] masterBits) { return (masterBits[ENABLE_INDEX] & ENABLE_MASK == 0); } This yields the Java compile error: 'The operator & is undefined for the argument type(s) byte, boolean' It should have refactored to: private boolean isEnabled(byte[] masterBits) { return ((masterBits[ENABLE_INDEX] & ENABLE_MASK) == 0); } | resolved fixed | edcd5c1 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-12T03:54:07Z" | "2006-07-06T10:00:00Z" |
170,385 | Bug 170385 [correction] Quick Fix autocomplete should remember listbox size | Build ID: 3.2.1 Steps To Reproduce: 1.Write a line of code with errors. 2.Quickfix icon will appear 3.Click the icon and a list of suggestion fixes will appear 4.Enlarge the list to read the whole text 5.Repeat this steps a second time and notice that the list still has the same size 6.This is not the case with the code complete where a resize is remembered (by default, a lot of times, the width is too small) More information: | resolved fixed | 9831bed | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/JavaSourceViewerConfiguration.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-10T15:37:22Z" | "2007-01-13T12:06:40Z" |
328,694 | Bug 328694 [call hierarchy] Clearing history should clear the status bar of the view | I20101025-1800 Steps - Open call hierarchy on a method - Call Hierarchy view > History > Clear History => the status bar at the top of the view still says "Members calling 'foo() - in workspace" This works correctly in Search view | verified fixed | f39f6e6 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-09T10:03:50Z" | "2010-10-26T13:33:20Z" |
324,237 | Bug 324237 [extract method] Extract Method refactoring fails if trailing ';' is also part of selection | I20100831-1001 ok, I have faced this too many times now... Steps: - Use this snippet and select "122;" package p; class A { int i; void foo() { this.i = 122; } } - Alt + Shift + M (Extract Method) => The end of selection contains characters that do not belong to a statement. -- bad!! Selecting the trailing ';' is very easy - I generally place the cursor right after '=' and then press Shift + End (to select till end of the line). Extract Method refactoring should simply ignore the trailing ';' instead of complaining about it. | resolved fixed | 2519762 | ["org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/expression_in/A_test623.java", "org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/expression_in/A_test624.java", "org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/expression_out/A_test623.java", "org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/expression_out/A_test624.java", "org.eclipse.jdt.ui.tests.refactoring/test", "cases/org/eclipse/jdt/ui/tests/refactoring/ExtractMethodTests.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/dom/SelectionAnalyzer.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodRefactoring.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/util/StatementAnalyzer.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-09T04:55:04Z" | "2010-09-01T19:40:00Z" |
83,061 | Bug 83061 [nls tooling] Ctrl+Click and 'Navigate > Open' should not start a search | I20050112-1200 On Ctrl+Click and 'Navigate > Open (F3)', the Properties File editor starts a lengthy search for references to the selected property key. This is a fairly unusual action, and it is confusing for the user that a seemingly quick command needs so much time when invoked in the Properties File editor. The Java Editor always jumps to the declaration of the current item, which is always a fast operation. The right command for this 'property key reference search' would be 'Search > References > Workspace'. This would also solve the problem of displaying multiple targets; the Search view is perfect for this. | verified fixed | c4e00c2 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertyKeyHyperlink.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-08T13:24:29Z" | "2005-01-18T09:20:00Z" |
81,493 | Bug 81493 [nls tooling] Properties File editor does not properly color first = or : on continuation lines | I200412162000 [nls tooling] Properties File editor does not properly color first = or : on continuation lines. In this example, all = and : characters are black, although those on continuation lines should be blue: key1= value\n\ notakey1= value2 key2: value\n\ notakey2: value2 | verified fixed | d93ed14 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertyValueScanner.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-08T13:19:16Z" | "2004-12-17T07:53:20Z" |
329,512 | Bug 329512 [formatting] invoking 'Format Element' from context menu in Java Editor | null | resolved fixed | 37f406f | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/GenerateActionGroup.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-05T11:12:57Z" | "2010-11-05T06:53:20Z" |
329,248 | Bug 329248 [ltk] "A file or folder with this name already exist" on empty input for resource rename dialog | Build Identifier: Version: 3.6.1 Build id: M20100909-0800 Inappropriate error message "A file or folder with this name already exist" appears on empty input for Resource Rename dialog. Reproducible: Always Steps to Reproduce: Steps to reproduce: 1) Create any file 2) Press F2 on it 3) Delete all text in opened "Rename Resource" dialog 4) Inappropriate error message "A file or folder with this name already exist" will appear | resolved fixed | 6a0c873 | ["org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/internal/core/refactoring/resource/RenameResourceProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-03T17:01:57Z" | "2010-11-02T12:13:20Z" |
329,252 | Bug 329252 [preferences][content assist] Auto-activation delay does not mention what unit of time it is in | Today someone on IRC mentioned that it was not clear what unit of time the 'Auto activation delay:' in the 'Java > Editor > Content Assist' preferences were in. | resolved fixed | 84cca11 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/CodeAssistAdvancedConfigurationBlock.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-11-02T13:39:52Z" | "2010-11-02T12:13:20Z" |
320,084 | Bug 320084 [hovering] NPE when hovering over @value reference within a type's Javadoc | null | resolved fixed | 343853c | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavadocContentAccess2.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-29T15:38:21Z" | "2010-07-16T08:46:40Z" |
197,969 | Bug 197969 Access Rules: The "Combine rules..." checkbox is undocumented | Build ID: I20070625-1500 Steps To Reproduce: 1.Open the Help Contents 2.Search for Combine rules 3.Notice only one hit: "Model Roadmap for Logical Model Integration" which is not about access rules. | verified fixed | 3c65230 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/IJavaHelpContextIds.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/AccessRulesDialog.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-27T15:36:09Z" | "2007-07-26T14:26:40Z" |
328,481 | Bug 328481 [quick fix] Adjust quick fixes for unused variable/field/param to improved problem detection | null | verified fixed | 89b63e6 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/fix/UnusedCodeFix.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-27T15:04:41Z" | "2010-10-22T15:06:40Z" |
86,576 | Bug 86576 [misc] invoking 'Format Source' from Outline view | Eclipse : 3.1M5a Right now to format a function, you have to highlight the function and choose 'Source --> Format' or 'Ctrl+Shift+F'. This can be cumbersome if the function is spanning more than a screenful. What would be cool is to be able to select the function in Outline view and choose 'Format'. | verified fixed | f3416bd | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/ActionMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaOutlinePage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-25T15:43:51Z" | "2005-02-25T00:06:40Z" |
88,434 | Bug 88434 [navigation] Would like to navigate to a type declaration directly | 1) Consider the following code and execute an Open Declaration at "|" CellClient c= new CellClient(); c|.bar(); 2) Open declaration selects CellClient >c<= new CellClient(); c.bar(); This is correct. However, there is no way to directly navigate to the type declaration, i.e., CellClient. It would therefore be helpul to not only have an "Open Declaration" action but also offer an "Open Type Declaration" | verified fixed | 3aefc94 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementDeclaredTypeHyperlink.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementHyperlinkDeclaredTypeDetector.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementHyperlinkReturnTypeDetector.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementReturnTypeHyperlink.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-25T14:46:12Z" | "2005-03-18T10:00:00Z" |
328,198 | Bug 328198 [nls tooling] NLSStringHover and PropertiesFileHover should not use HTMLTextPresenter | Whitespace information gets lost in NLSStringHover and PropertiesFileHover. For example a string like "This \t string \n has \t whitespace" is simply shown as "This string has whitespace" Both these hovers use DefaultInformationControl which in turn uses HTMLTextPresenter by default. | verified fixed | 8f7a578 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesFileHover.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/NLSStringHover.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavadocContentAccess2.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-22T17:18:29Z" | "2010-10-20T02:00:00Z" |
328,315 | Bug 328315 [call hierarchy] hidden view title not bold when result arrives | N20101020-2000 but probably broken since day one. The hidden view title is not bold when the result arrives. | verified fixed | 493ab1d | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-22T15:26:07Z" | "2010-10-21T05:46:40Z" |
304,135 | Bug 304135 [call hierarchy] Allow to pin Call Hierarchy | Build Identifier: I20100225-1936 After I remove some methods from the 'call hierarchy view', open another call hierarchy and then go back in history, the removed methods come back (this is quite annoying and renders the 'remove from view' functionality ineffective ). This happens because the hierarchy is computed again while going back in history. I would prefer an implementation similar to 'Search view' where the history is remembered completely (including the removed from view items) and I can hit 'F5' to search again if the results could have changed since the last search. Reproducible: Always Steps to Reproduce: Steps - Open Call hierarchy of method A - Remove some methods from the call hierarchy view - Open Call hierarchy of method B - Go back in history to view hierarchy of Method A -> the removed methods are back | verified fixed | 25f369e | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/IJavaHelpContextIds.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyUI.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/HistoryDropDownAction.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/PinCallHierarchyViewAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-22T15:00:56Z" | "2010-02-27T14:13:20Z" |
306,069 | Bug 306069 [preferences] Make new constants from bug 299514 API in PreferenceConstants | null | resolved fixed | 7a03bf8 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/JavaElementLabelsTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/AppearancePreferencePage.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/AppearanceAwareLabelProvider.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementLabelComposer.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/PreferenceConstants.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-21T10:52:48Z" | "2010-03-16T17:20:00Z" |
268,525 | Bug 268525 [nls tooling] exception in ExternalizeWizardPage.windEscapeChars() | Using Eclipse 3.5M5 While I was editing a key value, I accidentally entered '\' at the end of the key value and then clicked the mouse stopping the cell edit. The exception below occurs and key values can no longer be edited. java.lang.StringIndexOutOfBoundsException: String index out of range: 13 at java.lang.String.charAt(String.java:444) at org.eclipse.jdt.internal.ui.refactoring.nls.ExternalizeWizardPage.windEscapeChars(ExternalizeWizardPage.java:342) at org.eclipse.jdt.internal.ui.refactoring.nls.ExternalizeWizardPage.access$2(ExternalizeWizardPage.java:331) at org.eclipse.jdt.internal.ui.refactoring.nls.ExternalizeWizardPage$CellModifier.modify(ExternalizeWizardPage.java:194) at org.eclipse.jface.viewers.ColumnViewer$2.setValue(ColumnViewer.java:274) at org.eclipse.jface.viewers.EditingSupport.saveCellEditorValue(EditingSupport.java:113) at org.eclipse.jface.viewers.ColumnViewerEditor.saveEditorValue(ColumnViewerEditor.java:454) at org.eclipse.jface.viewers.ColumnViewerEditor.applyEditorValue(ColumnViewerEditor.java:311) at org.eclipse.jface.viewers.ColumnViewerEditor.handleEditorActivationEvent(ColumnViewerEditor.java:438) at org.eclipse.jface.viewers.ColumnViewer.triggerEditorActivationEvent(ColumnViewer.java:680) at org.eclipse.jface.viewers.ColumnViewer.handleMouseDown(ColumnViewer.java:664) at org.eclipse.jface.viewers.ColumnViewer.access$0(ColumnViewer.java:660) at org.eclipse.jface.viewers.ColumnViewer$1.mouseDown(ColumnViewer.java:89) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:179) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3875) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3470) | verified fixed | 9639a87 | ["org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/ExternalizeWizardPage.java", "org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/NLSUIMessages.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-15T10:22:05Z" | "2009-03-13T13:13:20Z" |
313,313 | Bug 313313 [implementation][preferences][spell checking] Move disabling of spelling for performance tests into tests itself | R3.3. We should move the code that disables spelling for performance tests from AbstractDecoratedTextEditorPreferenceConstants into tests itself. Currently, when running the performance tests on a local machine we get different results than on the official/releng test machines. | verified fixed | b2cb105 | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/FileBufferPerformanceTest.java", "org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/OpenPreferencePageTest.java", "org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/TextPerformanceTestCase.java", "org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/performance/TextPerformanceTestCase2.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-11T15:31:27Z" | "2010-05-18T10:53:20Z" |
139,215 | Bug 139215 [5.0][syntax highlighting] "</code>" after @ not rendered correctly in Javadoc | 3.2 RC2 candidate The <code>@BeforeClass</code> comment in the Javadoc below is not correctly rendered: /** * A <code>Failure</code> holds a description of the failed test and the * exception that was thrown while running it. In most cases the <code>Description</code> * will be of a single test. However, if problems are encountered while constructing the * test (for example, if a <code>@BeforeClass</code> method is not static), it may describe * something other than a single test. */ Seems like the @something is causing troubles | resolved fixed | 2437eed | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavaDocScanner.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-10-05T14:15:11Z" | "2006-04-28T16:00:00Z" |
326,116 | Bug 326116 [preferences] Add UI for new compiler warning option org.eclipse.jdt.core.compiler.problem.suppressNullInfoFromAsserts | null | resolved fixed | 483a951 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ProblemSeveritiesConfigurationBlock.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-30T14:33:32Z" | "2010-09-24T06:33:20Z" |
326,377 | Bug 326377 [content assist] Content assist for abstract class instantiation adds semicolon at wrong place | I20100915-2024 Given: public class E02 { public static abstract class Bar { public abstract void doBar(); } public void foo() { addBar(new Bar|) } public void addBar(Bar bar) { } } 1. Cursor where the '|' is 2. Control space 3. Select E02.Bar proposal IS: addBar(new Bar() { @Override public void doBar() { } };) Should: addBar(new Bar() { @Override public void doBar() { } }); I think this might be a regression: I've never had that before. | resolved fixed | a6f01e9 | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-28T14:43:40Z" | "2010-09-28T07:46:40Z" |
99,540 | Bug 99540 [javadoc export] javadoc: locale argument must come first | To reproduce: Project -> Generate Javadoc -> Next -> Next ... Now in the "Extra Javadoc options" put "-locale jp". Click Finish. Javadoc complains that the "option -locale must be first on the command line," although in fact it is the only argument. | resolved fixed | a3ad6ce | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocOptionsManager.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-28T09:37:09Z" | "2005-06-12T18:13:20Z" |
41,092 | Bug 41092 [navigation] provide 'Collapse All' action in Java Outline view | This would be quite valuable for classes with inner/nested classes. | verified fixed | 949a314 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaOutlinePage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-23T11:46:15Z" | "2003-08-04T09:40:00Z" |
325,982 | Bug 325982 [JUnit] Name of the test is not updated in the "Result Comparison" dialog | Build Identifier: 3.6 Helios The name which is set when the "Result Comparison" dialog is opened is never updated. It should update when a new test is selected and the content of the view is updated. Reproducible: Always Steps to Reproduce: 1. Run a test suite where several tests fail 2. Open the "Result Comparison" dialog for one 3. Select a different test The content of the dialog changes but the test name below the title bar stays the same. | verified fixed | aa6177b | ["org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/CompareResultDialog.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-23T06:52:52Z" | "2010-09-22T15:40:00Z" |
325,195 | Bug 325195 [clean up] Write test for bug 322543 (Stops working after 100 problems in one CU) | null | verified fixed | 24c78f8 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-22T11:05:42Z" | "2010-09-14T07:40:00Z" |
325,812 | Bug 325812 [type hierarchy] Open Type Hierarchy should work for selection of more than one logical packages | OTH should be enabled for multi-selection of logical packages since we support TH for all type containers. | verified fixed | 0296584 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenTypeHierarchyAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-21T06:22:52Z" | "2010-09-21T06:20:00Z" |
325,258 | Bug 325258 [type hierarchy] Improve label rendering in Type Hierarchy | null | verified fixed | 0916546 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyLifeCycle.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenTypeHierarchyAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-21T05:35:28Z" | "2010-09-14T13:13:20Z" |
325,694 | Bug 325694 [call hierarchy] Delete key should remove element from view instead of deleting it | Call hierarchy could be extended in the way that it's behavior matches the "standart" behavior of the search view. 1) "Delete" action deletes the Java element from the *code*. This is VERY inconvenient. Expected: as in the Search view, the *search result* is removed from view. Additionally, "del" keybinding should be used by the "remove from view" context menu. 2) There is no way to open multiple call hierarchies at same time. Expected: as in the Search view, "Pin this view" button should be available at the view toolbar. | verified fixed | 09dddb5 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/CCPActionGroup.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-20T13:05:14Z" | "2010-09-19T09:53:20Z" |
325,523 | Bug 325523 NPE when deleting resource | 3.7M2 test build - observed on Linux-motif, but presumably affects other platforms as well I could not find reproducable steps for this, but I'm pretty sure it happened while either dragging a resource within the Package Explorer, or deleting a resource there by pressing Delete. The stack follows. java.lang.NullPointerException 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.ltk.internal.ui.refactoring.actions.DeleteResourcesHandler.execute(DeleteResourcesHandler.java:40) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) 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.executeCommandInContext(HandlerService.java:270) at org.eclipse.ui.internal.ide.actions.LTKLauncher.runCommand(LTKLauncher.java:95) at org.eclipse.ui.internal.ide.actions.LTKLauncher.openDeleteWizard(LTKLauncher.java:47) at org.eclipse.ui.actions.DeleteResourceAction.run(DeleteResourceAction.java:481) at org.eclipse.jdt.internal.ui.refactoring.reorg.DeleteAction.run(DeleteAction.java:162) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java: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:929) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3224) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2895) 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:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:621) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:576) at org.eclipse.equinox.launcher.Main.run(Main.java:1409) | resolved fixed | 8df659c | ["org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/RefactoringWizardOpenOperation.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-17T07:03:38Z" | "2010-09-16T20:46:40Z" |
67,412 | Bug 67412 F1 help missing | null | verified fixed | 163a565 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/IJavaHelpContextIds.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/CopyQualifiedNameAction.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ShowInBreadcrumbAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-15T21:33:04Z" | "2004-06-16T07:13:20Z" |
325,221 | Bug 325221 [preferences] Add examples for new FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_* constants | HEAD A few of the new options for FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_* constants do not have examples showing in the preview pane: 1) Insert new lines after annotations on fields 2) Insert new lines after annotations on types | verified fixed | 42194e3 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/NewLinesTabPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-15T10:06:58Z" | "2010-09-14T10:26:40Z" |
21,417 | Bug 21417 [type hierarchy] Multi-select java elements and show in Type Hierarchy | F4 can be used for showing a package (or project) in the type hierarchy view. It would be nice if we could multi select packages and open in the type hierarchy view using F4. The use case is that I have a project with 2 source folders and some JARs in the classpath. If I use F4 on the project, the hierarchy view also shows the types in the JARs. What I'd like to have is only the types in my 2 source folders. | verified fixed | 4db882a | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/ActionMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/HierarchyLabelProvider.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/HistoryAction.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/HistoryDropDownAction.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/HistoryListAction.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyContentProvider.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyLifeCycle.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TypeHierarchyViewPart.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/util/OpenTypeHierarchyUtil.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenTypeHierarchyAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-13T19:41:04Z" | "2002-07-09T18:40:00Z" |
324,719 | Bug 324719 NPE in context help in Java Editor when CU not on build path | - Open an external java file - Focus in the Java editor - Press F1 java.lang.NullPointerException at org.eclipse.jdt.internal.ui.actions.ActionUtil.isOnBuildPath(ActionUtil.java:93) at org.eclipse.jdt.internal.ui.util.JavaUIHelp$JavaUIHelpListener.helpRequested(JavaUIHelp.java:99) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:147) 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:621) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:576) at org.eclipse.equinox.launcher.Main.run(Main.java:1409) at org.eclipse.equinox.launcher.Main.main(Main.java:1385) | resolved fixed | c39b372 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/util/JavaUIHelp.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-13T12:02:06Z" | "2010-09-08T10:00:00Z" |
324,995 | Bug 324995 [preferences] New formatter profile version must not automatically touch existing projects | null | verified fixed | 67d25b7 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/FormatterProfileStore.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-10T17:17:09Z" | "2010-09-10T17:33:20Z" |
318,010 | Bug 318010 [preferences] Add options for new FORMATTER_INSERT_NEW_LINE_AFTER_ANNOTATION_ON_* constants | null | verified fixed | 92e0e43 | ["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/NewLinesTabPage.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/ProfileVersioner.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-10T16:52:44Z" | "2010-06-25T15:33:20Z" |
323,690 | Bug 323690 [call hierarchy] Refresh view when selection is empty | Build Identifier: 20100617-1415 If I open the call hierarchy for a given method by placing the caret on the method and then pressing Ctrl+Alt+H, it can still happen, that the resulting tree is empty. In Eclipse 3.5 I could then simply press F5 3 or 4 times to refresh the tree until it show the actual result. Now in 3.6 the call hierarchy refreshes only, if it is non-empty. Pressing Ctrl+Alt+H again after the call hierarchy opened and the selection is on the requested method does it though. But F5 should also work, since I don'T have to worry about the selection then. Reproducible: Always | verified fixed | b2aa7e8 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyViewPart.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/RefreshElementAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-09T14:46:03Z" | "2010-08-26T10:53:20Z" |
324,769 | Bug 324769 Adopt new APIs on ILocalVariable | null | resolved fixed | a1f93bd | ["org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/util/JavaModelUtil.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameTypeProcessor.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementImageProvider.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementLabelComposer.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementLinks.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-08T17:11:41Z" | "2010-09-08T18:20:00Z" |
324,285 | Bug 324285 [JUnit] RemoteTestRunnerClient destroys line delimiters | 3.6 and HEAD. It took me quite a while to figure out why some of my tests failed until I noticed that the only difference were in the line delimiters. Test Case: 1. paste this source: --- %< --- import junit.framework.TestCase; public class C extends TestCase { public void test1() { String s1= "a\nb"; String s2= "a\r\nb"; assertEquals(s2, s1); } } --- %< --- 2. fix build path 3. run it as JUnit Test 4. compare the failing string result ==> no diffs found and different line delimiters are not visible. JUnit delivers the correct results but the reader in RemoteTestRunnerClient hard-codes the line delimiters to '\n'. | verified fixed | bdf5278 | ["org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/RemoteTestRunnerClient.java", "org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestRunSession.java", "org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/junit/tests/AbstractTestRunSessionSerializationTests.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-08T11:14:59Z" | "2010-09-02T09:33:20Z" |
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. | verified fixed | b04c07e | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-08T08:39:37Z" | "2010-05-24T08:33:20Z" |
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. | verified fixed | 3760f57 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ConvertNestedToTopAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-08T08:33:35Z" | "2010-05-24T08:33:20Z" |
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. | verified fixed | 71c3148 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/SelfEncapsulateFieldAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-06T14:01:45Z" | "2010-05-24T08:33:20Z" |
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) | verified fixed | 03c14c3 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/IntroduceParameterObjectAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-06T13:11:36Z" | "2010-05-24T08:33:20Z" |
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) | verified fixed | 1521bfe | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-06T12:07:24Z" | "2010-05-24T08:33:20Z" |
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) | verified fixed | 84c9229 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/IntroduceIndirectionAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-06T11:14:07Z" | "2006-04-28T16:00:00Z" |
305,255 | Bug 305255 [preferences] Accept jsr14 as a build target | null | resolved fixed | e5acb8c | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ComplianceConfigurationBlock.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-04T10:57:51Z" | "2010-03-09T21:26:40Z" |
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) { } } | resolved fixed | c6c3bc1 | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-03T14:52:01Z" | "2010-09-03T13:20:00Z" |
324,391 | Bug 324391 [content assist] Still too many semicolons after constructor completion | null | verified fixed | 364e3a3 | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-03T13:02:31Z" | "2010-09-03T10:33:20Z" |
319,532 | Bug 319532 [preference][typing] Allow to disable smart auto-indent on return | null | verified fixed | 19a57eb | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-03T09:23:02Z" | "2010-07-12T10:20:00Z" |
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 | verified fixed | 346ddb8 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaMethodCompletionProposal.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-02T14:51:37Z" | "2009-12-22T19:26:40Z" |
287,374 | Bug 287374 [extract method] Allows extracting lhs of full qualified expression | null | resolved fixed | aad3069 | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-09-01T17:35:41Z" | "2009-08-23T12:20:00Z" |
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. | verified fixed | 8252280 | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-08-31T05:57:00Z" | "2010-08-12T13:33:20Z" |
261,498 | Bug 261498 [spell checking] Locales without country code don't work. | null | verified fixed | 41e3642 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/spelling/SpellCheckEngine.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-08-30T14:34:07Z" | "2009-01-19T13:00:00Z" |
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>" | resolved fixed | 2eeef51 | ["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 | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-08-27T17:29:37Z" | "2010-05-07T08:13:20Z" |
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. | verified fixed | fc088b4 | ["org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceParameterRefactoring.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-08-25T10:24:03Z" | "2010-08-11T09:46:40Z" |
323,134 | Bug 323134 [JUnit] JUnit view loses several action states on restart | null | verified fixed | 7748890 | ["org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitCorePlugin.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2010-08-23T13:40:28Z" | "2010-08-19T12:13:20Z" |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.