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 | 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 timestamp[us, tz=UTC] | report_datetime timestamp[us, tz=UTC] | updated_file stringlengths 2 187 | file_content stringlengths 0 368k |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
79,905 | Bug 79905 Move inner to top failed for enums | public class A { enum E { } } - try moving E to top java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(Unknown Source) at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(Unknown Source) at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(Unknown Source) at org.... | resolved fixed | 6cdb86d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-06T16:59:53Z | 2004-12-01T19:40:00Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInnerToTopRefactoring.java | |
78,053 | Bug 78053 Package Explorer shouldn't fetch any children on startup. [package explorer] | We have a custom classpath container that reads a properties file in a workspace project. A typical workspace has around 50 projects in it. When Eclipse is started it takes a long time to come up with such a workspace on a ClearCase dynamic view. It is slightly better with snapshot views. During debugging/tracing I not... | verified fixed | 40d89ad | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-06T17:29:28Z | 2004-11-08T10:33:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerPart.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
80,349 | Bug 80349 Extract Local Variable refactoring does not remember final state [refactoring] | I always use final for variables, which are not modified after initialization. When I use Extract Local Variable, I always need to toggle the switch, Eclipse just forgets my previous toggling. | resolved fixed | c762167 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-07T15:19:02Z | 2004-12-07T09:00:00Z | org.eclipse.jdt.ui/ui | |
80,349 | Bug 80349 Extract Local Variable refactoring does not remember final state [refactoring] | I always use final for variables, which are not modified after initialization. When I use Extract Local Variable, I always need to toggle the switch, Eclipse just forgets my previous toggling. | resolved fixed | c762167 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-07T15:19:02Z | 2004-12-07T09:00:00Z | refactoring/org/eclipse/jdt/internal/ui/refactoring/ExtractTempWizard.java | |
80,393 | Bug 80393 NPE in AllTypesCache.getTypes() | reported by Christof Marti: running performance tests on 3.0 resulted in the following NPE. It seems that AllTypesCache.getAllTypes can return null and that AllTypesCache.getTypes() doesn't check for this. java.lang.NullPointerException at org.eclipse.jdt.internal.corext.util.AllTypesCache.getTypes(AllTypesCache.java:2... | resolved fixed | 6514fd5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-08T11:22:55Z | 2004-12-07T17:20:00Z | org.eclipse.jdt.ui/core | |
80,393 | Bug 80393 NPE in AllTypesCache.getTypes() | reported by Christof Marti: running performance tests on 3.0 resulted in the following NPE. It seems that AllTypesCache.getAllTypes can return null and that AllTypesCache.getTypes() doesn't check for this. java.lang.NullPointerException at org.eclipse.jdt.internal.corext.util.AllTypesCache.getTypes(AllTypesCache.java:2... | resolved fixed | 6514fd5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-08T11:22:55Z | 2004-12-07T17:20:00Z | extension/org/eclipse/jdt/internal/corext/util/AllTypesCache.java | |
80,455 | Bug 80455 [5.0] ITypeBinding.canAssign not aware of type boxing | 20041208 With the latest changes for type boxing (in N20041207) our tests for the assign compatibility fail: boolean b= true; Object o; o= b; // valid code, no compiler error but typeBindingOfB.isAssignCompatible(typeBindingOfO) is false | verified fixed | 0db53df | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-08T11:42:05Z | 2004-12-08T12:46:40Z | org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/TypeRulesTest.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
80,573 | Bug 80573 Prepare project specific preference options | I200412081200 From Martin's e-mail: I deprecated some methods that access options that will soon be offered per project as well: CodeFormatterUtil.getTabWidth() -> CodeFormatterUtil.getTabWidth(IJavaProject) CodeFormatterUtil.createIndentString(int) -> CodeFormatterUtil.createIndentString(int, IJavaProject) JavaPrefere... | resolved fixed | 9d9b52d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-09T11:47:06Z | 2004-12-09T08:13:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/IndentAction.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
80,573 | Bug 80573 Prepare project specific preference options | I200412081200 From Martin's e-mail: I deprecated some methods that access options that will soon be offered per project as well: CodeFormatterUtil.getTabWidth() -> CodeFormatterUtil.getTabWidth(IJavaProject) CodeFormatterUtil.createIndentString(int) -> CodeFormatterUtil.createIndentString(int, IJavaProject) JavaPrefere... | resolved fixed | 9d9b52d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-09T11:47:06Z | 2004-12-09T08:13:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
80,573 | Bug 80573 Prepare project specific preference options | I200412081200 From Martin's e-mail: I deprecated some methods that access options that will soon be offered per project as well: CodeFormatterUtil.getTabWidth() -> CodeFormatterUtil.getTabWidth(IJavaProject) CodeFormatterUtil.createIndentString(int) -> CodeFormatterUtil.createIndentString(int, IJavaProject) JavaPrefere... | resolved fixed | 9d9b52d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-09T11:47:06Z | 2004-12-09T08:13:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaSourceViewer.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
80,573 | Bug 80573 Prepare project specific preference options | I200412081200 From Martin's e-mail: I deprecated some methods that access options that will soon be offered per project as well: CodeFormatterUtil.getTabWidth() -> CodeFormatterUtil.getTabWidth(IJavaProject) CodeFormatterUtil.createIndentString(int) -> CodeFormatterUtil.createIndentString(int, IJavaProject) JavaPrefere... | resolved fixed | 9d9b52d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-09T11:47:06Z | 2004-12-09T08:13:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/JavaIndenter.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
80,573 | Bug 80573 Prepare project specific preference options | I200412081200 From Martin's e-mail: I deprecated some methods that access options that will soon be offered per project as well: CodeFormatterUtil.getTabWidth() -> CodeFormatterUtil.getTabWidth(IJavaProject) CodeFormatterUtil.createIndentString(int) -> CodeFormatterUtil.createIndentString(int, IJavaProject) JavaPrefere... | resolved fixed | 9d9b52d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-09T11:47:06Z | 2004-12-09T08:13:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaAutoIndentStrategy.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
80,573 | Bug 80573 Prepare project specific preference options | I200412081200 From Martin's e-mail: I deprecated some methods that access options that will soon be offered per project as well: CodeFormatterUtil.getTabWidth() -> CodeFormatterUtil.getTabWidth(IJavaProject) CodeFormatterUtil.createIndentString(int) -> CodeFormatterUtil.createIndentString(int, IJavaProject) JavaPrefere... | resolved fixed | 9d9b52d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-09T11:47:06Z | 2004-12-09T08:13:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/JavaSourceViewerConfiguration.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
77,964 | Bug 77964 Compiler settings defaults not compatible with our 'default' | 20041105 When starting a fresh workbench, open the compiler preference page. The compliance settings (compliance, classfile comp. source comp, enum and assert) are all initialized with the default provided by JDT core. Unfortunatly the 'default' check box is not checked as the last enum is set to warning. Can you set '... | resolved fixed | e8cfbd9 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-09T14:41:52Z | 2004-11-05T15:53:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ComplianceConfigurationBlock.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
74,627 | Bug 74627 [typing] Importing Type leaves linked editing mode | 3.1 M2: - use for-loop over collection template to enter linked editing mode - step to "type" - type Set - use quick fix to import java.util.Set Observe: linked edit mode is exited | resolved fixed | 77fd1a4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-09T15:59:36Z | 2004-09-22T16:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/AddImportOnSelectionAction.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
74,627 | Bug 74627 [typing] Importing Type leaves linked editing mode | 3.1 M2: - use for-loop over collection template to enter linked editing mode - step to "type" - type Set - use quick fix to import java.util.Set Observe: linked edit mode is exited | resolved fixed | 77fd1a4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-09T15:59:36Z | 2004-09-22T16:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OrganizeImportsAction.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
77,615 | Bug 77615 Move member to new file ignores reference to type parameter [refactoring] [move] | M3 test candidate public class A<T> { static class Inner<X> extends ArrayList<T> { public void foo() { X x= null; } } } - move inner to new file Observe: no error although type parameter T isn't visible in new file. | resolved fixed | 9a468a1 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-10T17:44:10Z | 2004-11-03T13:53:20Z | org.eclipse.jdt.ui/core | |
77,615 | Bug 77615 Move member to new file ignores reference to type parameter [refactoring] [move] | M3 test candidate public class A<T> { static class Inner<X> extends ArrayList<T> { public void foo() { X x= null; } } } - move inner to new file Observe: no error although type parameter T isn't visible in new file. | resolved fixed | 9a468a1 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-10T17:44:10Z | 2004-11-03T13:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInnerToTopRefactoring.java | |
80,715 | Bug 80715 ITypeBinding#isAssignmentCompatible(..) doesn't work across binding resolvers | I200412081200 We tried to replace our TypeRules#canAssign(..) method by ITypeBinding#isAssignmentCompatible(..). This resulted in many test failures in UseSupertypeWherePossibleTests and ExtractInterfaceTests. The reason is that isAssignmentCompatible(..) doesn't work corrctly with bindings that are isEqualTo(..), but ... | resolved wontfix | 8e81af5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-10T18:28:54Z | 2004-12-10T17:33:20Z | org.eclipse.jdt.ui/core | |
80,715 | Bug 80715 ITypeBinding#isAssignmentCompatible(..) doesn't work across binding resolvers | I200412081200 We tried to replace our TypeRules#canAssign(..) method by ITypeBinding#isAssignmentCompatible(..). This resulted in many test failures in UseSupertypeWherePossibleTests and ExtractInterfaceTests. The reason is that isAssignmentCompatible(..) doesn't work corrctly with bindings that are isEqualTo(..), but ... | resolved wontfix | 8e81af5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-10T18:28:54Z | 2004-12-10T17:33:20Z | extension/org/eclipse/jdt/internal/corext/dom/TypeRules.java | |
66,354 | Bug 66354 [quick fix] incorrect placement of new temp decl [quick fix] | 3.0rc1 void foo(Object x) { if (x != null) foo= x.toString(); } select foo, choose 'create local variable foo' you get: void foo(Object x) { if (x != null)String foo = x.toString(); } which is somewhat suboptimal :) | resolved fixed | 40e025a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T15:08:04Z | 2004-06-09T16:53:20Z | org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedVariablesQuickFixTest.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
66,354 | Bug 66354 [quick fix] incorrect placement of new temp decl [quick fix] | 3.0rc1 void foo(Object x) { if (x != null) foo= x.toString(); } select foo, choose 'create local variable foo' you get: void foo(Object x) { if (x != null)String foo = x.toString(); } which is somewhat suboptimal :) | resolved fixed | 40e025a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T15:08:04Z | 2004-06-09T16:53:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/NewVariableCompletionProposal.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
66,394 | Bug 66394 missing parenthesis in method call [quick fix] | 3.0rc1 int f(){ return foo; } private int foo() { return 0; } the reference to foo is no good. there are parantheses missing. amongst the many quick fixes offered, this obvious one is missing. | resolved fixed | a326d45 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T19:29:19Z | 2004-06-09T19:40:00Z | org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedVariablesQuickFixTest.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
66,394 | Bug 66394 missing parenthesis in method call [quick fix] | 3.0rc1 int f(){ return foo; } private int foo() { return 0; } the reference to foo is no good. there are parantheses missing. amongst the many quick fixes offered, this obvious one is missing. | resolved fixed | a326d45 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T19:29:19Z | 2004-06-09T19:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/UnresolvedElementsSubProcessor.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
66,946 | Bug 66946 JavaDoc wizard forgets about options on 3rd page [javadoc] | 3.0RC2 The options: - JRE 1.4 source compat. - Save the settings... (the checkbox) - Open generated index file in browser are not remembered in (or reloaded from?) the javadoc.xml when rerunning the wizard. | resolved fixed | 9eb47d8 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T20:01:24Z | 2004-06-14T13:33:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocOptionsManager.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
66,946 | Bug 66946 JavaDoc wizard forgets about options on 3rd page [javadoc] | 3.0RC2 The options: - JRE 1.4 source compat. - Save the settings... (the checkbox) - Open generated index file in browser are not remembered in (or reloaded from?) the javadoc.xml when rerunning the wizard. | resolved fixed | 9eb47d8 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T20:01:24Z | 2004-06-14T13:33:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocWizard.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
68,582 | Bug 68582 mass organize import modifies read only files | 1. Create a scratch project 2. create 2 files A.java and B.java 3. put unused import in both files. 4. Open file A for editing. 5. make file A read-only 6. open file B for editing. 7. Perform organize imports on the whole project 8. Observe file A is marked as dirty and if you try and save it there is a complaint. | resolved fixed | 73570cd | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T20:43:22Z | 2004-06-25T10:40:00Z | org.eclipse.jdt.ui/core | |
68,582 | Bug 68582 mass organize import modifies read only files | 1. Create a scratch project 2. create 2 files A.java and B.java 3. put unused import in both files. 4. Open file A for editing. 5. make file A read-only 6. open file B for editing. 7. Perform organize imports on the whole project 8. Observe file A is marked as dirty and if you try and save it there is a complaint. | resolved fixed | 73570cd | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T20:43:22Z | 2004-06-25T10:40:00Z | extension/org/eclipse/jdt/internal/corext/codemanipulation/ImportsStructure.java | |
77,586 | Bug 77586 Build Path inclusion filters: filter language must be explained | null | resolved fixed | 9981408 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T22:36:14Z | 2004-11-03T11:06:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/TypeRestrictionDialog.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
77,586 | Bug 77586 Build Path inclusion filters: filter language must be explained | null | resolved fixed | 9981408 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T22:36:14Z | 2004-11-03T11:06:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/TypeRestrictionEntryDialog.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
80,774 | Bug 80774 NPE in Quick Fix | I20041208 + latest plug-in export java.lang.NullPointerException at org.eclipse.jdt.internal.ui.text.correction.AdvancedQuickAssistProcessor.getFullyCoveredNodes(AdvancedQuickAssistProcessor.java:735) at org.eclipse.jdt.internal.ui.text.correction.AdvancedQuickAssistProcessor.getAssists(AdvancedQuickAssistProcessor.jav... | resolved fixed | b2707e2 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T22:47:17Z | 2004-12-12T14:00:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
78,880 | Bug 78880 [refactoring] self encapsulate field: exception on name 'fPackage' | 3.0 i have a field called fPackage (prefixes set to 'f') i wanted to encapsulate it. i accepted the default getter setter names, set 'refs in same class - use field direct references' and i got: (seems like the name has something to do with it.) java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation... | resolved fixed | 003512a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T23:26:26Z | 2004-11-17T19:33:20Z | org.eclipse.jdt.ui/core | |
78,880 | Bug 78880 [refactoring] self encapsulate field: exception on name 'fPackage' | 3.0 i have a field called fPackage (prefixes set to 'f') i wanted to encapsulate it. i accepted the default getter setter names, set 'refs in same class - use field direct references' and i got: (seems like the name has something to do with it.) java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation... | resolved fixed | 003512a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T23:26:26Z | 2004-11-17T19:33:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/sef/SelfEncapsulateFieldRefactoring.java | |
79,278 | Bug 79278 Selfencapsulate Field does not support annotations [refactoring] | I20041117: Create annotation: public @interface Annotation { int property; } Invoke sef refactoring on "property" -> property is private (illegal modifier in annotations) and accessor is static and has method body. Apart from generating an accessor, sef is not of much value for annotations, so we might disable it. | resolved fixed | 5bdbcd5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T23:53:55Z | 2004-11-23T14:26:40Z | org.eclipse.jdt.ui.tests.refactoring/resources/SefWorkSpace/SefTests/invalid/TestAnnotation.java | |
79,278 | Bug 79278 Selfencapsulate Field does not support annotations [refactoring] | I20041117: Create annotation: public @interface Annotation { int property; } Invoke sef refactoring on "property" -> property is private (illegal modifier in annotations) and accessor is static and has method body. Apart from generating an accessor, sef is not of much value for annotations, so we might disable it. | resolved fixed | 5bdbcd5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T23:53:55Z | 2004-11-23T14:26:40Z | org.eclipse.jdt.ui.tests.refactoring/test | |
79,278 | Bug 79278 Selfencapsulate Field does not support annotations [refactoring] | I20041117: Create annotation: public @interface Annotation { int property; } Invoke sef refactoring on "property" -> property is private (illegal modifier in annotations) and accessor is static and has method body. Apart from generating an accessor, sef is not of much value for annotations, so we might disable it. | resolved fixed | 5bdbcd5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T23:53:55Z | 2004-11-23T14:26:40Z | cases/org/eclipse/jdt/ui/tests/refactoring/SefTests.java | |
79,278 | Bug 79278 Selfencapsulate Field does not support annotations [refactoring] | I20041117: Create annotation: public @interface Annotation { int property; } Invoke sef refactoring on "property" -> property is private (illegal modifier in annotations) and accessor is static and has method body. Apart from generating an accessor, sef is not of much value for annotations, so we might disable it. | resolved fixed | 5bdbcd5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T23:53:55Z | 2004-11-23T14:26:40Z | org.eclipse.jdt.ui/core | |
79,278 | Bug 79278 Selfencapsulate Field does not support annotations [refactoring] | I20041117: Create annotation: public @interface Annotation { int property; } Invoke sef refactoring on "property" -> property is private (illegal modifier in annotations) and accessor is static and has method body. Apart from generating an accessor, sef is not of much value for annotations, so we might disable it. | resolved fixed | 5bdbcd5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T23:53:55Z | 2004-11-23T14:26:40Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/sef/SelfEncapsulateFieldRefactoring.java | |
79,278 | Bug 79278 Selfencapsulate Field does not support annotations [refactoring] | I20041117: Create annotation: public @interface Annotation { int property; } Invoke sef refactoring on "property" -> property is private (illegal modifier in annotations) and accessor is static and has method body. Apart from generating an accessor, sef is not of much value for annotations, so we might disable it. | resolved fixed | 5bdbcd5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-12T23:53:55Z | 2004-11-23T14:26:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/SelfEncapsulateFieldAction.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
77,649 | Bug 77649 'Refactor -> Undo' enabled after consecutive change | I200411022000 Having: package test2; public class A { public C c= new C(); public void foo() { } } package test2; public class B { public void bar() { new A().foo(); } } package test2; public class C { } and: - open all 3 CUs - move A#foo() to C - remove 'a' from 'new A().c.foo(a);' in B - save B - Refactor -> Undo -> ... | resolved fixed | 2a8f1e6 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T06:55:33Z | 2004-11-03T16:40:00Z | org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/IUndoManager.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
77,649 | Bug 77649 'Refactor -> Undo' enabled after consecutive change | I200411022000 Having: package test2; public class A { public C c= new C(); public void foo() { } } package test2; public class B { public void bar() { new A().foo(); } } package test2; public class C { } and: - open all 3 CUs - move A#foo() to C - remove 'a' from 'new A().c.foo(a);' in B - save B - Refactor -> Undo -> ... | resolved fixed | 2a8f1e6 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T06:55:33Z | 2004-11-03T16:40:00Z | org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/core/refactoring/PerformChangeOperation.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
77,649 | Bug 77649 'Refactor -> Undo' enabled after consecutive change | I200411022000 Having: package test2; public class A { public C c= new C(); public void foo() { } } package test2; public class B { public void bar() { new A().foo(); } } package test2; public class C { } and: - open all 3 CUs - move A#foo() to C - remove 'a' from 'new A().c.foo(a);' in B - save B - Refactor -> Undo -> ... | resolved fixed | 2a8f1e6 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T06:55:33Z | 2004-11-03T16:40:00Z | org.eclipse.ltk.core.refactoring/src/org/eclipse/ltk/internal/core/refactoring/UndoManager.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
80,037 | Bug 80037 remove references to EnumConstandDeclaration#bodyDeclaraions | null | resolved fixed | f21f43d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T10:13:01Z | 2004-12-02T17:53:20Z | org.eclipse.jdt.ui/core | |
80,037 | Bug 80037 remove references to EnumConstandDeclaration#bodyDeclaraions | null | resolved fixed | f21f43d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T10:13:01Z | 2004-12-02T17:53:20Z | extension/org/eclipse/jdt/internal/corext/dom/ASTFlattener.java | |
80,037 | Bug 80037 remove references to EnumConstandDeclaration#bodyDeclaraions | null | resolved fixed | f21f43d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T10:13:01Z | 2004-12-02T17:53:20Z | org.eclipse.jdt.ui/core | |
80,037 | Bug 80037 remove references to EnumConstandDeclaration#bodyDeclaraions | null | resolved fixed | f21f43d | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T10:13:01Z | 2004-12-02T17:53:20Z | extension/org/eclipse/jdt/internal/corext/dom/ASTNodes.java | |
80,784 | Bug 80784 NPE in TestHierarchyTab.cacheItems [JUnit] | I20041208 + plug-in export java.lang.NullPointerException at org.eclipse.jdt.internal.junit.ui.TestHierarchyTab.cacheItems(TestHierarchyTab.java:296) at org.eclipse.jdt.internal.junit.ui.TestHierarchyTab.endTest(TestHierarchyTab.java:287) at org.eclipse.jdt.internal.junit.ui.TestRunnerViewPart$6.run(TestRunnerViewPart.... | resolved fixed | cf31e67 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T12:53:15Z | 2004-12-12T22:20:00Z | org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestHierarchyTab.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/util/TestSearchEngine.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/OpenEditorAtLineAction.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestMethodSelectionDialog.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/util/TestSearchEngine.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/RenameTypeTests.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | extension/org/eclipse/jdt/internal/corext/callhierarchy/CallerMethodWrapper.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | extension/org/eclipse/jdt/internal/corext/util/SearchUtils.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringSearchEngine.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringSearchEngine2.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceFactoryRefactoring.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceParameterRefactoring.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/TargetProvider.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameFieldProcessor.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameMethodProcessor.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameNonVirtualMethodProcessor.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameTypeProcessor.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/CreateCopyOfCompilationUnitChange.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ChangeTypeRefactoring.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ConstructorReferenceFinder.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ExtractInterfaceUtil.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/HierarchyRefactoring.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MemberVisibilityAdjustor.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInnerToTopRefactoring.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInstanceMethodProcessor.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveStaticMembersProcessor.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/core | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PushDownRefactoring.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/ui | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/search/NLSSearchQuery.java | |
79,790 | Bug 79790 [1.5][search] Need to distinguish between raw and restricted search in the case of instantiated types | I20041130 Code select now return a special IJavaElement when resolving code list List<String>. If we hand such an element over to the search engine we need means to distinguish between searches for List and searches for List<String>. One idea is to add additional flags to SearchPattern. | verified fixed | 30ecdfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T17:19:05Z | 2004-11-30T15:53:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/JavaSearchQuery.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
77,849 | Bug 77849 [1.5][wizard] Java project wizard does only create projects for 1.4 | Currently, new java projects default to 1.4 compliance. In order to develop 1.5 projects, the JRE container has to be changed, and the compiler compliance as well, but at two different places in the project properties. The new project wizard already offers a page to choose the JRE container. The compiler compliance how... | resolved fixed | d5169b7 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T18:14:51Z | 2004-11-04T17:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/ChangeComplianceDialog.java | |
77,849 | Bug 77849 [1.5][wizard] Java project wizard does only create projects for 1.4 | Currently, new java projects default to 1.4 compliance. In order to develop 1.5 projects, the JRE container has to be changed, and the compiler compliance as well, but at two different places in the project properties. The new project wizard already offers a page to choose the JRE container. The compiler compliance how... | resolved fixed | d5169b7 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-12-13T18:14:51Z | 2004-11-04T17:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/JavaProjectWizard.java | /*******************************************************************************
* Copyright (c) 2000, 2004 IBM Corporation and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v1.0
* which accompanies this distribution, an... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.