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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/ExtractMethodTestSetup.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/ExtractMethodTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/ExtractTempTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/InlineTempTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/MoveMembersTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/PullUpTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/RefactoringScannerTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/RefactoringTest.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/RenameJavaProjectTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/RenamePackageTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/RenameSourceFolderChangeTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/RenameTempTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/RenameTypeTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/ReorgTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/SefTestSetup.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/SefTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/SurroundWithTests.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui/core | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/sef/AccessAnalyzer.java | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | org.eclipse.jdt.ui/core | |
20,017 | Bug 20017 Self Encapsulate does not work correctly when "this.field = value" is used before refactoring [refactoring] | As an example I start with this class: public class Test { private Object obj; public Test (Object obj) { this.obj = obj; } } Then apply the "Self Encapsulate" refactoring on the obj field, which results: public class Test { private Object obj; public Test (Object obj) { this.getObj() = obj; } private void setObj(Objec... | resolved fixed | 698c0fe | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T13:51:56Z | 2002-06-12T13:53:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/sef/EncapsulateWriteAccess.java | |
20,677 | Bug 20677 close/open project: incorrect compile order | eclipse-SDK-20020612 ibm jdk1.3.1 I closed 20 projects in the java perspective, choosing the projects from the package view. The 20 projects I closed were org.eclipse.swt.* and org.eclipse.jdt.* I closed all 20 projects simultaneously using the project>close menu. I then re-openned all 20 projects simultaneously using ... | resolved fixed | d22851a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T14:36:36Z | 2002-06-19T18:06:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/WorkbenchRunnableAdapter.java | package org.eclipse.jdt.internal.ui.actions;
import java.lang.reflect.InvocationTargetException;
import org.eclipse.core.resources.IWorkspaceRunnable;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.core.runtime.OperationCanceledException;
import or... |
20,677 | Bug 20677 close/open project: incorrect compile order | eclipse-SDK-20020612 ibm jdk1.3.1 I closed 20 projects in the java perspective, choosing the projects from the package view. The 20 projects I closed were org.eclipse.swt.* and org.eclipse.jdt.* I closed all 20 projects simultaneously using the project>close menu. I then re-openned all 20 projects simultaneously using ... | resolved fixed | d22851a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T14:36:36Z | 2002-06-19T18:06:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenProjectAction.java | /*******************************************************************************
* Copyright (c) 2002 International Business Machines Corp. and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v0.5
* which accompanies this... |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/A.java | public class A{
public A(int i) {
}
public void foo() {
A a= new A(10);
}
}
|
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/expression_in/A_test621.java | |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/expression_in/A_test622.java | |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/expression_out/A_test621.java | |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/ExtractMethodWorkSpace/ExtractMethodTests/expression_out/A_test622.java | |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/ExtractMethodTests.java | |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | org.eclipse.jdt.ui/core | |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodAnalyzer.java | |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | org.eclipse.jdt.ui/core | |
3,582 | Bug 3582 extract method: constructor //reminder (1GEYNSB) | AK (6/7/01 7:21:46 PM) just a reminder: DB knows well about it class A{ A(){ this(8 + 9); } A(int i){} } if you want to extract anything from the super or this call in the constructor you have to make the new method static. it's a special case. NOTES: EG (6/7/2001 11:14:08 AM) defer DB (09.08.2001 11:34:32) Currently y... | resolved fixed | ce575ee | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-13T16:03:18Z | 2001-10-11T03:13:20Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodRefactoring.java | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | org.eclipse.jdt.ui/core | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/base/Context.java | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | org.eclipse.jdt.ui/core | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/base/FileContext.java | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | org.eclipse.jdt.ui/core | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/base/JavaSourceContext.java | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | org.eclipse.jdt.ui/ui | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | refactoring/org/eclipse/jdt/internal/ui/refactoring/ErrorWizardPage.java | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | org.eclipse.jdt.ui/ui | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | refactoring/org/eclipse/jdt/internal/ui/refactoring/IErrorContextViewer.java | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | org.eclipse.jdt.ui/ui | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | refactoring/org/eclipse/jdt/internal/ui/refactoring/PreviewWizardPage.java | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | org.eclipse.jdt.ui/ui | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | refactoring/org/eclipse/jdt/internal/ui/refactoring/SourceContextViewer.java | |
9,448 | Bug 9448 Improve layout and appearanceof the refactoring error page [refactoring] | - the top viewer should have a pane and may be step buttons - the lower viewer should have a pane with a title. | resolved fixed | b7a1462 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-14T15:55:46Z | 2002-02-12T13:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/util/ViewerPane.java | |
18,467 | Bug 18467 Radio bullet on Packages view's Filters... item [filters] | Build 20020530 The Filters... item on the view menu has a radio bullet, even though there are no other items in this group to choose from. | resolved fixed | 1609d1a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-15T10:18:00Z | 2002-05-31T15:46:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/CustomFiltersActionGroup.java | |
22,467 | Bug 22467 TextEdits: replace != delete + insert | see TextBufferTest.testReplaceAndInsert1 | resolved fixed | 29f00f2 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-15T12:57:11Z | 2002-08-15T14:00:00Z | org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/core/TextBufferTest.java | /*
* Copyright (c) 2002 IBM Corp. All rights reserved.
* This file is made available under the terms of the Common Public License v1.0
* which accompanies this distribution, and is available at
* http://www.eclipse.org/legal/cpl-v10.html
*/
package org.eclipse.jdt.ui.tests.core;
import junit.framework.Test;
imp... |
18,409 | Bug 18409 EmptyInnerPackageFilter needs to be revisited [filters] | The Empty inner package filter also filter import declarations. This should be changed or made configurable. After 2.0 | resolved fixed | b01531e | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-19T09:36:08Z | 2002-05-31T07:26:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/filters/EmptyInnerPackageFilter.java | |
18,409 | Bug 18409 EmptyInnerPackageFilter needs to be revisited [filters] | The Empty inner package filter also filter import declarations. This should be changed or made configurable. After 2.0 | resolved fixed | b01531e | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-19T09:36:08Z | 2002-05-31T07:26:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/filters/PackageDeclarationFilter.java | |
19,278 | Bug 19278 jar source attachment: jar icon not refreshed [package explorer] [browsing] | F2 .a jar with no source attached .attach source the icon is still suggesting that no source is attached | resolved fixed | 5b0b955 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-19T10:29:15Z | 2002-06-05T09:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/browsing/JavaBrowsingContentProvider.java | /*
* (c) Copyright IBM Corp. 2000, 2001.
* All Rights Reserved.
*/
package org.eclipse.jdt.internal.ui.browsing;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.Collection;
import java.util.Iterator;
import java.util.List;
import org.eclipse.core.resources.IResource;
import org.eclipse.swt.w... |
19,278 | Bug 19278 jar source attachment: jar icon not refreshed [package explorer] [browsing] | F2 .a jar with no source attached .attach source the icon is still suggesting that no source is attached | resolved fixed | 5b0b955 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-19T10:29:15Z | 2002-06-05T09:40:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/packageview/PackageExplorerContentProvider.java | /*
* (c) Copyright IBM Corp. 2000, 2001.
* All Rights Reserved.
*/
package org.eclipse.jdt.internal.ui.packageview;
import org.eclipse.core.resources.IResource;
import org.eclipse.core.resources.IResourceDelta;
import org.eclipse.swt.widgets.Control;
import org.eclipse.jface.viewers.IBasicPropertyConstants;
impor... |
14,299 | Bug 14299 Package filter [browsing] | Hello, I would suggest the following useful feature ; could it be possible to add a filter in the package view of the java browsing perspective, and elsewhere in order to aneble the user to filter the "package", "protected", "private", "public" classes of a package or a group of packages. Actually we often need to have... | resolved fixed | 543fd80 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-19T12:16:10Z | 2002-04-22T07:20:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/filters/NonPublicTypeFilter.java | |
20,970 | Bug 20970 class/interface filters in type browsing view [filters] [browsing] | Build 20020625 (GM2) A post 2.0 feature request... I think it would be useful to have "filter classes" and "filter interfaces" in the type browsing view. One use scenario for this: when the type hierarchy view is open on a package, it can't show interfaces. To get around this I generally stack the type browsing view wi... | resolved fixed | 43aa9ad | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-19T15:16:41Z | 2002-06-25T18:33:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/filters/ClassFilter.java | |
20,970 | Bug 20970 class/interface filters in type browsing view [filters] [browsing] | Build 20020625 (GM2) A post 2.0 feature request... I think it would be useful to have "filter classes" and "filter interfaces" in the type browsing view. One use scenario for this: when the type hierarchy view is open on a package, it can't show interfaces. To get around this I generally stack the type browsing view wi... | resolved fixed | 43aa9ad | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-19T15:16:41Z | 2002-06-25T18:33:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/filters/InterfaceFilter.java | |
22,380 | Bug 22380 "No Source" class file editor does not fetch keyboard focus | Build N20020813 Test Case: 1. From the package explorer open a class from a JAR without attached source 2. Activate the editor 3. Select something in another view (note: selection is blue) 4. Activate the class file editor by clicking on the tab ==> selection in other view remains blue but should be gray. Suggest to se... | resolved fixed | c6c96b9 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-20T12:52:48Z | 2002-08-13T12:00:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ClassFileEditor.java | package org.eclipse.jdt.internal.ui.javaeditor;
/*
* (c) Copyright IBM Corp. 2000, 2001.
* All Rights Reserved.
*/
import java.util.ArrayList;
import java.util.Iterator;
import java.util.List;
import org.eclipse.swt.SWT;
import org.eclipse.swt.custom.ScrolledComposite;
import org.eclipse.swt.custom.StackLayout;
i... |
20,622 | Bug 20622 resize bug in "Override Method" [code manipulation] | When there's lot of methods potentially overrideable and I enlarge the override method view, the inner subfields do not enlarge accordingly. I enclose a screenshot that will make clear what I mean. | resolved fixed | c9ca516 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-20T14:24:19Z | 2002-06-19T07:00:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/CheckedTreeSelectionDialog.java | /*
* (c) Copyright IBM Corp. 2000, 2001.
* All Rights Reserved.
*/
package org.eclipse.jdt.internal.ui.actions;
import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;
import org.eclipse.core.runtime.IStatus;
import org.eclipse.core.runtime.Status;
import org.eclipse.swt.SWT;
import org.eclips... |
20,622 | Bug 20622 resize bug in "Override Method" [code manipulation] | When there's lot of methods potentially overrideable and I enlarge the override method view, the inner subfields do not enlarge accordingly. I enclose a screenshot that will make clear what I mean. | resolved fixed | c9ca516 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-20T14:24:19Z | 2002-06-19T07:00:00Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/OverrideMethodQuery.java | package org.eclipse.jdt.internal.ui.actions;
import java.util.ArrayList;
import java.util.HashSet;
import org.eclipse.core.runtime.IStatus;
import org.eclipse.swt.SWT;
import org.eclipse.swt.events.SelectionEvent;
import org.eclipse.swt.events.SelectionListener;
import org.eclipse.swt.layout.GridData;
import org.ecl... |
22,054 | Bug 22054 Can't extract local variable from super send [refactoring] | - Import the following Java class into Eclipse: public class Foo { public String toString() { return super.toString() + new Integer(1).toString(); } } - Select 'super.toString()' and choose 'Extract local variable' - An error message appears saying: 'Cannot extract this kind of expression into a local variable'. | verified fixed | b9edfac | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-20T15:34:31Z | 2002-07-30T20:13:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/ExtractTemp/canExtract/A_test48_in.java | |
22,054 | Bug 22054 Can't extract local variable from super send [refactoring] | - Import the following Java class into Eclipse: public class Foo { public String toString() { return super.toString() + new Integer(1).toString(); } } - Select 'super.toString()' and choose 'Extract local variable' - An error message appears saying: 'Cannot extract this kind of expression into a local variable'. | verified fixed | b9edfac | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-20T15:34:31Z | 2002-07-30T20:13:20Z | org.eclipse.jdt.ui.tests.refactoring/resources/ExtractTemp/canExtract/A_test48_out.java | |
22,054 | Bug 22054 Can't extract local variable from super send [refactoring] | - Import the following Java class into Eclipse: public class Foo { public String toString() { return super.toString() + new Integer(1).toString(); } } - Select 'super.toString()' and choose 'Extract local variable' - An error message appears saying: 'Cannot extract this kind of expression into a local variable'. | verified fixed | b9edfac | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-20T15:34:31Z | 2002-07-30T20:13:20Z | org.eclipse.jdt.ui.tests.refactoring/test | |
22,054 | Bug 22054 Can't extract local variable from super send [refactoring] | - Import the following Java class into Eclipse: public class Foo { public String toString() { return super.toString() + new Integer(1).toString(); } } - Select 'super.toString()' and choose 'Extract local variable' - An error message appears saying: 'Cannot extract this kind of expression into a local variable'. | verified fixed | b9edfac | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-20T15:34:31Z | 2002-07-30T20:13:20Z | cases/org/eclipse/jdt/ui/tests/refactoring/ExtractTempTests.java | |
20,832 | Bug 20832 NullPointerException in finally block hides real exception (in RenameMethodRefactoring.java) [refactoring] | I suddenly started having a problem with the rename method refactoring, getting an Internal Error with the following unhelpful root cause: ================== java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:280) [...rest of stack trace omitted] Caused by: jav... | resolved fixed | 69236e6 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T11:02:45Z | 2002-06-21T20:06:40Z | org.eclipse.jdt.ui/core | |
20,832 | Bug 20832 NullPointerException in finally block hides real exception (in RenameMethodRefactoring.java) [refactoring] | I suddenly started having a problem with the rename method refactoring, getting an Internal Error with the following unhelpful root cause: ================== java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:280) [...rest of stack trace omitted] Caused by: jav... | resolved fixed | 69236e6 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T11:02:45Z | 2002-06-21T20:06:40Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameFieldRefactoring.java | |
20,832 | Bug 20832 NullPointerException in finally block hides real exception (in RenameMethodRefactoring.java) [refactoring] | I suddenly started having a problem with the rename method refactoring, getting an Internal Error with the following unhelpful root cause: ================== java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:280) [...rest of stack trace omitted] Caused by: jav... | resolved fixed | 69236e6 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T11:02:45Z | 2002-06-21T20:06:40Z | org.eclipse.jdt.ui/core | |
20,832 | Bug 20832 NullPointerException in finally block hides real exception (in RenameMethodRefactoring.java) [refactoring] | I suddenly started having a problem with the rename method refactoring, getting an Internal Error with the following unhelpful root cause: ================== java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:280) [...rest of stack trace omitted] Caused by: jav... | resolved fixed | 69236e6 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T11:02:45Z | 2002-06-21T20:06:40Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/rename/RenameMethodRefactoring.java | |
19,067 | Bug 19067 Useless error message | F2 - create project Test with source folder src - create folder data - create Test.java in data - paste content class Test { public Object field; } class B extends Test { public Object field2; } - select field2 - select Refactor->Pullup... You get an error message saying: Pull up is not allowed on elements declared in ... | resolved fixed | 18b4ef5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T12:50:47Z | 2002-06-04T14:13:20Z | org.eclipse.jdt.ui/ui | |
19,067 | Bug 19067 Useless error message | F2 - create project Test with source folder src - create folder data - create Test.java in data - paste content class Test { public Object field; } class B extends Test { public Object field2; } - select field2 - select Refactor->Pullup... You get an error message saying: Pull up is not allowed on elements declared in ... | resolved fixed | 18b4ef5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T12:50:47Z | 2002-06-04T14:13:20Z | refactoring/org/eclipse/jdt/internal/ui/refactoring/actions/MoveMembersAction.java | |
19,067 | Bug 19067 Useless error message | F2 - create project Test with source folder src - create folder data - create Test.java in data - paste content class Test { public Object field; } class B extends Test { public Object field2; } - select field2 - select Refactor->Pullup... You get an error message saying: Pull up is not allowed on elements declared in ... | resolved fixed | 18b4ef5 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T12:50:47Z | 2002-06-04T14:13:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/PullUpAction.java | package org.eclipse.jdt.ui.actions;
import java.util.Arrays;
import java.util.HashSet;
import java.util.Iterator;
import java.util.Set;
import org.eclipse.jface.dialogs.MessageDialog;
import org.eclipse.jface.text.ITextSelection;
import org.eclipse.jface.viewers.IStructuredSelection;
import org.eclipse.jface.viewers.... |
22,632 | Bug 22632 inline temp: should disallow iniling arrays intialized with array constants | class A{ void f(A a){ A[] arr= {a}; arr[0]= null; } } cannot inline arr | resolved fixed | fa2abaa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T14:37:12Z | 2002-08-21T14:26:40Z | org.eclipse.jdt.ui.tests.refactoring/resources/InlineTemp/cannotInline/A_testFail14.java | |
22,632 | Bug 22632 inline temp: should disallow iniling arrays intialized with array constants | class A{ void f(A a){ A[] arr= {a}; arr[0]= null; } } cannot inline arr | resolved fixed | fa2abaa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T14:37:12Z | 2002-08-21T14:26:40Z | org.eclipse.jdt.ui.tests.refactoring/test | |
22,632 | Bug 22632 inline temp: should disallow iniling arrays intialized with array constants | class A{ void f(A a){ A[] arr= {a}; arr[0]= null; } } cannot inline arr | resolved fixed | fa2abaa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T14:37:12Z | 2002-08-21T14:26:40Z | cases/org/eclipse/jdt/ui/tests/refactoring/InlineTempTests.java | |
22,632 | Bug 22632 inline temp: should disallow iniling arrays intialized with array constants | class A{ void f(A a){ A[] arr= {a}; arr[0]= null; } } cannot inline arr | resolved fixed | fa2abaa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T14:37:12Z | 2002-08-21T14:26:40Z | org.eclipse.jdt.ui/core | |
22,632 | Bug 22632 inline temp: should disallow iniling arrays intialized with array constants | class A{ void f(A a){ A[] arr= {a}; arr[0]= null; } } cannot inline arr | resolved fixed | fa2abaa | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-21T14:37:12Z | 2002-08-21T14:26:40Z | refactoring/org/eclipse/jdt/internal/corext/refactoring/code/InlineTempRefactoring.java | |
12,261 | Bug 12261 Eclipse dies after SWT error | build 20020321 Adding a method to a java file I get an SWT error and a dialog pops up asking if I want to exit Eclipse because of an Internal error. The log file is attached. I could not isolate the problem but I do have a workspace that reproduces it. If you need the workspace and the steps to reproduce, just let me k... | resolved fixed | 6189678 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-22T14:33:30Z | 2002-03-26T02:33:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/link/LinkedPositionUI.java | /*
* (c) Copyright IBM Corp. 2000, 2001.
* All Rights Reserved.
*/
package org.eclipse.jdt.internal.ui.text.link;
import java.lang.reflect.InvocationTargetException;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.swt.SWT;
import org.eclipse.swt.custom.StyledText;
import org.eclipse.swt.custom.V... |
22,329 | Bug 22329 Incorrect icon shown for jar entries [package explorer] [browsing] | The icon displayed for jar file entries is not always correct. I am supplying the following to demonstrate the problem: 1. test.plugin.zip - This is a plugin that defines several default text editors with unique icons for particular file names. Extract it into the eclipse/plugins directory. 2. IconJarTest.zip - This is... | resolved fixed | 52e543c | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-23T15:11:05Z | 2002-08-09T21:53:20Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/StorageLabelProvider.java | /*
* (c) Copyright IBM Corp. 2000, 2001.
* All Rights Reserved.
*/
package org.eclipse.jdt.internal.ui.viewsupport;
import java.util.HashMap;
import java.util.Iterator;
import java.util.Map;
import org.eclipse.core.resources.IStorage;
import org.eclipse.swt.graphics.Image;
import org.eclipse.jface.resource.Imag... |
12,802 | Bug 12802 modify parameters: should be enabled if a parameter is selected in the editor [refactoring] | currently, you have to select a method | resolved fixed | 56cdb5a | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-26T13:38:20Z | 2002-04-04T17:06:40Z | org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/ModifyParametersAction.java | /*******************************************************************************
* Copyright (c) 2002 International Business Machines Corp. and others.
* All rights reserved. This program and the accompanying materials
* are made available under the terms of the Common Public License v0.5
* which accompanies this... |
22,725 | Bug 22725 NLS Tool: Default common prefix [refactoring] | It would be nice if the "Externalize Strings" wizard filled in the "Enter common prefix for generated keys" field with the name of the name of the class by default. For example, if I'm externalizing the strings in JDIModelPresentation, the prefix would be set to "JDIModelPresentation." by default. I believe this is wha... | resolved fixed | c257cf3 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-28T14:51:05Z | 2002-08-22T15:26:40Z | org.eclipse.jdt.ui/ui | |
22,725 | Bug 22725 NLS Tool: Default common prefix [refactoring] | It would be nice if the "Externalize Strings" wizard filled in the "Enter common prefix for generated keys" field with the name of the name of the class by default. For example, if I'm externalizing the strings in JDIModelPresentation, the prefix would be set to "JDIModelPresentation." by default. I believe this is wha... | resolved fixed | c257cf3 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-28T14:51:05Z | 2002-08-22T15:26:40Z | refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/ExternalizeWizardPage.java | |
22,827 | Bug 22827 nls: incorrect error if package starts with uppercase [refactoring] | If you try to externalize strings from a class contained in a package whose name starts with a cap, you will not be able to complete the externalization because of an error on the second page. The error message says : "By convention, packages names usually start with a lowercase letter". This is inconsistent with the b... | resolved fixed | 0d45186 | JDT | https://github.com/eclipse-jdt/eclipse.jdt.ui | eclipse-jdt/eclipse.jdt.ui | java | null | null | null | 2002-08-28T16:16:19Z | 2002-08-26T08:20:00Z | org.eclipse.jdt.ui/ui |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.