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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
367,629 | Bug 367629 [hovering] JavaDoc-Navigation broken if there are spaces in the URL | If the JavaDoc location e.g. on the local file system has spaces in it navigating to internal links is broken. Not sure if this once more a problem of the browser control which should have escaped such spaces with "%20" or this is the task of the handler. Here's the relevant stacktrace: !ENTRY org.eclipse.jdt.ui 4 10001 2011-12-29 15:56:37.740 !MESSAGE Internal Error !STACK 0 java.net.URISyntaxException: Illegal character in path at index 17: file://C:/Program Files (x86)/Oracle/JavaFX 2.0 SDK/docs/api/javafx/scene/layout/Region.html at java.net.URI$Parser.fail(URI.java:2809) at java.net.URI$Parser.checkChars(URI.java:2982) at java.net.URI$Parser.parseHierarchical(URI.java:3066) at java.net.URI$Parser.parse(URI.java:3014) at java.net.URI.<init>(URI.java:578) at org.eclipse.jdt.internal.ui.viewsupport.JavaElementLinks$1.changing(JavaElementLinks.java:222) at org.eclipse.swt.browser.IE$7.handleEvent(IE.java:499) at org.eclipse.swt.ole.win32.OleEventTable.sendEvent(OleEventTable.java:55) at org.eclipse.swt.ole.win32.OleEventSink.notifyListener(OleEventSink.java:145) at org.eclipse.swt.ole.win32.OleEventSink.Invoke(OleEventSink.java:120) at org.eclipse.swt.ole.win32.OleEventSink.access$1(OleEventSink.java:97) at org.eclipse.swt.ole.win32.OleEventSink$1.method6(OleEventSink.java:71) at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2545) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:977) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:893) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:91) at org.eclipse.ui.internal.Workbench$3.run(Workbench.java:565) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:520) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) 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:352) 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:624) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:579) at org.eclipse.equinox.launcher.Main.run(Main.java:1433) at org.eclipse.equinox.launcher.Main.main(Main.java:1409) | verified fixed | c3eb737 | ["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 | "2012-05-15T13:23:19Z" | "2011-12-29T14:46:40Z" |
378,337 | Bug 378337 [quick fix] improve description for adding library with default null annotations to a bundle | I20120502-2000. We should improve the description for adding library with default null annotations to a bundle. Currently it's a bit confusing because it talks about the build.properties file only. | verified fixed | 3a8080a | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/UnresolvedElementsSubProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-05-14T11:57:13Z" | "2012-05-03T10:13:20Z" |
378,989 | Bug 378989 Unused method in NullQuickFixes | The method isMissingNullAnnotationProblem(int) from the type NullQuickFixes is never used locally Deepak, OK to remove the method? | verified fixed | 12193ba | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/NullQuickFixes.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-05-11T14:12:13Z" | "2012-05-09T13:26:40Z" |
377,474 | Bug 377474 [nls tooling][DBCS4.2] Unescape and escape backslash for properties file not working properly for DBCS characters. | Build Identifier: I20120321 JRE: IBM 7 JRE OS: Windows 7, AIX 7.1 (Both, Japanese, SJIS) Reproducible: Always Steps to Reproduce: 1.Create a properties file eg. example.properties in Java project. 2. Add following line k=c:\\program 3. The DBCS characters will be automatically transformed to unicode equivalent characters into the following, k=c:\\u3077\u308D\u3050\u3089\u3080\program 4. Press ctrl+1 and click escape. 5. Expected result, The backslash in front of unicode characters should not be escaped. Actual result Even the backslash in front of unicode characters are escaped, giving the following. k=c:\\\\u3077\\u308D\\u3050\\u3089\\u3080\\program This when read from Java as property file will be interpreted as c:\\u30D7\u30ED\u30B0\u30E9\u30E0\program Instead of original c:\\program | verified fixed | 802ed4d | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/EscapeBackslashCompletionProposal.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesFileAutoEditStrategy.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesFileEditorMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-05-10T14:31:43Z" | "2012-04-24T09:33:20Z" |
379,086 | Bug 379086 [quick fix] Quick fix to add the missing cases of a switch on enum is not being proposed | ### package p1; public class UseEnum { public void foo(DeclEnum e) { switch(bar()) { case C1: break; } } public DeclEnum bar() { return null; } } enum DeclEnum { C1, C2, C3; } ### With the above example, notice the warning on switch(bar()). Quick fix to add the missing cases is not being proposed. It is proposed if 'switch(e)' is used. | verified fixed | 0d9287b | ["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 | "2012-05-10T09:13:28Z" | "2012-05-10T08:53:20Z" |
378,619 | Bug 378619 [hovering] Hovering on closing bracket shows incorrect block in switch statements | null | verified fixed | 6df8a30 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavaSourceHover.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-05-09T11:10:33Z" | "2012-05-07T05:53:20Z" |
378,258 | Bug 378258 [hovering] F2 hover shows variable name instead of rich variable value hover | Set a breakpoint and then debug this: public class Try { static int fValue= 42; public static void main(String[] args) { System.out.println("hi " + fValue); } } Hovering over 'fValue' or 'out' shows the variable value hover, but F2 shows shows the variable name. | verified fixed | 862f59d | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/BestMatchHover.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavaInformationProvider.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-05-02T19:04:21Z" | "2012-05-02T14:46:40Z" |
378,149 | Bug 378149 [quick fix] Also add imports when invoking 'Copy 'org.eclipse.jdt.annotation.jar' to build path' | I20120430-2000. Like the quick fix that adds JUnit, we should also add the imports, so that the we don't have any errors after invoking the quick fix. Test Case: class A { public @NonNull Object foo(@Nullable Object input) { return this; } } class B extends A { } | verified fixed | 31910b7 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/UnresolvedElementsSubProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-05-02T17:56:59Z" | "2012-05-01T11:00:00Z" |
378,068 | Bug 378068 Update ImportOrganizeTest (FUP of bug 376734 and bug 376930) | null | resolved fixed | 31bc2c1 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/ImportOrganizeTest.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-05-02T11:08:36Z" | "2012-04-30T12:46:40Z" |
181,788 | Bug 181788 [quick fix] Quick fix to import static from favorite class | In 3.3M6 The content assist to import a static member from one of several favorite classes is a godsend. I'd like to extend it to work the same as instance methods in the class--not only would static members from favorite classes be available for content assist, but also as quick fixes. So if I type sin(3) And Math.* is in my favorites, a quick fix on the error would include the option to import static Math.sin. | verified fixed | f0a9341 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedMethodsQuickFixTest.java", "org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedVariablesQuickFixTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/SimilarElementsRequestor.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/UnresolvedElementsSubProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-29T14:24:12Z" | "2007-04-10T15:46:40Z" |
372,516 | Bug 372516 [syntax highlighting] bracket highlighting should also work if caret is after the last bracket | null | resolved fixed | d296fed | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JavaPairMatcherTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaPairMatcher.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-27T08:18:12Z" | "2012-02-24T16:13:20Z" |
377,445 | Bug 377445 [content assist] Code complete is vague when multiple Options exist for Enum member type on annotation | Build Identifier: Assuming JPA annotation javax.persistence.OneToMany If defining the cascade member on the annotation and the CascadeType is not already imported I am presented with 3 different CascadeType which provide no detail as to which is which. javax.persistence.CascadeType org.hibernate.annotations.CascadeType org.hibernate.metamodel.binding.CascadeType I think the package name should be provided so that you can see which option you want to select and or limit to javax.persistence.CascadeType which is the only acceptable type for member cascade on javax.persistence.OneToMany Reproducible: Always Steps to Reproduce: 1. Add Annotation 2. Add member 3. See complete options | resolved fixed | f443721 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/CompletionProposalLabelProvider.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-24T10:02:48Z" | "2012-04-23T19:40:00Z" |
335,132 | Bug 335132 [actions] Override / Implement dialog size / position are not saved | Build Identifier: 20100917-0705 The size and position of "override/implement method" dialog box is not saved. If I make the dialog larger to see more methods at once (I have a large monitor), then on subsequent invocations the dialog resets to default size / position. Reproducible: Always Steps to Reproduce: 1. Bring up override/implement method dialog. 2. Resize the dialog, e.g. make it larger. 3. Finish by overriding a method (clicking "Ok) 4. Bring up the dialog again. ---> The dialog has the old, default size - its size and position are not saved. | resolved fixed | 3161739 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/SourceActionDialog.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-23T12:12:11Z" | "2011-01-23T19:13:20Z" |
377,393 | Bug 377393 [content assist] Remove final modifier from several JavaCompletionProposal subclasses | To make subwords completion work for almost all standard completions, I had to copy the following classes because they have a final modifier: org.eclipse.jdt.internal.ui.text.java.FilledArgumentNamesMethodProposal org.eclipse.jdt.internal.ui.text.java.LazyGenericTypeProposal org.eclipse.jdt.internal.ui.text.java.ParameterGuessingProposal Is is possible to remove the final modifier from these classes? It would be nice if this change can make it into Juno release; it would make our codebase a bit cleaner for 3.9. | resolved fixed | 4df8e6f | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/FilledArgumentNamesMethodProposal.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/LazyGenericTypeProposal.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ParameterGuessingProposal.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavadocInlineTagCompletionProposal.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavadocLinkTypeCompletionProposal.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-23T11:35:57Z" | "2012-04-23T11:20:00Z" |
377,184 | Bug 377184 [content assist] Override method proposal does not format in subclass with type parameter | Override method proposal does not format the resulting method in cases where a subclass has a type parameter and forwards it to the superclass. Example: package bug; class Super<T> { void foo(T t) { } } public class Impl<T2 extends Number> extends Super<T2> { foo } Result: void foo(T2 t) {}; Problem is a bad subsignature implementation in Bindings#isEqualMethod(IMethodBinding, String, String[]) | resolved fixed | b767faa | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/CodeCompletionTest.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 | "2012-04-19T13:32:20Z" | "2012-04-19T12:53:20Z" |
353,126 | Bug 353126 improve StubCreator | null | resolved fixed | 910a3b6 | ["org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/binary/StubCreator.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-16T18:11:07Z" | "2011-07-26T14:20:00Z" |
243,912 | Bug 243912 IProject#delete(..) should suppress deltas from CharsetDeltaJob | null | resolved fixed | 774fcb6 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/browsing/PackagesViewContentProviderTests2.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-16T18:07:22Z" | "2008-08-12T16:53:20Z" |
352,785 | Bug 352785 [extract method] Refactor > Extract Method with break statement in switch causes NPE | Build Identifier: 20110615-0604 If I attempt to Refactor > Extract Method which includes a break statement inside a switch, an unexpected exception occurs, which is an NPE (will attach stack later). It should give an error which says something like you can't refactor a method which includes multiple exit points, or something like that. Reproducible: Always Steps to Reproduce: 1. Write some code: public void foo(int i) { switch (i) { case 1: if (true) { break; } } } 2. Highlight the some code within the case 1 statement. 3. Choose Refactor > Extract Method | resolved fixed | 75fd0aa | ["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 | "2012-04-16T18:03:26Z" | "2011-07-21T17:40:00Z" |
130,922 | Bug 130922 [quick assist] 'Assign parameter to new field' must not make field final' | I20060307-1315 package xy; public class Try{ public Try(String arg) { } public Try() { } } Quick assist on 'arg' to assign to a new field -> field is final, yielding a compile error -> expected: field not final as it was in earlier builds | resolved fixed | e116450 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AssistQuickFixTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/saveparticipant/AbstractSaveParticipantPreferenceConfiguration.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/AssignToVariableAssistProposal.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-16T17:49:58Z" | "2006-03-08T15:00:00Z" |
335,249 | Bug 335249 [preferences] Improve grouping of "Potential programming problems" on Errors/Warnings page | Improve grouping of options on Errors/Warnings page. "Potential programming problems" is too big and without logical order. It could be split into options that affect - members (method signatures, serial id) - expressions - statements and blocks Or we could just order them by scope. | resolved fixed | e8e5356 | ["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 | "2012-04-16T16:25:19Z" | "2011-01-24T20:13:20Z" |
357,997 | Bug 357997 [type hierarchy] Type Hierarchy View has button bar painting issues on workspace startup | Build Identifier: 20110615-0604 My workspace has type hierarchy active on my Workspace on startup. I believe that View is responsible for leaving an unpainted, gray modeless floating rectangle over or under other parts of UI. If I horizontally expand and collapse the column that the type hierarchy is in, I can get the rectangle to be clearly visible. If I collapse the column enough, I can get the rectangle to disappear, and briefly I catch that the rectangle is actually the Type Hierarchy button bar, just unpainted. (The buttons appear for one frame before the bar disappears.) While the button bar is unpainted, it does not respond to mouse clicks or drags. The button bar I am referring to contains the "Show the Type Hierarchy", "Show the Supertype Hierarchy", "Show the Subtype Hierarchy", and "Previous Type Hierarchies" buttons. Reproducible: Always Steps to Reproduce: 1. Start Eclipse 2. Expand/collapse the Type Hierarchy view horizontally 3. View the modeless rectangle occlude other parts of the UI | resolved fixed | 8f53a99 | ["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 | "2012-04-16T15:40:16Z" | "2011-09-17T03:26:40Z" |
86,168 | Bug 86168 [type wizards] Allow the creation of a compilation unit called package-info.java | null | verified fixed | 9111b35 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewPackageCreationWizard.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewWizardMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewPackageWizardPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-16T15:13:38Z" | "2005-02-22T16:33:20Z" |
373,885 | Bug 373885 [jar exporter] save runnable jar export as ant script with relative name saves in eclipse program folder not workspace | Build Identifier: Version: Indigo Service Release 2 Build id: 20120216-1857 When saving settings for producing a runnable jar file as an ant script, if you enter a relative filename in the filename box, a message appears suggesting that this will be relative to the workspace root. However, when the file is actually saved, it is saved relative to the directory eclipse is installed in. Reproducible: Always Steps to Reproduce: 1. export > runnable jar file 2. check 'save as ant script' 3. enter a relative path (e.g. 'myproject/exportjar.xml') in the filename box 4. click finish the file is not produced in the myproject directory of the workspace, but in a new subdirectory of the eclipse program directory. | resolved fixed | e2a5dd8 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/FatJarPackageWizardPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-16T14:35:21Z" | "2012-03-11T12:46:40Z" |
376,779 | Bug 376779 [navigation] JavaElementHyperlinkDetector#detectHyperlinks(..) is wasting time | Navigation via Ctrl+Hyperlinks is very slow in medium-sized classes, e.g. LocalCorrectionsSubProcessor. When I hold Ctrl and move the mouse, I see update times of almost a second. Most of the time is wasted in repeated calls to JavaElementHyperlinkDetector#detectHyperlinks(..). The two major factors are: 1. All 4 subclasses of JavaElementHyperlinkDetector perform ICodeAssist#codeSelect(..) again on the same element. 2. ICodeAssist#codeSelect(..) is already quite slow, since it often has to compile large parts of the AST and resolve many bindings (I think not using star imports adds to this). We should consider adding a wrapper around calls to codeSelect and first see if we already have a shared AST available for free. If we find a SimpleName without recovered/malformed parents, we should just use resolveBinding().getJavaElement() and keep codeSelect as a fallback. | resolved fixed | 41549d5 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaElementHyperlinkDetector.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-13T20:49:13Z" | "2012-04-13T20:46:40Z" |
376,688 | Bug 376688 [type wizards] New class wizard doesn't remember setting for which method stubs to create | Build Identifier: 3.8.0 I20120314-1800 Which checkboxes are selected in "Which method stubs would you like to create?" is not remembered across invocations of the new class wizard although NewPackageWizardPage tries to save them. The problem seems to be that NewPackageWizardPage#setVisible(false) is never invoked because WizardDialog#finishPressed() sends #hardClose() Reproducible: Always Steps to Reproduce: 1. Invoke the New Class wizard 2. Check "public static void main(String[] args)" 3. Uncheck "Constructors from superclass" 4. Uncheck "Inherited abstract methods" 5. Create the class 6. Invoke the New Class wizard again Expected result: Which method stubs would you like to create? [x] public static void main(String[] args) [ ] Constructors from superclass [ ] Inherited abstract methods Actual result: Which method stubs would you like to create? [ ] public static void main(String[] args) [ ] Constructors from superclass [x] Inherited abstract methods | resolved fixed | 069fa7c | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewClassCreationWizard.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewClassWizardPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-13T08:25:22Z" | "2012-04-13T06:53:20Z" |
353,472 | Bug 353472 [override method] generating a method override should copy annotations | null | verified fixed | ccad5c0 | ["org.eclipse.jdt.ui.tests.refactoring/resources/PushDown/test30/out/A.java", "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/codemanipulation/StubUtility2.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/dom/ASTNodeFactory.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/ExtractInterfaceProcessor.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/HierarchyProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-10T18:33:02Z" | "2011-07-31T19:20:00Z" |
376,381 | Bug 376381 [preferences][clean up] ICleanUpConfigurationUI parent Composite has excess margins | Build Identifier: Version: Indigo Service Release 2 Build id: 20120216-1857 ContributedCleanUpTabPage.doCreatePreferences(...) creates a Composite to pass into fContribution.createContents(parent). This composite is setup with a GridData and GridLayout as follows: final Composite parent= new Composite(composite, SWT.NONE); GridData layoutData= new GridData(SWT.FILL, SWT.FILL, true, true); layoutData.horizontalSpan= numColumns; parent.setLayoutData(layoutData); parent.setLayout(new GridLayout(1, false)); This results in adding extra margin around UI within contributed tabs. To work around this I have to use the following code at the start of my createContents(...) method: // Fix parent layout which added some extra margin GridLayout parentLayout = new GridLayout(); parentLayout.marginHeight = 0; parentLayout.marginWidth = 0; parent.setLayout(parentLayout); Reproducible: Always Steps to Reproduce: 1. Implement ICleanUpConfigurationUI. 2. Create some UI within the createContents(...) method. 3. Resulting UI has extra margin compared to the existing UI tabs. | resolved fixed | 313ed85 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/ContributedCleanUpTabPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-10T10:59:00Z" | "2012-04-10T09:26:40Z" |
374,111 | Bug 374111 [common navigator][package explorer] problem marker on package should not be repeated on parent package | null | verified fixed | d8af25b | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/ProblemsLabelDecorator.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-02T14:14:04Z" | "2012-03-13T17:33:20Z" |
348,368 | Bug 348368 [syntax highlighting] Add highlight for inherited fields | Please add support to highlight inherited fields. Example: class A { ... protected int a; protected int x; ... } class B extends A { ... protected int b; void isntThatCoolIfSomeoneOverridesA() { a = b; x = b * b; } ... } In the example, "a" and "x" should be highlighted using a special "inherited field" style. | resolved fixed | cfd27e2 | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/SemanticHighlightingTest.java", "org.eclipse.jdt.text.tests/testResources/semanticHighlightingTest1/SHTest.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 | "2012-04-02T13:33:19Z" | "2011-06-06T08:46:40Z" |
374,689 | Bug 374689 [search] Difficult to Select Limit To options in Search dialog with keyboard | 1. Open the search dialog (Ctrl+H). 2. Tab through the items until you reach the Limit To area (you mush search for either Type or Method). 3. The "Match locations" is in a different grouping from the other radio buttons, so when selecting one of the first few options then tabbing forward leads to the selection being lost and Match locations being selected. This makes it difficult to select any of the other options, though you could Shift+Tab backwards through the entire dialog after selecting a option, but that's not a very nice experience. | resolved fixed | 32bb5a8 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/JavaSearchPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-04-02T13:00:46Z" | "2012-03-19T18:00:00Z" |
347,587 | Bug 347587 [package explorer] Empty parent packages are not filtered correctly if they contain .svn folder | Build Identifier: 20110218-0911 org | `-.svn (filtered) org.test | `-.svn (filtered) The filter "Empty parent packages" does not hide a parent package if it contains filtered .svn ressource folders. So logically they are empty but the filter does not think that. Reproducible: Always Steps to Reproduce: 1. Check out a project from svn in Windows 7 with TortoriseSVN 2. Import the project in eclipse (without using subclipse or subversive etc.) 3. Enable the .ressources and empty parent packages filters | resolved fixed | 2c2a9da | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/filters/EmptyInnerPackageFilter.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/filters/EmptyPackageFilter.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-30T10:32:45Z" | "2011-05-29T20:13:20Z" |
353,221 | Bug 353221 [correction][quick fix] Should jump to closest problem even if there's a breakpoint | BETA_JAVA7, same in 3.6.2 package xy; public class Try { void foo() { equals(); // add breakpoint } } - add a line breakpoint to indicated line - put caret at end of line - Ctrl+1 => expected: Caret should jump to error position => was: Caret stays at end, no quick fix offered | resolved fixed | 3c68065 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/JavaCorrectionAssistant.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-26T15:57:11Z" | "2011-07-27T15:20:00Z" |
351,181 | Bug 351181 [hovering] Javadoc hover should have default modifier set | null | resolved fixed | de881c0 | ["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 | "2012-03-22T13:45:09Z" | "2011-07-05T12:46:40Z" |
355,039 | Bug 355039 [nls tooling] Error searching references to the selected properties key | null | resolved fixed | 75f87bb | ["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 | "2012-03-22T13:27:56Z" | "2011-08-18T09:33:20Z" |
374,264 | Bug 374264 [clean up] Convert for loop to enhanced applied to iterator produces broken code | Build Identifier: 20120216-1857 public static void main(String[] args) { List<String> list = new ArrayList<String>(Arrays.asList("first", "second", "third")); for (Iterator<String> iterator = list.iterator(); iterator.hasNext();) { removeSecond(iterator); } System.out.println(list); } private static void removeSecond(Iterator<String> iterator) { if ("second".equals(iterator.next())) { iterator.remove(); } } Reproducible: Always Steps to Reproduce: 1.Enter the code from details into any class 2.Check that "Convert for loop to enhanced" is checked in Save actions. 3.Save. Detected: "for (Iterator<String> iterator = list.iterator(); iterator.hasNext();)" string is changed to "for (String string : list)", the code becomes broken - compilation error. Expected: Code should not be changed. Workaround: not using "Convert for loop to enhanced" functionality. | resolved fixed | 5f95049 | ["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/ConvertIterableLoopOperation.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-21T18:07:01Z" | "2012-03-14T15:46:40Z" |
374,920 | Bug 374920 [preferences] Non-intuitive tab order on editor preferences dialog | 1. Open preferences. 2. Go to the Editor option. 3. Tab through the various preferences. The Bracket highlighting radio buttons come before any of the checkboxes above them. It should probably be made so it is consistent with the rest of the preference dialogs, i.e. so that the tab order has the higher up controls first. | resolved fixed | c3edc19 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaEditorAppearanceConfigurationBlock.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-21T17:03:59Z" | "2012-03-21T14:26:40Z" |
344,552 | Bug 344552 Source tabs not cleared when project is closed | Build Identifier: M20100211-1343 When a project is opened, Problems, Javadoc & Declarations display the relevant data. If the project is closed, these tab fields are not cleared and the (now irrelevant) data remains displayed. It remains displayed even if the project is deleted (from the Edit menu). Reproducible: Always Steps to Reproduce: 1.create a new project 2.Close it from Project menu 3.Delete it from the Edit menu | resolved fixed | 6440735 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/AbstractInfoView.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-20T15:54:44Z" | "2011-05-03T10:53:20Z" |
343,832 | Bug 343832 [navigation] Double-Clicking does not do anything sometimes | null | resolved fixed | dd1902f | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JavaDoubleClickSelectorTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaDoubleClickSelector.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-20T13:50:32Z" | "2011-04-26T12:13:20Z" |
348,758 | Bug 348758 [ltk] DeleteResourceChange should tell which resource could not be deleted | null | resolved fixed | 451d596 | ["org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/resource/DeleteResourceChange.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-20T11:59:13Z" | "2011-06-08T13:33:20Z" |
300,542 | Bug 300542 [build path] user library dialog should allow to select JAR from workspace | Build Identifier: When adding a jar to a user library, you are give the dialog for selecting a file with an external path. When attaching the source attachment or native library location you can select either an external path or a workspace path. It would be useful to also be able to specify the jar location as a workspace path, which would aid in sharing projects with other people. Reproducible: Always Steps to Reproduce: 1. Open preferences, navigate to Java -> Build Path -> User Libraries 2. Click New, and enter a name for the User Library. 3. Click "Add JARs", note the dialog type. 4. Select the "Native libary location" element, click "Edit". 5. Note the dialog type which allows for choosing an External Folder or Workspace path. | resolved fixed | 61c6412 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/UserLibraryPreferencePage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-20T10:37:49Z" | "2010-01-22T19:53:20Z" |
374,074 | Bug 374074 [navigation] Paste text then type Numpad_Enter doesn't work in Ctrl+O dialog | Build Identifier: If I copy some text(for example - charAt), then go to the class(say String), then I want to go to that method, so I type ctrl+O, paste the text(charAt) in the textbox, then type enter. This will not work - nothing happens. If I move the up and down key, then enter tyoe, it will go to that method. Of course there are many other ways to navigate to a method - for example we can type charAt in the outline view. This is a very very small issue, but if Eclipse can fix this, it would be a little better : ) Reproducible: Always | resolved fixed | cac0c43 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/AbstractInformationControl.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-19T13:08:50Z" | "2012-03-13T14:46:40Z" |
373,944 | Bug 373944 [breadcrumb] should show package-info.java | Breadcrumb should show package-info.java as child of a package (as a CU). | verified fixed | 8f9de10 | ["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 | "2012-03-19T13:08:16Z" | "2012-03-12T11:00:00Z" |
339,752 | Bug 339752 [ltk] Improve error reporting when deleting a project fails | Build ID: Eclipse 3.6.1 CQ:WIND00252893 When deleting a project fails because one of its directories is still hoged by a process (such as a cmd shell), the delete operation fails ungracefully with the stacktrace pasted below. Eclipse should improve its error reporting, telling the user what folder could not be deleted such that the user can investigate the problem. Steps to reproduce: 1. Create a project foo with a contained folder bar 2. Open Windows cmd prompt and chdir into .../foo/bar 3. Delete Project foo --> Error message is unfriendly. org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. at org.eclipse.core.internal.resources.Resource.delete(Resource.java:799) at org.eclipse.core.internal.resources.Project.delete(Project.java:331) at org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:130) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Contains: Could not delete '/SIM64-SMP-VSB/h'. org.eclipse.core.internal.resources.ResourceException: Problems encountered while deleting resources. at org.eclipse.core.internal.localstore.FileSystemResourceManager.delete(FileSystemResourceManager.java:270) at org.eclipse.core.internal.resources.ResourceTree.internalDeleteFolder(ResourceTree.java:352) at org.eclipse.core.internal.resources.ResourceTree.internalDeleteProject(ResourceTree.java:387) at org.eclipse.core.internal.resources.ResourceTree.standardDeleteProject(ResourceTree.java:837) at org.eclipse.core.internal.resources.Resource.unprotectedDelete(Resource.java:1944) at org.eclipse.core.internal.resources.Resource.delete(Resource.java:786) at org.eclipse.core.internal.resources.Project.delete(Project.java:331) at org.eclipse.ltk.core.refactoring.resource.DeleteResourceChange.perform(DeleteResourceChange.java:130) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278) at org.eclipse.ltk.core.refactoring.PerformChangeOperation$1.run(PerformChangeOperation.java:258) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.executeChange(PerformChangeOperation.java:306) at org.eclipse.ltk.internal.ui.refactoring.UIPerformChangeOperation.executeChange(UIPerformChangeOperation.java:92) at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:218) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) Contains: Problems encountered while deleting files. Contains: Could not delete: D:\NoScan\ws33\SIM64-SMP-VSB\h\config\vxConfig\cavium. Contains: Could not delete: D:\NoScan\ws33\SIM64-SMP-VSB\h\config\vxConfig\ipmpls. Contains: Could not delete: D:\NoScan\ws33\SIM64-SMP-VSB\h\config\vxConfig. Contains: Could not delete: D:\NoScan\ws33\SIM64-SMP-VSB\h\config. Contains: Could not delete: D:\NoScan\ws33\SIM64-SMP-VSB\h. Contains: Could not delete 'D:\NoScan\ws33\SIM64-SMP-VSB'. | resolved fixed | a5032a7 | ["org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/ChangeExceptionHandler.java", "org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/CompositeChange.java", "org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/internal/ui/refactoring/ChangeExceptionHandler.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-16T19:29:07Z" | "2011-03-11T19:00:00Z" |
367,669 | Bug 367669 IAE during setRawClasspath(..) due to missing link to external | In the Object Teams tests I'm intermittently seeing the following exception: java.lang.IllegalArgumentException: Element not found: /.org.eclipse.jdt.core.external.folders/.link15. at org.eclipse.core.internal.watson.ElementTree.elementNotFound(ElementTree.java:256) at org.eclipse.core.internal.watson.ElementTree.createElement(ElementTree.java:184) at org.eclipse.core.internal.resources.Workspace.createResource(Workspace.java:1369) at org.eclipse.core.internal.resources.Workspace.createResource(Workspace.java:1322) at org.eclipse.core.internal.localstore.RefreshLocalVisitor.createResource(RefreshLocalVisitor.java:80) at org.eclipse.core.internal.localstore.RefreshLocalAliasVisitor.createResource(RefreshLocalAliasVisitor.java:38) at org.eclipse.core.internal.localstore.RefreshLocalVisitor.synchronizeExistence(RefreshLocalVisitor.java:219) at org.eclipse.core.internal.localstore.RefreshLocalVisitor.visit(RefreshLocalVisitor.java:293) at org.eclipse.core.internal.localstore.UnifiedTree.accept(UnifiedTree.java:110) at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:920) at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:904) at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1694) at org.eclipse.core.internal.resources.Resource.createLink(Resource.java:711) at org.eclipse.core.internal.resources.Resource.createLink(Resource.java:647) at org.eclipse.jdt.internal.core.ExternalFoldersManager.createLinkFolder(ExternalFoldersManager.java:153) at org.eclipse.jdt.internal.core.ExternalFoldersManager.createLinkFolder(ExternalFoldersManager.java:145) at org.eclipse.jdt.internal.core.ExternalFolderChange.updateExternalFoldersIfNecessary(ExternalFolderChange.java:48) at org.eclipse.jdt.internal.core.ChangeClasspathOperation.classpathChanged(ChangeClasspathOperation.java:62) at org.eclipse.jdt.internal.core.SetClasspathOperation.executeOperation(SetClasspathOperation.java:74) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:793) at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3147) at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3109) at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3162) I suspect that the missing linked resource corresponds to a classpath container. The container initializer uses a path obtained using these steps: installDirectory = bundle.getEntry("/") -> yields s.t. like bundleentry://537.fwk23545827/ FileLocator.toFileURL(installDirectory).getPath() -> yields an absolute path into the area at configuration/org.eclipse.osgi/bundles/537/2/.cp/ At a closer look the above scheme is more complicated than needed and I'm hoping to work around the issue by an easier scheme. Still the IAE looks suspicious to me. | resolved fixed | 7bbe9b2 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/jarexport/FatJarExportTests.java", "org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/jarexport/PlainJarExportTests.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-16T16:48:00Z" | "2011-12-30T18:33:20Z" |
339,224 | Bug 339224 [content assist] ',' does not jump to the next argument if linked position has no proposal | null | resolved fixed | 576c9c7 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/AbstractJavaCompletionProposal.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ParameterGuessingProposal.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-16T14:26:00Z" | "2011-03-08T13:13:20Z" |
373,950 | Bug 373950 [preferences] Getting recommendations about the null settings even if annotation-based null analysis is not enabled | null | resolved fixed | e0b0a2c | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.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 | "2012-03-12T13:28:05Z" | "2012-03-12T13:46:40Z" |
372,128 | Bug 372128 [syntax highlighting] "Highlight enclosing brackets" has massive performance problems | N20120217-2000 "Highlight enclosing brackets" has massive performance problems: - open CleanUpTest - go to the last test and set caret in front of "public" - hold down ArrowRight => takes multiple seconds to move caret | resolved fixed | f52357d | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaPairMatcher.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-11T22:46:33Z" | "2012-02-21T16:00:00Z" |
373,788 | Bug 373788 Compilation errors when you create new JUnit test case | Build Identifier: M20110909-1335 When you create new JUnit test case called "Test" you receive compilation errors. There is following generate class: import static org.junit.Assert.*; import org.junit.Test; public class Test { @Test public void test() { fail("Not yet implemented"); } } The error message: Cannot convert Test to Annotation (in the line with @Test) It should be @org.junit.Test annotation used instead of @Test Reproducible: Always Steps to Reproduce: 1. File->New->Junit Test Case... 2. Set the class name to Test | resolved fixed | a299c4f | ["org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/wizards/NewTestCaseWizardPageOne.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-09T19:54:53Z" | "2012-03-09T13:33:20Z" |
322,556 | Bug 322556 [hovering] Quick Fix hover cuts message | null | resolved fixed | 7e3d706 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/AbstractAnnotationHover.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-08T10:44:42Z" | "2010-08-12T16:20:00Z" |
372,013 | Bug 372013 [preferences] option to turn on warnings for missing null default annotation | null | resolved fixed | a4197b7 | ["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 | "2012-03-07T09:27:32Z" | "2012-02-20T12:13:20Z" |
373,169 | Bug 373169 [open type] Annotation types find way into history of 'Implemented Interfaces Selection' dialog | Build Identifier: Version: 3.7.0 Build id: I20110613-1736 In 'New Java Class' wizard, dialog 'Implemented Interfaces Selection' normally does not allow to select an annotation type. But an annotation type worms its way into history section of this dialog, after it was selected in 'Enclosing Type Selection' dialog. While an annotation type is in its history, 'Implemented Interfaces Selection' dialog considers it as a valid option, so that finally 'New Java Class' wizard successfully creates Java class implementing an annotation type (with a warning 'The annotation type {0} should not be used as a superinterface for {1}). Reproducible: Always Steps to Reproduce: 1. Create a Java project, and an annotation type MyAnnotation in it. 2. Open 'New Java Class' wizard. 3. Click 'Add...' button at 'Interfaces' input - 'Implemented Interfaces Selection' dialog appears. 4. Make sure that there is no way to select MyAnnotation in it. That is ok. 5. Check 'Enclosing type' input and click 'Browse...' button to the right of it - 'Enclosing Type Selection' dialog appears. Select MyAnnotation in it and click 'OK' - 'Enclosing type' is populated. That is ok. 6. Repeat step 3. ('New Java Class' wizard may be reopened, that does not matter). 7. Make sure that MyAnnotation now is present in History section, and can be selected as valid option. That is a bug. | resolved fixed | fea27d2 | ["org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/util/TypeInfoFilter.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/IJavaElementSearchConstants.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/JavaUI.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-06T17:00:05Z" | "2012-03-03T02:00:00Z" |
355,926 | Bug 355926 [content assist] Code completion adds wrong method proposal if superclass method contains generic varargs argument | Build Identifier: M20110825-0847 When overriding a method from a superclass which has got a generic varargs argument, code completion adds a wrong method declaration. Expected: - the following method declaration should be added @Override void method(Z<?>... zs) { // TODO Auto-generated method stub super.method(zs); } Actual: - "transient" modifier is added - varargs argument is changed to array - outer class name ("Testcase") is added - the complete method declaration looks like follows transient void method(Testcase.Z<?>[] zs) {}; Environment: - Eclipse 3.7.1 (M20110825-0847) - JDK 7 --- class Testcase { static interface Z<T> {} static class A { void method(Z<?>... zs) {} } static class B extends A { // - type here `method` and then use code completion (ctrl + space) } } --- Reproducible: Always | resolved fixed | 944192f | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/CodeCompletionTest.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 | "2012-03-03T10:08:38Z" | "2011-08-26T09:13:20Z" |
372,973 | Bug 372973 [call hierarchy] Selecting element in callee hierarchy reveals wrong editor location | Build Identifier: Version: 3.7.2 Build id: M20120208-0800 package packageA; public class A { public static void m1() {m2();}; public static void m2() {m3();}; public static void m3() {} } package packageB; public class B { static void m1() { packageA.A.m2(); packageA.A.m1(); } static void main() { m1(); } } This CTRL+ALT+H produces the graph m1() : void - packageB.B m2() : void - packageA.A m3() : void - packageA.A m1() : void - packageA.A m2() : void - packageA.A m3() : void - packageA.A The structure is ok and jumps to invocation site, as expected, when asked to focus. The only problem is clicking on m1->m1 and m1->m2. It oscillates between invocation site and invoked method declaration with every click. Reproducible: Always | resolved fixed | 6bbf682 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyUI.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-01T19:24:08Z" | "2012-03-01T13:53:20Z" |
106,228 | Bug 106228 [navigation] CamelCase pattern matching in quick outline and quick hierarchy | I've gotten to like this in the open type dialog. I think it would be quite useful in the quick outline opened in the java editor as well. | verified fixed | e5a4564 | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JavaElementPrefixPatternMatcherTest.java", "org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JdtTextTestSuite.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/util/TypeInfoFilter.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/AbstractInformationControl.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaElementPrefixPatternMatcher.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaOutlineInformationControl.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/util/PatternMatcher.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-03-01T17:38:27Z" | "2005-08-05T19:26:40Z" |
372,818 | Bug 372818 Test failures in UI because of bug 265744 | Failures exist in following suites. ScopeAnalyzerTest UnresolvedVariablesQuickFixTest LocalCorrectionsQuickFixTest I will take a look. | resolved fixed | c7788bb | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/ScopeAnalyzerTest.java", "org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java", "org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedVariablesQuickFixTest.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-02-29T12:13:43Z" | "2012-02-29T07:20:00Z" |
40,580 | Bug 40580 [navigation] Matching brace (Ctrl+Shift+P) should work anywhere in the file | Now you have to be exactly behind a brace to get CTRL-SHIFT-P working. This is a bit annoying. Can't it just work every where in the file? then it just searches for the brace i am in and toggles between begin and end. for example: int foo() { // code <<< cursor here 1. if(bar()) { // code <<< cursor here 2. // some more code } } with cursor here 1 it shows the braces of the complete method with cursor here 2 it shows the braces of the if. | verified fixed | 8fc5b67 | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JavaPairMatcherTest.java", "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"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-02-26T08:19:39Z" | "2003-07-22T07:46:40Z" |
371,968 | Bug 371968 recommend option settings when enabling annotation-based null analysis | null | resolved fixed | 595c559 | ["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 | "2012-02-24T21:09:32Z" | "2012-02-18T13:00:00Z" |
71,406 | Bug 71406 [rulers] request for click & event modifiers from ruler annotations | The debugger would like to be able to register for "shift-click" and "alt- click" events on breakpoints in the editor ruler. This way we can implement features such as enable/disable in the ruler and "show breakpoint properties" via mouse clicks, rather than having to display the context menu. | resolved fixed | 2a1572b | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaSelectMarkerRulerAction2.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/AnnotationExpansionControl.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-02-22T17:36:43Z" | "2004-08-04T20:06:40Z" |
367,465 | Bug 367465 [jar exporter] Runnable Jar File Export "repacks referenced libraries" warning cannot be disabled | null | resolved fixed | 93cf9ad | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/OptionalMessageDialog.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/SortMembersMessageDialog.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/FatJarPackageWizard.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-02-21T09:03:01Z" | "2011-12-23T00:26:40Z" |
371,987 | Bug 371987 [quick fix] generated code where required type is masked by a local declaration should use full type name | Build Identifier: Indigo release, 20110615-0604 If the context in which an undeclared field is used refers to a type whose name is masked by another one (e.g. due to a locally declared class of the same name), the 'quick fix' generated just substitutes one error for another, i.e. that the types are incompatible. Eclipse should detect this scenario and use fully qualified types when it would occur. This is not as strange a scenario as it would at first appear, and happens especially frequently in code using the Android API, which includes interfaces that mask each other in the same context (e.g. DialogInterface.OnClickListener and View.OnClickListener, both of which are local types in classes that extend Dialog, and Eclipse currently declares fields to be the former whereas the latter is more commonly used). Reproducible: Always Steps to Reproduce: 1. Create class with code that refers to a non-existent field that should have a type which is masked by a local declaration, for example: public class Test { class Runnable { } public void test () { new Thread (myRunnable); } } 2. Choose 'quick fix' for the undefined identifier error, and choose 'create field' The field declaration added is: private Runnable myRunnable; It should be: private java.lang.Runnable myRunnable; as in this context 'Runnable' refers to the local class that is not the one that should be used. | resolved fixed | 6a4ed47 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedVariablesQuickFixTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/NewVariableCorrectionProposal.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-02-20T19:11:25Z" | "2012-02-19T11:13:20Z" |
296,589 | Bug 296589 [breadcrumb] Opening a file via breadcrumb does not retarget the status line | User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB0; .NET CLR 1.1.4322; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Build Identifier: 20090920-1017 When I choose a class via the breadcrumb, the line numbers at the bottom of the screen do not update themselves. In addition, Source -> Clean Up fails to work until I've fixed the problem. The only way for the line numbers to update themselves again (and for Source -> Clean Up) is for me to select a document not using breadcrumbs and go back to my document. Another way is to control+pageup and control+pagedown to get back to where I'm at. Reproducible: Always Steps to Reproduce: 1.I'm in the Java Perspective. My breadcrumb bar looks like the following: ncoserver-business-cbservices -> src/main/java -> com.ncogroup.ncoserver.business.service -> NcoDeceasedService 2. I observe the line number at the bottom of the screen. It reflects the current file I'm in, for this example line 10 of NcoDeceasedService.java. 3. I click on the 4th item in the breadcrumb to choose another file. For this example, I choose NcoDependentService. 4. The cursor focus moves to line 3 and hilites the class name. The bottom of the screen still shows that I'm on line number 10 of the previous file. 5. When I move the cursor around the screen via keyboard or mouse, the line number does not update. | verified fixed | deaa20e | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/breadcrumb/EditorBreadcrumb.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-02-09T14:02:24Z" | "2009-12-01T17:53:20Z" |
370,725 | Bug 370725 [implementation] BadLocationException when pasting in a string | What steps will reproduce the problem? 1. Ran a unit test, which failed. Copied Actual content from the Compare dialog 2. Pasted it into a test case file 3. Copied '+ "' string from the file 4. Started to paste it in front of each line -- Error Details -- Date: Mon Feb 06 15:35:16 CET 2012 Message: Internal Error Severity: Error Product: Eclipse SDK 3.7.0.v201106030909 (org.eclipse.sdk.ide) Plugin: org.eclipse.jdt.ui Session Data: eclipse.buildId=I20110603-0909 java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-20091214_49398 (JIT enabled, AOT enabled) J9VM - 20091214_049398 JIT - r9_20091123_13891 GC - 20091111_AA BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pl_PL Command-line arguments: -os win32 -ws win32 -arch x86 Exception Stack Trace: org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.AbstractDocument.getChar(AbstractDocument.java:806) at org.eclipse.jdt.internal.ui.text.JavaIndenter.isStringContinuation(JavaIndenter.java:831) at org.eclipse.jdt.internal.ui.text.JavaIndenter.findReferencePosition(JavaIndenter.java:793) at org.eclipse.jdt.internal.ui.text.JavaIndenter.getReferenceIndentation(JavaIndenter.java:444) at org.eclipse.jdt.internal.ui.text.JavaIndenter.computeIndentation(JavaIndenter.java:477) at org.eclipse.jdt.internal.ui.text.JavaIndenter.computeIndentation(JavaIndenter.java:463) at org.eclipse.jdt.internal.ui.text.java.JavaAutoIndentStrategy.smartPaste(JavaAutoIndentStrategy.java:702) at org.eclipse.jdt.internal.ui.text.java.JavaAutoIndentStrategy.customizeDocumentCommand(JavaAutoIndentStrategy.java:1240) at org.eclipse.jface.text.TextViewer.customizeDocumentCommand(TextViewer.java:3752) at org.eclipse.jface.text.TextViewer.handleVerifyEvent(TextViewer.java:3782) at org.eclipse.jface.text.source.projection.ProjectionViewer.handleVerifyEvent(ProjectionViewer.java:1277) at org.eclipse.jface.text.TextViewer$TextVerifyListener.verifyText(TextViewer.java:435) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:265) 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.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:774) at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7148) at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:7994) at org.eclipse.swt.custom.StyledText.paste(StyledText.java:7236) at org.eclipse.jface.text.TextViewer.paste(TextViewer.java:4052) at org.eclipse.jface.text.TextViewer.doOperation(TextViewer.java:3990) at org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:1012) at org.eclipse.jface.text.source.projection.ProjectionViewer.doOperation(ProjectionViewer.java:1534) at org.eclipse.jdt.internal.ui.javaeditor.JavaSourceViewer.doOperation(JavaSourceViewer.java:191) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:200) at org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction.doPasteWithImportsOperation(ClipboardOperationAction.java:544) at org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction.internalDoOperation(ClipboardOperationAction.java:328) at org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction$1.run(ClipboardOperationAction.java:278) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jdt.internal.ui.javaeditor.ClipboardOperationAction.run(ClipboardOperationAction.java:276) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1262) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1104) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1100) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1509) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4640) at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:345) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4528) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2530) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) | resolved fixed | 22dfdc4 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaIndenter.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-02-07T08:26:25Z" | "2012-02-06T14:53:20Z" |
369,558 | Bug 369558 [build path] Source Attachment dialogs should leave encoding combo empty if none is set | null | verified fixed | 31088ad | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewWizardMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/SourceAttachmentBlock.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-02-01T20:02:08Z" | "2012-01-24T18:33:20Z" |
366,013 | Bug 366013 [preferences] Polish preference UI for null annotations | I20111207-2118. The preference UI for nulll annotations looks clumsy and the important parts are coming after the less important settings. We should move the rarely used configuration of the annotations into a separate dialog which has a 'Restore Defaults' button. On the main page we add a 'Configure Annotations...' button (most likely at the end of the section). | verified fixed | cfb978b | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.java", "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 | "2012-01-23T20:28:47Z" | "2011-12-08T13:13:20Z" |
369,319 | Bug 369319 [junit] interesting warning in JUnitPropertyTester | null | resolved fixed | 423f052 | ["org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JUnitPropertyTester.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-01-23T11:34:30Z" | "2012-01-21T21:06:40Z" |
369,295 | Bug 369295 [extract method] Extract code in a method that returns generic type causes compilation error | Build Identifier: Version: 3.7.1 Build id: I20110613-1736 Extract method refactoring introduces incorrect return type for the extracted method. Reproducible: Always Steps to Reproduce: 1. Mark "toExtract(list)" in the example below 2. Perform ExtractMethod refactoring 3. The resulting code is not compilable class ExtractMethod { class C { void m() { } } <T extends Comparable<? super T>> void method(List<T> list) { toExtract(list).m(); } static <T extends Comparable<? super T>> C toExtract(List<T> list) { return null; } } | resolved fixed | e5035aa | ["org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/generics_in/A_test1120.java", "org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/generics_out/A_test1120.java", "org.eclipse.jdt.ui.tests.refactoring/test", "cases/org/eclipse/jdt/ui/tests/refactoring/ExtractMethodTests.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodRefactoring.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-01-21T18:11:37Z" | "2012-01-20T20:06:40Z" |
350,511 | Bug 350511 [preferences] Incorrect padding for Show Whitespace characters preference | Build Identifier: 20110615-0604 The Show whitespace characters preference in the text editors preference page looks misaligned under GTK3. I think this is because setText wasn't called on the check box. Reproducible: Always Steps to Reproduce: 1. Running GTK3 2. Open the Text Editors preference page 3. observe that the Show Whitespace preference is indented slightly more than other items 4. Clicking on the checkbox also shows a little rectangle next to the check box where the text would normally go. | resolved fixed | f996782 | ["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 | "2012-01-20T18:36:44Z" | "2011-06-28T03:00:00Z" |
368,452 | Bug 368452 Full rebuild is asked on compiler options changed even when workspace is empty | Build Identifier: Version: Indigo Service Release 1 Build id: 20110916-0149 When a compiler option has been changed (through Preferences / Java / Compiler / Errors/Warnings), a dialog box appears and tells you that The Error/Warning settings have changed and that A full rebuild is required for changes to take effect and asks you if you want to Do the full build now. The question should not be asked when the workspace contains no project to possibly rebuild. Reproducible: Always Steps to Reproduce: 1. Grab a fresh eclipse install. (Optional, but just to be sure.) 2. Start eclipse, pointing it to a blank, new workspace directory. (So that it starts with no projects.) 3. Go straight to Preferences, change some Java compiler option, e.g., ask for Include 'assert' in null analysis. Click Apply or OK. | resolved fixed | ffbb42b | ["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 | "2012-01-13T15:45:00Z" | "2012-01-12T14:53:20Z" |
345,213 | Bug 345213 [content assist][preferences] Add enablement to Java completion proposal category extension point | We have a java completion proposal computer, but it should only be used for projects of a specific type. However, there is no way to eliminate our computer for projects that don't match this criteria. If there were an enablement (optional) element on the extension point, we'd be able to prevent this completion proposal category from showing up on project where it makes no sense. example: <extension point="org.eclipse.jdt.ui.javaCompletionProposalComputer" id="jaxbCompletionProposals" name="%jaxbCompletionProposals"> <proposalCategory icon="icons/full/etool16/jaxb_facet.gif"/> <enablement> <with variable="project"> <test property="org.eclipse.wst.common.project.facet.core.projectFacet" value="jpt.jaxb" forcePluginActivation="true"/> </with> </enablement> </extension> | resolved fixed | 9538bb8 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/SpecificContentAssistAction.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/SpecificContentAssistExecutor.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/CompletionProposalCategory.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ContentAssistProcessor.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaCompletionProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2012-01-09T12:19:11Z" | "2011-05-09T22:26:40Z" |
365,775 | Bug 365775 [preferences] Validate syntactic correctness of null annotation option settings | Validate syntactic correctness of null annotation option settings (must be a fully qualified name). | resolved fixed | 12e3f37 | ["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 | "2012-01-03T12:05:07Z" | "2011-12-06T16:46:40Z" |
365,041 | Bug 365041 Similar named entries in Surround with menu cause confusion | In the Surround With menu there are two (confusing) items 1. Try/catch Block - uses 'Code Templates' 2. try (try catch block) - based on 'Editor Templates' The first one invokes the Surround With 'Refactoring' which will find the exact exceptions thrown from the selection and use those in the catch block. The second one, which uses the editor template, always uses 'Exception' in the catch block. => This can be quite confusing. Solution 1. Use icons in the Surround With menu a) The 'green arrow' we use for Quick Assists can be used to indicate that the action is a refactoring b) In Content Assist popup we use an icon to indicate template proposals, the same icon can be used here. 2. 'Configure Templates' action should also show the 'Code Template' node. | verified fixed | 52f1ab9 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/SurroundWithActionGroup.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/SurroundWithTemplateMenuAction.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-12-24T11:33:54Z" | "2011-11-29T12:33:20Z" |
41,302 | Bug 41302 [quick assist] [extract method] Calling extract method from a selection | In 3.0M2 If you select the following code (up to the very last character) and ask for "extract method" you'll get an error dialog indication "Selection ends inside a comment" foo();//a comment | resolved fixed | 1271a27 | ["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 | "2011-12-23T10:30:10Z" | "2003-08-07T21:00:00Z" |
357,325 | Bug 357325 [render] Method parameter annotations are not shown in Javadoc hover/view | Build Identifier: 3.7.1 or any previous 3.5 - 3.7 builds AS IS: Given the example class below, javadoc hover shown for both methods (toString()/main()) does NOT include parameter annotations information. ################################# import static java.lang.annotation.ElementType.*; import java.lang.annotation.*; public class TestParameterAnnotations { @NonNull String x; /** * @param y any * @return given value as string or empty string */ @NonNull public String toString(@NonNull Object y) { return y != null ? y.toString() : ""; } /** * @param args any parameters */ public static void main(@NonNull String[] args) { String s = new TestParameterAnnotations().toString(null); System.err.println(s); } } @Target({TYPE, FIELD, METHOD, PARAMETER, CONSTRUCTOR, LOCAL_VARIABLE}) @Retention(RetentionPolicy.CLASS) @interface NonNull { } ###################################### TO BE: As annotations like above are often very important for the code documentation, they should be shown for method parameters. Interestingly, method return value annotation and class field annotations are shown in the javadoc hover/view. Reproducible: Always | verified fixed | b441737 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/JavaElementLabelsTest.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/dom/ASTNodes.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java", "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", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/JavaElementLabels.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-12-05T15:46:53Z" | "2011-09-11T11:20:00Z" |
364,947 | Bug 364947 [move method] The design of the Move Instance Method refactoring tool doesn't match users' expectations | null | resolved fixed | a83a65b | ["org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/MoveInstanceMethodWizard.java", "org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/RefactoringMessages.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-12-01T07:54:28Z" | "2011-11-28T14:20:00Z" |
125,326 | Bug 125326 [pull up] of abstract methods to abstract base class fails [refactoring] | I have an abstract class X with some abstract methods, some regular methods, some static methods, and some subclasses. X has an abstract base class B. In fact, B is empty: It has no methods, no fields, nothing yet. I want to move three abstract methods from X to B. I could have simply used cut&paste in this situation. But instead, I choose to use "refactor->pull up". That bombed on me. The .metadata/.log has this to say (due to an oversecured internet setup, I have to copy this by typing it in, so pardon any mistakes): !ENTRY org.eclipse.ltk.ui.refactoring 4 10000 2006-01-26 14:10:28.07 !MESSAGE Internal Error !STACK 0 java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModelContext.java:327) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:830) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.createChange(RefactoringWizard.java:573) at org.eclipse.ltk.ui.refactoring.RefactoringWizard.computeUserInputSuccessorPage(RefactoringWizard.java:416) at org.eclipse.ltk.ui.refactoring.RefactoringWizardPage.computeSuccessorPage(UserInputWizardPage.java:74) at org.eclipse.jdt.internal.ui.refactoring.PullUpWizard$PullUpInputPage2.getNextPage(PullUpWizard.java:1150) at org.eclipse.jface.wizard.WizardDialg.nextPressed(WizardDialg.java:747) - and so on - Caused by: java.lang.IllegalArgumentException at org.eclipse.jdt.core.dom.rewrite.ASTRewrite.createStringPlaceholder(ASTRewrite.java:428) at org.eclipse.jdt.internal.context.refactoring.structure.PullUpRefactoring.createJavadocForStub(PullUpRefactoring.java:1035) at org.eclipse.jdt.internal.context.refactoring.structure.PullUpRefactoring.addMethodStubsToNonAbstractSubclassesOfTargetClass(PullUpRefactoring.java:415) at org.eclipse.jdt.internal.context.refactoring.structure.PullUpRefactoring.createChangeManager(PullUpRefactoring.java:1002) at org.eclipse.jdt.internal.context.refactoring.structure.PullUpRefactoring.checkFinalConditions(PullUpRefactoring.java:615) - and so on - Regards, and thank you for providing fine software. | resolved fixed | c2b8767 | ["org.eclipse.jdt.ui.tests.refactoring/resources/PullUp/test50/in/A.java", "org.eclipse.jdt.ui.tests.refactoring/resources/PullUp/test50/out/A.java", "org.eclipse.jdt.ui.tests.refactoring/test", "cases/org/eclipse/jdt/ui/tests/refactoring/PullUpTests.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PullUpRefactoringProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-11-15T15:07:37Z" | "2006-01-26T12:53:20Z" |
361,916 | Bug 361916 [nls tooling][quick assist] Suggestions to fine tune quick assists in Properties File editor | null | verified fixed | c76aef0 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesQuickAssistProcessor.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/EditAnnotator.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-11-14T15:31:53Z" | "2011-10-25T13:40:00Z" |
362,743 | Bug 362743 [ltk] NPE when deleting plugin from workspace | This is 4.2M3. Here is the stack trace: org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:228) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:209) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:123) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:161) at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommandInContext(LegacyHandlerService.java:494) 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:474) at org.eclipse.jdt.internal.ui.refactoring.reorg.DeleteAction.run(DeleteAction.java:195) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:275) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:251) 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.Display.sendEvent(Display.java:4129) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3975) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3614) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:972) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:888) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:90) at org.eclipse.ui.internal.Workbench$3.run(Workbench.java:565) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:520) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:352) 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:624) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:579) at org.eclipse.equinox.launcher.Main.run(Main.java:1431) Caused by: java.lang.NullPointerException at org.eclipse.ltk.ui.refactoring.resource.DeleteResourcesWizard$DeleteResourcesRefactoringConfigurationPage.getLocation(DeleteResourcesWizard.java:183) at org.eclipse.ltk.ui.refactoring.resource.DeleteResourcesWizard$DeleteResourcesRefactoringConfigurationPage.createControl(DeleteResourcesWizard.java:161) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.createContents(RefactoringWizardDialog2.java:632) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:178) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:202) at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:122) 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.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:68) at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) ... 44 more | resolved fixed | 868f969 | ["org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/resource/DeleteResourceChange.java", "org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/resource/DeleteResourcesWizard.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-11-14T14:30:00Z" | "2011-11-03T00:26:40Z" |
139,231 | Bug 139231 [quick fix] duplicate exception name after add throws to catch | Eclipse SDK Version: 3.2.0 Build id: I20060413-1718 "Add catch clause to surrounding try" of "Quick Fix" generates code with error. | resolved fixed | 4bf2e6c | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest17.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 | "2011-10-31T17:25:26Z" | "2006-04-28T16:00:00Z" |
362,496 | Bug 362496 [quick assist][nls tooling] IAE in new 'Create field...' quick assist in properties editor | If a property is not a valid java identifier the following exception is thrown on invoking the quick assist. java.lang.IllegalArgumentException at org.eclipse.jdt.core.dom.SimpleName.setIdentifier(SimpleName.java:198) at org.eclipse.jdt.core.dom.AST.newSimpleName(AST.java:2031) at org.eclipse.jdt.internal.corext.refactoring.nls.AccessorClassModifier.getNewFinalStringFieldDeclaration(AccessorClassModifier.java:331) at org.eclipse.jdt.internal.corext.refactoring.nls.AccessorClassModifier.addKey(AccessorClassModifier.java:291) at org.eclipse.jdt.internal.corext.refactoring.nls.AccessorClassModifier.addKey(AccessorClassModifier.java:282) at org.eclipse.jdt.internal.corext.refactoring.nls.AccessorClassModifier.addFields(AccessorClassModifier.java:191) at org.eclipse.jdt.internal.ui.propertiesfileeditor.PropertiesQuickAssistProcessor.getCreateFieldsInAccessorClassProposals(PropertiesQuickAssistProcessor.java:188) at org.eclipse.jdt.internal.ui.propertiesfileeditor.PropertiesQuickAssistProcessor.collectAssists(PropertiesQuickAssistProcessor.java:87) at org.eclipse.jdt.internal.ui.propertiesfileeditor.PropertiesCorrectionProcessor.computeQuickAssistProposals(PropertiesCorrectionProcessor.java:8 | verified fixed | 02dab19 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-31T14:52:41Z" | "2011-10-31T14:06:40Z" |
362,404 | Bug 362404 [1.7][preferences] new warning for missing try-with-resources is in wrong category | The "Resource not managed via try-with-resource" option is in the wrong category in the UI. The compiler problem is in the CategorizedProblem#CAT_CODE_STYLE category, so we should also show the option in the corresponding UI section (Code style, not Potential programming problem). | resolved fixed | 640f8fd | ["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-10-31T13:09:37Z" | "2011-10-29T17:40:00Z" |
221,782 | Bug 221782 [jar exporter] JAR Export Wizard Should Warn You if Skipping Class files | Build ID: 3.3.1.1 Steps To Reproduce: 1. Create a class with a compiler warning (e.g., unused import). 2. Export to a JAR file, leaving "Export Class files with compile warnings" unchecked. 3. Finish the export. Note that you get no indication that anything went wrong. However, the JAR file contains no class file and of course will not execute (NoClassDefFoundError). More information: I just wasted a lot of time on this. In retrospect, I should have noticed this checkbox. However, since Eclipse is unable to do what I was asking, ideally I should have received a warning -- something like "Warning: Class files with compile warnings were skipped". Thanks. | verified fixed | d442e5c | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarFileExportOperation.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-27T15:18:29Z" | "2008-03-07T03:20:00Z" |
361,920 | Bug 361920 [nls tooling][quick assist] IAE with 'Remove key' quick assist in Properties File editor | null | verified fixed | b4c16cc | ["org.eclipse.jdt.ui.tests.refactoring/test", "cases/org/eclipse/jdt/ui/tests/refactoring/nls/PropertyFileDocumentModellTest.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/nls/PropertyFileDocumentModel.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-26T19:00:21Z" | "2011-10-25T13:40:00Z" |
362,106 | Bug 362106 [nls tooling][quick assist] 'Remove key' should be called 'Remove property' | 'Remove key' should be called 'Remove property'. | verified fixed | f9af56f | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/PropertiesFileQuickAssistTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesFileEditorMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertiesQuickAssistProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-26T17:21:37Z" | "2011-10-26T17:26:40Z" |
361,559 | Bug 361559 [ltk] DeleteArguments misses API getDeleteProjectContents() | master DeleteArguments misses the API below. Without that, participants can't know whether contents will be deleted or not. /** * Returns whether projects contents will be deleted as well. This method * is not applicable for file and folder deletions. * * @return <code>true</code> if the refactoring will delete the project * contents, <code>false</code> if it only removes the reference * from the workspace */ public boolean getDeleteProjectContents() { return fDeleteProjectContents; } | resolved fixed | 6a7fe43 | ["org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/participants/DeleteArguments.java", "org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/internal/core/refactoring/resource/DeleteResourcesProcessor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-24T19:45:57Z" | "2011-10-20T14:13:20Z" |
347,599 | Bug 347599 [refactoring] Provide a way to implement refactorings that depend on resources that have to be explicitly released | null | resolved fixed | 5069473 | ["org.eclipse.jdt.ui.tests/examples/org/eclipse/jdt/ui/examples/TestMoveDescriptorAction.java", "org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/binary/BinaryRefactoringHistoryWizard.java", "org.eclipse.ltk.core.refactoring.tests/src/org/eclipse/ltk/core/refactoring/tests/AllTests.java", "org.eclipse.ltk.core.refactoring.tests/src/org/eclipse/ltk/core/refactoring/tests/RefactoringContextTest.java", "org.eclipse.ltk.core.refactoring.tests/src/org/eclipse/ltk/core/refactoring/tests/resource/ResourceRefactoringTests.java", "org.eclipse.ltk.core.refactoring.tests/src/org/eclipse/ltk/core/refactoring/tests/resource/ResourceRefactoringUndoTests.java", "org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/PerformRefactoringHistoryOperation.java", "org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/PerformRefactoringOperation.java", "org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/Refactoring.java", "org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/RefactoringContext.java", "org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/RefactoringDescriptor.java", "org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/RefactoringWizard.java", "org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/RefactoringWizardOpenOperation.java", "org.eclipse.ltk.ui.refactoring/src/org/eclipse/ltk/ui/refactoring/history/RefactoringHistoryWizard.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-24T18:59:38Z" | "2011-05-30T04:33:20Z" |
361,403 | Bug 361403 Add UI for new JDT Core option: OUTPUT_LOCATION_OVERLAPPING_ANOTHER_SOURCE | null | verified fixed | a5b3f92 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/buildpath/BuildpathModifierActionTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaBuildConfigurationBlock.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 | "2011-10-20T14:55:20Z" | "2011-10-19T13:13:20Z" |
360,913 | Bug 360913 Resource leaks in o.e.jdt.ui | There are 2 valid resource leaks warnings in o.e.jdt.ui Resource leak: 'outputStream' is not closed at this location UnpackFatJarAntExporter.java /org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat line 58 Resource leak: 'outputStream' is not closed at this location UnpackJarAntExporter.java /org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat line 64 | resolved fixed | b863c82 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/UnpackFatJarAntExporter.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/UnpackJarAntExporter.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-14T08:46:11Z" | "2011-10-14T05:26:40Z" |
360,642 | Bug 360642 Allow to associate an editor to class files which have no source | 3.7. We should allow to associate an editor to class files which have no source. This will e.g. allow users to associate a disassembler to such files. | verified fixed | 39fa1b9 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/EditorUtility.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/InternalClassFileEditorInput.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-12T10:22:14Z" | "2011-10-12T09:00:00Z" |
304,176 | Bug 304176 [hashcode/equals] Generated equals() should use Arrays.deepEquals() instead of Arrays.equals() | Build Identifier: I'm not sure what is the point of Arrays.equals() since it can fail to work properly for a number of cases, including three-dimensional arrays, as demonstrated in this example: import java.util.Arrays; public class Test { public static void main(String[] args) { int[][][] a = new int[][][] {{null}}; int[][][] b = new int[][][] {{null}}; System.out.println(Arrays.equals(a, b)); // false System.out.println(Arrays.deepEquals(a, b)); // true } } I believe Eclipse-generated equals() method should use Arrays.deepEquals() as it seems to be doing its job properly. Reproducible: Always | resolved fixed | 8bddf00 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/source/GenerateHashCodeEqualsTest.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/codemanipulation/GenerateHashCodeEqualsOperation.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-11T09:00:22Z" | "2010-03-01T02:20:00Z" |
350,285 | Bug 350285 ASTRewrite destroys formatting on CatchClause#setBody(copyTarget) | BETA_JAVA7, but most probably not Java 7 related The new Quick Fix to convert a multi-catch to separate catch blocks tried to use newCatchClause.setBody( (Block) rewrite.createCopyTarget(catchClause.getBody())); in QuickAssistProcessor#getUnrollMultiCatchProposals(..), but this mangled e.g. public class E { void foo() { try { System.out.println("foo"); } catch (IllegalArgumentException | NullPointerException ex) { ex.printStackTrace(); } } } into void foo() { try { System.out.println("foo"); } catch (IllegalArgumentException ex) { ex.printStackTrace(); } catch (NullPointerException ex) { ex.printStackTrace(); } } As a workaround, we now copy statement-by-statement, but this should not be necessary, and it can lose comments if they are separated by newlines. UI tests are in AssistQuickFixTest17. | verified fixed | b557721 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AssistQuickFixTest17.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-10T09:33:08Z" | "2011-06-24T15:40:00Z" |
359,940 | Bug 359940 [nls tooling] NLS hover shown in place of Java hover | Hover over any reference of a public string field of org.eclipse.jdt.internal.corext.refactoring.nls.NLSRefactoring class. => The hover says - "The properties file could not be detected", which is not right. | verified fixed | de2edee | ["org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/nls/AccessorClassCreator.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/nls/NLSRefactoring.java", "org.eclipse.jdt.ui/ui", "refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/search/NLSSearchQuery.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-05T12:06:37Z" | "2011-10-05T02:00:00Z" |
354,092 | Bug 354092 [preferences] Java Compiler property page doesn't gray out all widgets (without project specific settings) | Build id: I20110803-1800 Steps to reproduce: 1. Create new Java project. 2. Open properties dialog for this project. 3. Open Java Compiler page. Note that by default 'Enable project specific settings' is disabled and all widgets below are grayed (see Screenshot 1). 4. Switch to another property page but do not close the dialog. 5. Switch back to Java Compiler page. Note that some widgets are not grayed any more but no action can be done on those widgets (see Screenshot 2). Reproducible: Always | verified fixed | c7b806a | ["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 | "2011-10-04T11:58:05Z" | "2011-08-07T15:13:20Z" |
349,782 | Bug 349782 [quick assist] "Convert to enhanced for loop" isn't available for loops over array with prefix increment | Build Identifier: M20110210-1200 public static void main(String[] args) { for (int i = 0; i < args.length; ++i) { // "Convert to enhanced for loop" refactoring should be available on this line String arg = args[i]; System.out.println(arg); } for (int i = 0; i < args.length; ++i) { String arg = args[i]; System.out.println(arg); } } Reproducible: Always Steps to Reproduce: 1. Paste example function to some class. 2. Open suggestion window on for loop header (Ctrl-1). 3. Expected: "Convert to enhanced for loop" command is in list of suggestions, actual: It isn't. | resolved fixed | a5cb166 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java", "org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/ConvertForLoopQuickFixTest.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/fix/ConvertForLoopOperation.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-10-01T03:54:51Z" | "2011-06-20T06:06:40Z" |
350,290 | Bug 350290 Remove FlowInfo#fExceptions and everything that refers to it | null | resolved fixed | f8b5b03 | ["org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/FlowAnalyzer.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/FlowInfo.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/MessageSendFlowInfo.java", "org.eclipse.jdt.ui/core", "refactoring/org/eclipse/jdt/internal/corext/refactoring/code/flow/ThrowFlowInfo.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-09-30T12:32:22Z" | "2011-06-24T15:40:00Z" |
358,823 | Bug 358823 Checkbox wrongly enabled on Clean up preference page | null | resolved fixed | c1839c4 | ["org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/cleanup/CleanUpTabPage.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-09-30T10:15:16Z" | "2011-09-25T14:13:20Z" |
358,846 | Bug 358846 [1.7][preferences] new warning for missing try-with-resources | null | verified fixed | d77b8b6 | ["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-09-29T13:50:11Z" | "2011-09-26T06:53:20Z" |
335,224 | Bug 335224 [JUnit] New JUnit Test Case wizard doesn't store method stub selection state | HEAD The New JUnit Test Case wizard doesn't store method stub selection state when you click Finish on the first page. Reason is that NewTestCaseWizardPageOne#saveWidgetValues() is only called on setVisible(false). | resolved fixed | 08752e9 | ["org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/wizards/MethodStubsSelectionButtonGroup.java", "org.eclipse.jdt.junit/src/org/eclipse/jdt/junit/wizards/NewTestCaseWizardPageOne.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-09-27T08:25:47Z" | "2011-01-24T17:26:40Z" |
353,731 | Bug 353731 [type hierarchy] Exception occurred in listener of Type hierarchy change notification | No steps, sorry. Noticed it in the Error Log an hour later. -- Error Details -- Date: Wed Aug 03 11:10:31 CEST 2011 Message: Exception occurred in listener of Type hierarchy change notification Severity: Error Product: Eclipse SDK 3.7.0.v201107291200 (org.eclipse.sdk.ide) Plugin: org.eclipse.jdt.core Session Data: eclipse.buildId=I20110729-1200 java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr7-20091214_49398 (JIT enabled, AOT enabled) J9VM - 20091214_049398 JIT - r9_20091123_13891 GC - 20091111_AA BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=pl_PL Framework arguments: -product org.eclipse.sdk.ide Command-line arguments: -product org.eclipse.sdk.ide -data D:\workspace\eclipse\web -dev file:D:/workspace/eclipse/team/dev.eclipse.org_HEAD_extssh/.metadata/.plugins/org.eclipse.pde.core/Eclipse (web)/dev.properties -os win32 -ws win32 -arch x86 Exception Stack Trace: java.lang.NullPointerException at org.eclipse.jdt.internal.corext.util.SuperTypeHierarchyCache$HierarchyCacheEntry.dispose(SuperTypeHierarchyCache.java:57) at org.eclipse.jdt.internal.corext.util.SuperTypeHierarchyCache.removeHierarchyEntryFromCache(SuperTypeHierarchyCache.java:211) at org.eclipse.jdt.internal.corext.util.SuperTypeHierarchyCache.access$0(SuperTypeHierarchyCache.java:208) at org.eclipse.jdt.internal.corext.util.SuperTypeHierarchyCache$HierarchyCacheEntry.typeHierarchyChanged(SuperTypeHierarchyCache.java:41) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy$1.run(TypeHierarchy.java:365) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.fireChange(TypeHierarchy.java:360) at org.eclipse.jdt.internal.core.DeltaProcessor$5.run(DeltaProcessor.java:1697) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.core.DeltaProcessor.notifyTypeHierarchies(DeltaProcessor.java:1688) at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:2081) at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:470) at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285) at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149) at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:395) at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1530) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2353) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) at org.eclipse.ui.internal.editors.text.WorkspaceOperationRunner.run(WorkspaceOperationRunner.java:75) at org.eclipse.ui.internal.editors.text.WorkspaceOperationRunner.run(WorkspaceOperationRunner.java:65) at org.eclipse.ui.editors.text.TextFileDocumentProvider.executeOperation(TextFileDocumentProvider.java:456) at org.eclipse.ui.editors.text.TextFileDocumentProvider.saveDocument(TextFileDocumentProvider.java:772) at org.eclipse.ui.texteditor.AbstractTextEditor.performSave(AbstractTextEditor.java:5048) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.performSave(CompilationUnitEditor.java:1247) at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.doSave(CompilationUnitEditor.java:1301) at org.eclipse.ui.texteditor.AbstractTextEditor$TextEditorSavable.doSave(AbstractTextEditor.java:7177) at org.eclipse.ui.Saveable.doSave(Saveable.java:214) at org.eclipse.ui.internal.SaveableHelper.doSaveModel(SaveableHelper.java:349) at org.eclipse.ui.internal.SaveableHelper$3.run(SaveableHelper.java:195) at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:277) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2642) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:285) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:264) at org.eclipse.ui.internal.SaveableHelper.saveModels(SaveableHelper.java:207) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:144) at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1399) at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:3416) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3429) at org.eclipse.ui.internal.handlers.SaveHandler.execute(SaveHandler.java:54) 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.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1262) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1104) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1098) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1509) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4640) at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:345) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4528) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) | resolved fixed | 4778eb2 | ["org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/util/SuperTypeHierarchyCache.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-09-27T08:24:06Z" | "2011-08-03T11:13:20Z" |
347,734 | Bug 347734 [typing] Angle brackets wrongly auto-closed when starting at the beginning of a line | Build Identifier: Version: 3.6.2, Build id: M20110210-1200 This happens only if the identifier is single letter. This happens only if the identifier is typed in the first column. I understand this is a rare scenario. But, text editors inherited from AbstractTextEditor will have the same behavior as well. That's why I raise this as a Minor bug. I guess, the problem might be in org.eclipse.jdt.internal.ui.text.JavaHeuristicScanner.scanBackward() method. Reproducible: Always Steps to Reproduce: 1. Open a Java editor. 2. Type "int x = 10;" in the class body. 3. Then try typing "x <" in the first column. 4. Even with the identifier context (i.e. x), angular brace is auto completed as "x <>". | verified fixed | c6d7766 | ["org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/BracketInserterTest.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitEditor.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-09-22T08:26:52Z" | "2011-05-31T08:20:00Z" |
89,432 | Bug 89432 [quick assist] Transform enhanced for-loop to iterator | I've often written iteration code using the enhanced for-loop initially, then later discovered I needed access to the Iterator to remove an object. It would be nice if Eclipse could do this simple (but verbose) transformation for me. For example: for (final Member member : list) { //... } becomes: for (final Iterator<Member> memberIter = list.iterator(); memberIter.hasNext(); ) { final Member member = memberIter.next(); // ... // if (foo) memberIter.remove(); } Similarly, the transformation could support arrays: for (final Member member : array) { // ... } becomes: for (int memberIndex = 0; memberIndex < array.length; ++memberIndex) { final Member member = array[memberIndex]; // ... // if (foo) member[memberIndex] = null; } Another variation would be creating a ListIterator for lists, to allow adding elements, or doing reverse iteration. | verified fixed | 4a41572 | ["org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AssistQuickFixTest.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/dom/Bindings.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/fix/LinkedProposalModel.java", "org.eclipse.jdt.ui/core", "extension/org/eclipse/jdt/internal/corext/fix/LinkedProposalPositionGroup.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMessages.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/QuickAssistProcessor.java", "org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/LinkedCorrectionProposal.java"] | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | "2011-09-09T19:08:31Z" | "2005-03-29T23:46:40Z" |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.