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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
47,207 | Bug 47207 call hierarchy: Enablement of "Search Scope" item on view menu is wrong [call hierarchy] | At least on Windows NT/2000 this item is shown as disabled until the user clicks it it which case the submenu opens. I have been looking into this problem but without any results so far. Any suggestions are welcome. | resolved fixed | 675825b | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T18:44:41Z | 2003-11-21T10:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/SearchScopeProjectAction.java | |
47,207 | Bug 47207 call hierarchy: Enablement of "Search Scope" item on view menu is wrong [call hierarchy] | At least on Windows NT/2000 this item is shown as disabled until the user clicks it it which case the submenu opens. I have been looking into this problem but without any results so far. Any suggestions are welcome. | resolved fixed | 675825b | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T18:44:41Z | 2003-11-21T10:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/SearchScopeWorkingSetAction.java | |
47,207 | Bug 47207 call hierarchy: Enablement of "Search Scope" item on view menu is wrong [call hierarchy] | At least on Windows NT/2000 this item is shown as disabled until the user clicks it it which case the submenu opens. I have been looking into this problem but without any results so far. Any suggestions are welcome. | resolved fixed | 675825b | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T18:44:41Z | 2003-11-21T10:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/SearchScopeWorkspaceAction.java | |
47,207 | Bug 47207 call hierarchy: Enablement of "Search Scope" item on view menu is wrong [call hierarchy] | At least on Windows NT/2000 this item is shown as disabled until the user clicks it it which case the submenu opens. I have been looking into this problem but without any results so far. Any suggestions are welcome. | resolved fixed | 675825b | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T18:44:41Z | 2003-11-21T10:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/SearchUtil.java | |
47,207 | Bug 47207 call hierarchy: Enablement of "Search Scope" item on view menu is wrong [call hierarchy] | At least on Windows NT/2000 this item is shown as disabled until the user clicks it it which case the submenu opens. I have been looking into this problem but without any results so far. Any suggestions are welcome. | resolved fixed | 675825b | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T18:44:41Z | 2003-11-21T10:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/SelectWorkingSetAction.java | |
48,325 | Bug 48325 introduce parameter throws NPE if there are compiler errors [refactoring] | I200312020950 in the file below introduce the "3" as a parameter. -------------------------------------------------- class A { void method() { } void method() { int x = 3; //<-- introduce 3 as a parameter } } ---------------------------------------------------- the result is: -------------------------------------------... | resolved fixed | 321e262 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T19:20:47Z | 2003-12-09T08:53:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/IntroduceParameter/invalid/NoMethodBinding.java | |
48,325 | Bug 48325 introduce parameter throws NPE if there are compiler errors [refactoring] | I200312020950 in the file below introduce the "3" as a parameter. -------------------------------------------------- class A { void method() { } void method() { int x = 3; //<-- introduce 3 as a parameter } } ---------------------------------------------------- the result is: -------------------------------------------... | resolved fixed | 321e262 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T19:20:47Z | 2003-12-09T08:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
48,325 | Bug 48325 introduce parameter throws NPE if there are compiler errors [refactoring] | I200312020950 in the file below introduce the "3" as a parameter. -------------------------------------------------- class A { void method() { } void method() { int x = 3; //<-- introduce 3 as a parameter } } ---------------------------------------------------- the result is: -------------------------------------------... | resolved fixed | 321e262 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T19:20:47Z | 2003-12-09T08:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/IntroduceParameterTests.java | |
48,325 | Bug 48325 introduce parameter throws NPE if there are compiler errors [refactoring] | I200312020950 in the file below introduce the "3" as a parameter. -------------------------------------------------- class A { void method() { } void method() { int x = 3; //<-- introduce 3 as a parameter } } ---------------------------------------------------- the result is: -------------------------------------------... | resolved fixed | 321e262 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T19:20:47Z | 2003-12-09T08:53:20Z | org.eclipse.jdt.ui/core | |
48,325 | Bug 48325 introduce parameter throws NPE if there are compiler errors [refactoring] | I200312020950 in the file below introduce the "3" as a parameter. -------------------------------------------------- class A { void method() { } void method() { int x = 3; //<-- introduce 3 as a parameter } } ---------------------------------------------------- the result is: -------------------------------------------... | resolved fixed | 321e262 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-16T19:20:47Z | 2003-12-09T08:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/IntroduceParameterRefactoring.java | |
52,275 | Bug 52275 Package Explorer error marker icon not updated | I have a custom builder which is invoked after a save (CTRL+S) that identifies problems with resources in my non-Java project and marks the resource with errors (or clears them as needed). This seems to work fine except that the problem marker icons in the Package Explorer are for some reason not automatically updated.... | resolved fixed | d3694f6 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T09:29:41Z | 2004-02-17T17:46:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/ProblemMarkerManager.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
48,482 | Bug 48482 Wording on "File Search" page | I20031203 The button next to the "File Name Patterns" combo is labeled "Browse...". A more appropriate term would be "Choose..." (identical to the term used for the Scope). For me "Browsing" is more associated with exploring a network or a filesystem but not for picking an item from a list. | resolved fixed | a0b6315 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T09:44:39Z | 2003-12-11T13:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/JavaSearchResultPage.java | |
32,378 | Bug 32378 Java Build Path properties page [general issue] [build path] | The Java Build Path properties page should refresh when it is opened and should also have an apply button. We are running into problems because we also contribute a properties page to Java projects that edits the build properties and it is unclear what the current state of the build path is. There are two main problems... | closed fixed | a0ed6d5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T15:34:07Z | 2003-02-20T19:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/BuildPathDialog.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
32,378 | Bug 32378 Java Build Path properties page [general issue] [build path] | The Java Build Path properties page should refresh when it is opened and should also have an apply button. We are running into problems because we also contribute a properties page to Java projects that edits the build properties and it is unclear what the current state of the build path is. There are two main problems... | closed fixed | a0ed6d5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T15:34:07Z | 2003-02-20T19:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/BuildPathsPropertyPage.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
32,378 | Bug 32378 Java Build Path properties page [general issue] [build path] | The Java Build Path properties page should refresh when it is opened and should also have an apply button. We are running into problems because we also contribute a properties page to Java projects that edits the build properties and it is unclear what the current state of the build path is. There are two main problems... | closed fixed | a0ed6d5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T15:34:07Z | 2003-02-20T19:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/BuildPathsBlock.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
32,378 | Bug 32378 Java Build Path properties page [general issue] [build path] | The Java Build Path properties page should refresh when it is opened and should also have an apply button. We are running into problems because we also contribute a properties page to Java projects that edits the build properties and it is unclear what the current state of the build path is. There are two main problems... | closed fixed | a0ed6d5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T15:34:07Z | 2003-02-20T19:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/CPListElement.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
32,378 | Bug 32378 Java Build Path properties page [general issue] [build path] | The Java Build Path properties page should refresh when it is opened and should also have an apply button. We are running into problems because we also contribute a properties page to Java projects that edits the build properties and it is unclear what the current state of the build path is. There are two main problems... | closed fixed | a0ed6d5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T15:34:07Z | 2003-02-20T19:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/JavaCapabilityConfigurationPage.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
32,378 | Bug 32378 Java Build Path properties page [general issue] [build path] | The Java Build Path properties page should refresh when it is opened and should also have an apply button. We are running into problems because we also contribute a properties page to Java projects that edits the build properties and it is unclear what the current state of the build path is. There are two main problems... | closed fixed | a0ed6d5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T15:34:07Z | 2003-02-20T19:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPage.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
37,513 | Bug 37513 [misc] Outline tool-tip window should remember size and position | It would be very nice if the Outline window (accessible from Ctrl+O or the menu "Navigate|Show Outline") would remember its size and position like most other windows in Eclipse do. | resolved fixed | 54d3604 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T16:39:44Z | 2003-05-12T17:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/AbstractInformationControl.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
37,513 | Bug 37513 [misc] Outline tool-tip window should remember size and position | It would be very nice if the Outline window (accessible from Ctrl+O or the menu "Navigate|Show Outline") would remember its size and position like most other windows in Eclipse do. | resolved fixed | 54d3604 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T16:39:44Z | 2003-05-12T17:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/JavaSourceViewerConfiguration.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
51,609 | Bug 51609 Not all interfaces shown in Type Hierarchy | I200402102000 Open Type Hierarchy on package junit.framework. Observe: only one interface instead of three is shown. Nothing in .log | verified fixed | 8f438b2 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-18T16:44:36Z | 2004-02-11T11:46:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/typehierarchy/TraditionalHierarchyViewer.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
52,460 | Bug 52460 [spell checking] Spell check index out of range | I was running in console mode for other reasons, when I spotted this stack trace, that did not appear in the log. This is in M7; JDK 1.4.2_03. I just turned on spell checking in the In Progress pref pane but didn't otherwise do anything to configure. I don't know what specific action triggered this (nor did I observe a... | verified fixed | 8f50f86 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T09:18:01Z | 2004-02-19T08:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/spelling/SpellCheckIterator.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots1/in/srcPrg/p/p/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots1/in/srcTest/p/p/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots1/in/srcTest/tests/AllTests.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots1/out/srcPrg/q/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots1/out/srcTest/p/p/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots1/out/srcTest/tests/AllTests.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/in/srcPrg/p/p/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/in/srcTest/p/p/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/in/srcTest/p/p/TestHelper.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/in/srcTest/tests/AllTests.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/in/srcTest/tests/QualifiedTests.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/out/srcPrg/q/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/out/srcTest/p/p/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/out/srcTest/p/p/TestHelper.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/out/srcTest/tests/AllTests.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots2/out/srcTest/tests/QualifiedTests.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots3/in/srcPrg/p/p/ToQ.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots3/in/srcTest/p/p/Ref.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots3/out/srcPrg/q/ToQ.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots3/out/srcTest/p/p/Ref.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots4/in/srcPrg/p/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots4/in/srcPrg/p/B.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots4/in/srcTest/p/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots4/out/srcPrg/a/b/c/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots4/out/srcPrg/a/b/c/B.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots4/out/srcTest/p/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots5/in/srcPrg/p/p/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots5/in/srcTest/p/p/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots5/out/srcPrg/p/p/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots5/out/srcTest/q/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots6/in/srcPrg/p/p/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots6/in/srcTest/p/p/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots6/out/srcPrg/p/p/A.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots6/out/srcTest/cheese/ATest.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots7/in/srcPrj.other/pack/Namesake.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots7/in/srcPrj.ref/pack/Referer.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots7/in/srcPrj.ref/pack/man/StarImporter.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots7/in/srcPrj/pack/DingsDa.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots7/out/srcPrj.other/pack/Namesake.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots7/out/srcPrj.ref/pack/Referer.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots7/out/srcPrj.ref/pack/man/StarImporter.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/RenamePackage/testImportFromMultiRoots7/out/srcPrj/com/packt/DingsDa.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/RenamePackageTests.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui/core | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RefactoringScopeFactory.java | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | org.eclipse.jdt.ui/core | |
47,509 | Bug 47509 Refactor name of package fragment does not handle on demand import | Build Eclipse 2.1.2 On the following setup, select package fragment 'p' located in project B and rename it into 'q'. It will rename the 'import p.*;' statement, but did not realize there was still a use for it due to other fragment. It should have inserted an extra import during the rename action. Project A +- package ... | verified fixed | 9186dd4 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-19T14:22:48Z | 2003-11-26T12:33:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenamePackageProcessor.java | |
52,310 | Bug 52310 [Refactor] Moving a class from default package has missing "." from imports | Moved a class from the default package and ended up with imports missing the last ".". For example: I got something like org.eclipseMovedClass instead of org.eclipse.MovedClass | resolved fixed | 9dd8937 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-20T14:15:53Z | 2004-02-17T23:20:00Z | org.eclipse.jdt.ui.tests.refactoring/test | |
52,310 | Bug 52310 [Refactor] Moving a class from default package has missing "." from imports | Moved a class from the default package and ended up with imports missing the last ".". For example: I got something like org.eclipseMovedClass instead of org.eclipse.MovedClass | resolved fixed | 9dd8937 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-20T14:15:53Z | 2004-02-17T23:20:00Z | cases/org/eclipse/jdt/ui/tests/reorg/MoveTest.java | |
52,310 | Bug 52310 [Refactor] Moving a class from default package has missing "." from imports | Moved a class from the default package and ended up with imports missing the last ".". For example: I got something like org.eclipseMovedClass instead of org.eclipse.MovedClass | resolved fixed | 9dd8937 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-20T14:15:53Z | 2004-02-17T23:20:00Z | org.eclipse.jdt.ui/core | |
52,310 | Bug 52310 [Refactor] Moving a class from default package has missing "." from imports | Moved a class from the default package and ended up with imports missing the last ".". For example: I got something like org.eclipseMovedClass instead of org.eclipse.MovedClass | resolved fixed | 9dd8937 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-20T14:15:53Z | 2004-02-17T23:20:00Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/reorg/MoveCuUpdateCreator.java | |
51,954 | Bug 51954 IOException while generating Javadoc | M7 build Try to generate Javadoc for the package org.eclipse.jdt.internal.corext.refactoring.participants.xml. java.io.IOException: CreateProcess: C:\apps\java\jdk1.4.2\bin\javadoc.exe -d c:\tmp\testdoc - sourcepath "C:\home\dbaeumer\devel\workspaces\eclipse\3.0new\org.eclipse.jdt.ui \ui;C:\home\dbaeumer\devel\workspac... | resolved fixed | 47eda9e | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-20T19:00:50Z | 2004-02-13T13:46:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocOptionsManager.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
51,954 | Bug 51954 IOException while generating Javadoc | M7 build Try to generate Javadoc for the package org.eclipse.jdt.internal.corext.refactoring.participants.xml. java.io.IOException: CreateProcess: C:\apps\java\jdk1.4.2\bin\javadoc.exe -d c:\tmp\testdoc - sourcepath "C:\home\dbaeumer\devel\workspaces\eclipse\3.0new\org.eclipse.jdt.ui \ui;C:\home\dbaeumer\devel\workspac... | resolved fixed | 47eda9e | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-20T19:00:50Z | 2004-02-13T13:46:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocSpecificsWizardPage.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
51,954 | Bug 51954 IOException while generating Javadoc | M7 build Try to generate Javadoc for the package org.eclipse.jdt.internal.corext.refactoring.participants.xml. java.io.IOException: CreateProcess: C:\apps\java\jdk1.4.2\bin\javadoc.exe -d c:\tmp\testdoc - sourcepath "C:\home\dbaeumer\devel\workspaces\eclipse\3.0new\org.eclipse.jdt.ui \ui;C:\home\dbaeumer\devel\workspac... | resolved fixed | 47eda9e | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-20T19:00:50Z | 2004-02-13T13:46:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocWizard.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
52,750 | Bug 52750 correct indentation messes with comment boxes | 3m7 /* ******** */ /* */ /* ******** */ comes out /* ******** */ /* */ /* ******** */ | resolved fixed | 32c050f | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T10:50:49Z | 2004-02-21T21:46:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/IndentAction.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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, and... |
47,316 | Bug 47316 [Junit] Add support to run/re-run an individual test which requires some setup | (based on a discussion with Dirk) The JUnit plug-in supports to run or re-run a single test. However, this only works for simple tests which don't depend on being decorated by some setup. In the case of decorated test suites you always have to run the entire suite and you cannot run an individual test. Proposal: A deco... | resolved fixed | d16ecfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:55:30Z | 2003-11-23T20:40:00Z | org.eclipse.jdt.ui.tests.refactoring/test | |
47,316 | Bug 47316 [Junit] Add support to run/re-run an individual test which requires some setup | (based on a discussion with Dirk) The JUnit plug-in supports to run or re-run a single test. However, this only works for simple tests which don't depend on being decorated by some setup. In the case of decorated test suites you always have to run the entire suite and you cannot run an individual test. Proposal: A deco... | resolved fixed | d16ecfa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:55:30Z | 2003-11-23T20:40:00Z | cases/org/eclipse/jdt/ui/tests/refactoring/ExtractTempTests.java | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | org.eclipse.jdt.ui/core | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractConstantRefactoring.java | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | org.eclipse.jdt.ui/core | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodAnalyzer.java | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | org.eclipse.jdt.ui/core | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodRefactoring.java | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | org.eclipse.jdt.ui/core | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractTempRefactoring.java | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | org.eclipse.jdt.ui/ui | |
52,352 | Bug 52352 refactor: extract local variable: default: no selection of ... for literal expressions | When I am extracting a local variable from a trivial/literal expression, e.g. true, 100, ... I do NOT want to replace occurrences of that expression, because the next expression e.g. true may have a totally independent/orthogonal semantic and value. In all other cases (complex expressions) the current default is o.k. b... | resolved fixed | 5c5c2ca | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T11:58:56Z | 2004-02-18T10:26:40Z | refactoring/org/eclipse/jdt/internal/ui/refactoring/code/ExtractMethodInputPage.java | |
52,476 | Bug 52476 [painting] redraw behavior | build M7 Annotated method AnnotationPainter.handleDrawRequest with a repaint counter. 1) Open TestCase.java 2) add line >String s= < to tearDown method, set caret at end of line 3) spell checking enabled, otherwise default settings 3) type a single space -> 1 immediate repaint, 3 after timeout 4) type " -> auto inserte... | resolved fixed | 4f2336a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T13:51:48Z | 2004-02-19T14:13:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/link/LinkedUIControl.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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, and... |
52,361 | Bug 52361 [templates] linked mode not exited / annotations not redrawn when inserting anonymous completion | M7 0. Auto-closed parenthesis on 1. Insert this code: import java.lang.Runnable; void m() { method(<caret> } -> closing parenthesis gets inserted -> linked mode entered 2. type "new Runnable(" -> nested linked mode is entered for second parenthesis, also autoclosed 3. use code completion to complete the anonymous type ... | verified fixed | 7413ec3 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T14:37:32Z | 2004-02-18T16:00:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/link/LinkedPositionAnnotations.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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, and... |
52,361 | Bug 52361 [templates] linked mode not exited / annotations not redrawn when inserting anonymous completion | M7 0. Auto-closed parenthesis on 1. Insert this code: import java.lang.Runnable; void m() { method(<caret> } -> closing parenthesis gets inserted -> linked mode entered 2. type "new Runnable(" -> nested linked mode is entered for second parenthesis, also autoclosed 3. use code completion to complete the anonymous type ... | verified fixed | 7413ec3 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T14:37:32Z | 2004-02-18T16:00:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/link/LinkedUIControl.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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, and... |
52,470 | Bug 52470 CallHierarchy: SourceLocation View doesn't deliver IJavaElement selection | M7 Steps: - Open Java Browsing Perspective - Open CallHierarchy - single-click on source location -> observe: JavaBrowsing Views lose their JavaElement I guess it's because there's no SelectionProviderMediator which delivers IJavaElements for selected source positions. | resolved fixed | 7d6c359 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T14:53:03Z | 2004-02-19T11:26:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/CallHierarchyUI.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
52,801 | Bug 52801 "Press F2 for focus" does not work for spell-checking hovers | "Press F2 for focus" does not work for spell-checking hovers. | resolved fixed | 4c0b449 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T15:22:14Z | 2004-02-23T09:53:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
52,257 | Bug 52257 NPE in org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.getSignedSelection | I'm editing Java and doing CVS. A dialog box comes up: File Changed The File has been changed on the file system. Do you want to load the changes? I saw yes, then these error come out: !ENTRY org.eclipse.core.filebuffers 4 0 Feb 17, 2004 23:40:36.778 !MESSAGE Exception when synchronizing !STACK 0 java.lang.NullPointerE... | verified fixed | b28a95a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T16:23:54Z | 2004-02-17T15:00:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitEditor.java | /*******************************************************************************
* Copyright (c) 2000, 2003 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... |
50,971 | Bug 50971 Extract temp: index out of bounds error [refactoring] | I20040129 Trying to extract a local from entries[i].getPluginId() caused an exception. private MultiStatus createMultiStatus() { MultiStatus status= new MultiStatus( JavaPlugin.getPluginId(), IStatus.ERROR, RefactoringMessages.getString ("UndoManagerAction.validation_failed"), //$NON-NLS-1$ null); RefactoringStatusEntr... | resolved fixed | 30a745b | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T19:46:38Z | 2004-01-30T16:26:40Z | org.eclipse.jdt.ui.tests.refactoring/resources/ExtractTemp/canExtract/A_test78_in.java | |
50,971 | Bug 50971 Extract temp: index out of bounds error [refactoring] | I20040129 Trying to extract a local from entries[i].getPluginId() caused an exception. private MultiStatus createMultiStatus() { MultiStatus status= new MultiStatus( JavaPlugin.getPluginId(), IStatus.ERROR, RefactoringMessages.getString ("UndoManagerAction.validation_failed"), //$NON-NLS-1$ null); RefactoringStatusEntr... | resolved fixed | 30a745b | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T19:46:38Z | 2004-01-30T16:26:40Z | org.eclipse.jdt.ui.tests.refactoring/resources/ExtractTemp/canExtract/A_test78_out.java | |
50,971 | Bug 50971 Extract temp: index out of bounds error [refactoring] | I20040129 Trying to extract a local from entries[i].getPluginId() caused an exception. private MultiStatus createMultiStatus() { MultiStatus status= new MultiStatus( JavaPlugin.getPluginId(), IStatus.ERROR, RefactoringMessages.getString ("UndoManagerAction.validation_failed"), //$NON-NLS-1$ null); RefactoringStatusEntr... | resolved fixed | 30a745b | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T19:46:38Z | 2004-01-30T16:26:40Z | org.eclipse.jdt.ui.tests.refactoring/test | |
50,971 | Bug 50971 Extract temp: index out of bounds error [refactoring] | I20040129 Trying to extract a local from entries[i].getPluginId() caused an exception. private MultiStatus createMultiStatus() { MultiStatus status= new MultiStatus( JavaPlugin.getPluginId(), IStatus.ERROR, RefactoringMessages.getString ("UndoManagerAction.validation_failed"), //$NON-NLS-1$ null); RefactoringStatusEntr... | resolved fixed | 30a745b | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2004-02-23T19:46:38Z | 2004-01-30T16:26:40Z | cases/org/eclipse/jdt/ui/tests/refactoring/ExtractTempTests.java |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.