id
int64 1
6.5k
| bug_id
int64 2.03k
426k
| summary
stringlengths 9
251
| description
stringlengths 1
32.8k
⌀ | report_time
stringlengths 19
19
| report_timestamp
int64 1B
1.39B
| status
stringclasses 6
values | commit
stringlengths 7
9
| commit_timestamp
int64 1B
1.39B
| files
stringlengths 25
32.8k
| project_name
stringclasses 6
values |
|---|---|---|---|---|---|---|---|---|---|---|
35
| 409,520
|
Bug 409520 [1.8][quick fix] "Add unimplemented methods" should not create stubs for default methods
|
BETA_JAVA8 and master The "Add unimplemented methods" quick fix should not create stubs for default methods. public class MyString implements CharSequence { } => When compiling against a 1.8 JRE, the quick fix also adds stubs for chars() and codePoints(), which are new default methods in CharSequence. "Source > Override/Implement Methods" already looks good (only selects abstract methods).
|
2013-05-30 12:58:01
| 1,369,930,000
|
verified fixed
|
100ddaa
| 1,374,670,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility2.java
|
JDT
|
36
| 411,794
|
Bug 411794 [JUnit] Add a monospace font option for the Junit view
| null |
2013-06-27 12:12:00
| 1,372,350,000
|
verified fixed
|
d0add17
| 1,374,660,000
|
org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/FailureTrace.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestRunnerViewPart.java
|
JDT
|
37
| 411,841
|
Bug 411841 Rerunning a test from JUnit results view is launching the test on UI thread.
|
When I rerun a test by selecting "Run" from the JUnit test results view context menu the test launch is happening on the UI thread. When build before launch is enabled the project build is invoked on UI thread on Eclipse is frozen during the test launch process. I am working on a patch to avoid it by delegating the rerun config launching to DebugUITools.launch() and will attach it to the bug soon. A sample stack trace captured during the freeze is ... java.io.UnixFileSystem.createDirectory(Native Method) java.io.File.mkdir(File.java:1239) java.io.File.mkdirs(File.java:1266) org.eclipse.core.internal.filesystem.local.LocalFile.mkdir(LocalFile.java:286) org.eclipse.core.internal.localstore.FileSystemResourceManager.write(FileSystemResourceManager.java:1132) org.eclipse.core.internal.resources.Folder.internalCreate(Folder.java:180) org.eclipse.core.internal.resources.Folder.create(Folder.java:107) org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.createFolder(AbstractImageBuilder.java:470) org.eclipse.jdt.internal.core.builder.AbstractImageBuilder$1.visit(AbstractImageBuilder.java:254) org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:85) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127) org.eclipse.core.internal.resources.Resource.accept(Resource.java:95) org.eclipse.core.internal.resources.Resource.accept(Resource.java:52) org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.addAllSourceFiles(AbstractImageBuilder.java:219) org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:51) org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254) org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:184) org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394) org.eclipse.core.internal.resources.Project$1.run(Project.java:618) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597) org.eclipse.core.internal.resources.Project.build(Project.java:114) org.eclipse.debug.core.model.LaunchConfigurationDelegate$1.run(LaunchConfigurationDelegate.java:423) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326) org.eclipse.debug.core.model.LaunchConfigurationDelegate.buildProjects(LaunchConfigurationDelegate.java:430) org.eclipse.debug.core.model.LaunchConfigurationDelegate.buildForLaunch(LaunchConfigurationDelegate.java:126) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:823) org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:704) org.eclipse.jdt.internal.junit.model.TestRunSession.rerunTest(TestRunSession.java:485) org.eclipse.jdt.internal.junit.ui.TestRunnerViewPart.rerunTest(TestRunnerViewPart.java:2062) org.eclipse.jdt.internal.junit.ui.RerunAction.run(RerunAction.java:52) org.eclipse.jface.action.Action.runWithEvent(Action.java:498) org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1276) org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3554) org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3179)
|
2013-06-27 19:03:40
| 1,372,370,000
|
resolved fixed
|
a81ceba
| 1,372,770,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/model/TestRunSession.java org.eclipse.jdt.junit/src/org/eclipse/jdt/internal/junit/ui/TestRunnerViewPart.java
|
JDT
|
38
| 411,588
|
Bug 411588 "Convert for loops to enhanced" may mess up program logic when dealing with Iterable
|
With the save action "Convert 'for' loops to enhanced 'for' loops" enabled, the conversion to enhanced loop might introduce a logical error. Lets suppose you have an object "s" with a class implementing java.lang.Iterable and this class has also another method named "iterator", also with an "Iterator" return type, BUT with a __non empty signature__. for (Iterator<Object> it = s.iterator(42) ; it.hasNext(); ) { Object obj = it.next(); // ... } The save action will convert it to an enhanced loop assuming the use of "s.iterator()" instead of "s.iterator(42)" ! for (Object obj : s) { // ... } (The bug exists also in 3.7.2 and probably in all releases until Kepler)
|
2013-06-25 07:28:22
| 1,372,160,000
|
verified fixed
|
a8d9f12
| 1,372,770,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/ConvertIterableLoopQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/ConvertIterableLoopOperation.java
|
JDT
|
39
| 411,641
|
Bug 411641 [content assist] Unnecessary content assist popup after decimal
|
If you are typing a floating point number say 3.14 then content assist window pops up after typing '.', e.g. in this situation below void bar() { System.out.println(3.); } Tried this with 4.3 RC4. (Likely a consequence of changes for showing Template and keyword proposals without prefix)
|
2013-06-25 17:19:28
| 1,372,200,000
|
verified fixed
|
25f6fa1
| 1,372,240,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/JavaContext.java
|
JDT
|
40
| 411,585
|
Bug 411585 [mark occurrence][search] Mark occurrences reports 0 based line numbers but the actual line numbers in the line number rulers starts with 1
|
If i do ctrl-shift-u on a identifier i get a list of lines in the search view where those are found. But the line numbers that are reported are 1 off. It does jump to the right line but it is funny to see that the search view reports "203:" and the actual code is according to the line of the ruler is on 204 It seems that the search view reports 0 based but the line number ruler starts with 1 Eclipse SDK Version: 4.3.0 Build id: I20130605-2000
|
2013-06-25 07:02:59
| 1,372,160,000
|
resolved fixed
|
b5d624f
| 1,372,160,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/JavaElementLine.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/OccurrencesSearchLabelProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/OccurrencesSearchResultPage.java
|
JDT
|
41
| 408,072
|
Bug 408072 [nls tooling] Interface is flagged as missing NLS key
|
Version: 4.3.0 Build id: I20130513-2000 While scanning org.eclipse.jface I got the following during the search: Undefined keys in: MenuManager.java - org.eclipse.jface.action (2 matches) One of the matches is: ExternalActionManager.ICallback callback = ExternalActionManager.getInstance().getCallback(); with ExternalActionManager.ICallback highlighted. There are 17 of these flagged for all of jface.
|
2013-05-14 21:31:21
| 1,368,580,000
|
resolved fixed
|
9a7c42a
| 1,371,730,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/search/NLSSearchResultRequestor.java
|
JDT
|
42
| 410,830
|
Bug 410830 [syntax highlighting] Argument of {@code *}/{@literal *} in Javadoc should not use HTML markup coloring
|
In Java source editors, the argument of an {@code *} or {@literal *} tag in Javadoc should not use "HTML markup" coloring. E.g. "<String>" is not an HTML tag and should be rendered the same as "Set" here: * {@code Set<String>}
|
2013-06-14 11:30:38
| 1,371,220,000
|
resolved fixed
|
48580ac
| 1,371,730,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavaDocScanner.java
|
JDT
|
43
| 104,379
|
Bug 104379 [syntax highlighting] {@link} tag syntax coloring does not work when on two lines
|
Set a color for {@link} tags from the preferences page. When you have a link tag that is on two lines, the part of it that is on the second line is not colored properly.
|
2005-07-19 13:57:02
| 1,121,800,000
|
resolved fixed
|
2d19131
| 1,371,730,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavaDocScanner.java
|
JDT
|
44
| 408,060
|
Bug 408060 Bug in NLSSearchQuery
| null |
2013-05-14 15:55:49
| 1,368,560,000
|
resolved fixed
|
3969b41
| 1,371,730,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/search/NLSSearchQuery.java
|
JDT
|
45
| 410,569
|
Bug 410569 Remove 'org.eclipse.releng.tools' from the list of not loaded plug-ins
|
4.3 RC4.
|
2013-06-12 05:10:55
| 1,371,030,000
|
verified fixed
|
16ee663
| 1,371,710,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/PluginsNotLoadedTest.java
|
JDT
|
46
| 409,705
|
Bug 409705 IntroduceIndirectionTests.test31 fails with an error while deleting resources
| null |
2013-06-03 05:23:16
| 1,370,250,000
|
verified fixed
|
0ac85d5
| 1,370,270,000
|
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/IntroduceIndirectionTests.java
|
JDT
|
47
| 409,704
|
Bug 409704 MoveInnerToTopLevelTests.test25 throws error during tearDown
| null |
2013-06-03 05:21:39
| 1,370,250,000
|
verified fixed
|
8029c94
| 1,370,270,000
|
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/RefactoringTest.java org.eclipse.jdt.ui.tests/test plugin/org/eclipse/jdt/testplugin/JavaProjectHelper.java
|
JDT
|
48
| 408,555
|
Bug 408555 DeleteTest.testDeleteInternalJAR fails sporadically
|
http://download.eclipse.org/eclipse/downloads/drops4/I20130518-1500/testresults/html/org.eclipse.jdt.ui.tests.refactoring_win32.win32.x86_7.0.html
|
2013-05-21 06:13:40
| 1,369,130,000
|
verified fixed
|
4fc272a
| 1,369,840,000
|
org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/RefactoringTest.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ccp/DeleteTest.java org.eclipse.jdt.ui.tests/test plugin/org/eclipse/jdt/testplugin/JavaProjectHelper.java
|
JDT
|
49
| 408,124
|
Bug 408124 [refactoring] CCE with Extract Class refactoring on a class with comment
|
Perform Refactor > Extract Class... on the following example: // comment public class Test { int i; } We get this exception: java.lang.reflect.InvocationTargetException at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421) at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:331) ... Caused by: java.lang.ClassCastException: org.eclipse.jdt.core.dom.CompilationUnit cannot be cast to org.eclipse.jdt.core.dom.TypeDeclaration at org.eclipse.jdt.internal.corext.refactoring.structure.ExtractClassRefactoring.createParameterObject(ExtractClassRefactoring.java:479)
|
2013-05-15 09:01:01
| 1,368,620,000
|
verified fixed
|
c880487
| 1,369,150,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ExtractClass/testComment/in/Comment.java org.eclipse.jdt.ui.tests.refactoring/resources/ExtractClass/testComment/out/Comment.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ExtractClassTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/ExtractClassRefactoring.java
|
JDT
|
50
| 408,330
|
Bug 408330 Java Model Exception from Javadoc view if element is deleted
|
Select foo() in the following example and open the Javadoc view: public class Test { private void foo() {} } Now, delete the method: private void foo() {} An error is logged in the Error Log view on deletion: Java Model Exception: Java Model Status [foo() [in Test [in [Working copy] Test.java [in test.bugs.var [in src [in com.bugs.test]]]]] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:498) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:532) ... at org.eclipse.jdt.internal.ui.text.javadoc.JavadocContentAccess2.getHTMLContentFromSource(JavadocContentAccess2.java:600) at org.eclipse.jdt.internal.ui.text.javadoc.JavadocContentAccess2.getHTMLContent(JavadocContentAccess2.java:495) at org.eclipse.jdt.internal.ui.infoviews.JavadocView.getJavadocHtml(JavadocView.java:1097) at org.eclipse.jdt.internal.ui.infoviews.JavadocView.computeInput(JavadocView.java:908)
|
2013-05-17 07:22:46
| 1,368,790,000
|
verified fixed
|
a0f013e
| 1,369,150,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/AbstractInfoView.java
|
JDT
|
51
| 407,434
|
Bug 407434 [BiDi][templates] Wrong BTD in templates [BiDi 2013]
| null |
2013-05-07 11:47:10
| 1,367,940,000
|
verified fixed
|
6836a99
| 1,368,550,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/EditTemplateDialog.java
|
JDT
|
52
| 401,844
|
Bug 401844 [JUnit] Unable to locate proper Javadoc for JUnit 4
| null |
2013-02-26 17:41:20
| 1,361,920,000
|
verified fixed
|
92914ba
| 1,368,530,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/JunitPreferenceInitializer.java org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/BuildPathSupport.java
|
JDT
|
53
| 407,382
|
Bug 407382 [type wizards] NPE on content assist for a new workspace
|
1. Open a new workspace. 2. Go to File -> New -> Class. (Open any New type wizard). 3. Check "Enclosing type". 4. Press Ctrl+Space in the text field of Enclosing type. We get an exception in Error Log view. org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) .... Caused by: java.lang.NullPointerException at org.eclipse.jdt.internal.ui.refactoring.contentassist.CUPositionCompletionProcessor.computeCompletionProposals(CUPositionCompletionProcessor.java:159)
|
2013-05-07 06:15:43
| 1,367,920,000
|
verified fixed
|
eaba698
| 1,368,020,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/contentassist/CUPositionCompletionProcessor.java
|
JDT
|
54
| 273,728
|
Bug 273728 [BiDi][type wizards] Incorrect representation of complex expressions (like filepath) containing Bidi characters in "Create New ..." wizards.
|
Build ID: I20090313-0100 Steps To Reproduce: Use the Bidi (Arabic/Hebrew) enabled version of Windows. 1. Start eclipse with following arguments: "-nl en -dir rtl" in workspace "C:\workspace". 2. Select "New->Project", then choose any any project except "General". 3. In "New ....Project" wizard type "ABC" (capital letters stands for Bidi characters) into 'Project name' field. This field now contains: "CBA". Result: The "Directory field contains "CBA\C:\workspace". The correct display should be of course: "c:\workspace\CBA". Remark. This problem has been resolved, for instance, for "General" project ('New Project' page of create project wizard 'New->Project->General->Project'). The built in mechanism for correct processing of complex expressions (like filepath) containing Bidi characters exists in Text processor. More information:
|
2009-04-26 13:27:10
| 1,240,770,000
|
verified fixed
|
7ea3eb6
| 1,367,430,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/CodeAssistFavoritesConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ImportOrganizeInputDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavadocConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/TypeFilterInputDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/UserLibraryPreferencePage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/NewSourceFolderWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/AddSourceFolderWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/SourceContainerWorkbookPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/VariableCreationDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewContainerWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPageOne.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewPackageWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.java
|
JDT
|
55
| 406,992
|
Bug 406992 [content assist] Template proposal should not be more relevant than constructor proposal
|
package xy; public class CompletionTest { { new File() } } - put caret between () - press Ctrl+Space => 4.3 M5a allowed me to choose a constructor proposal, press Enter, and then see context information. But now, I get a bunch of less interesting template proposals in front.
|
2013-05-01 10:58:33
| 1,367,420,000
|
verified fixed
|
d74093a
| 1,367,430,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/template/contentassist/TemplateProposal.java
|
JDT
|
56
| 406,171
|
Bug 406171 [navigation] "Next Word" did not complete normally
|
While navigating some code in the Scala IDE v3.0.0 for Eclipse 3.7, the following exception was reported by the Eclipse platform: "Next Word" did not complete normally. I believe this happened while pressing "CMD + Right arrow" on a dirty (i.e., not yet saved) editor. Unfortunately, I can't reproduce it. I'm filing a ticket here and not the Scala IDE issue tracker because in the stacktrace (see below) there isn't any call that involves the Scala IDE codebase. That being said, the Scala IDE could still be in fault, because the Scala Editor is built on top of the Java Editor. Below follows the full stacktrace org.eclipse.core.runtime.AssertionFailedException: assertion failed: at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96) at org.eclipse.jface.text.Position.<init>(Position.java:62) at org.eclipse.jface.text.link.LinkedPosition.<init>(LinkedPosition.java:43) at org.eclipse.jface.text.link.LinkedPosition.<init>(LinkedPosition.java:58) at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor$NextSubWordAction.findNextPosition(JavaEditor.java:806) at org.eclipse.jdt.internal.ui.javaeditor.JavaEditor$NextSubWordAction.run(JavaEditor.java:768) at org.eclipse.ui.texteditor.TextNavigationAction.runWithEvent(TextNavigationAction.java:99) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1069) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4127) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Control.traverse(Control.java:4768) at org.eclipse.swt.widgets.Control.translateTraversal(Control.java:4552) at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1058) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5563) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68) at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:587) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5473) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3610) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
|
2013-04-21 11:33:40
| 1,366,560,000
|
verified fixed
|
eb70b90
| 1,367,420,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditor.java
|
JDT
|
57
| 406,995
|
Bug 406995 [content assist] Context Information is not shown after completion of void method
|
With the automatic addition of ';' to void-returning method completion proposals, we don't show Context Information any more for such completions. Example: Complete after "wait" here and choose a method with parameters: package xy; public class CompletionTest { { wait } } The problem in this case is that JavaMethodCompletionProposal#computeContextInformation() needs another condition "|| getReplacementString().endsWith(SEMICOLON)". Need to check other proposals as well.
|
2013-05-01 11:16:33
| 1,367,420,000
|
verified fixed
|
04f7136
| 1,367,420,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaMethodCompletionProposal.java
|
JDT
|
58
| 167,472
|
Bug 167472 [quick fix] Suggest to add missing type for for-each variable
|
Given the code: ArrayList<T> list = new ArrayList<T>(); for (item : list) { // error } There is an error on "item", as it is undeclared. Quickfix asks if you want to create a class, interface or enum for "item", or add a type parameter "item" to the class. I would expect a suggestion of declaring an iterator variable "T item". (Also the compiler is confused because it says on "list" that "Cannot convert element type T to item", so it thinks item is a type.) This looks like a trivial content-assist but saves a lot of typing when iterating through complex generic containers-inside-containers.
|
2006-12-11 14:29:43
| 1,165,870,000
|
verified fixed
|
9f57afc
| 1,367,190,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/TypeMismatchQuickFixTests.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedTypesQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/ASTResolving.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/TypeMismatchSubProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/UnresolvedElementsSubProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/NewVariableCorrectionProposal.java
|
JDT
|
59
| 406,463
|
Bug 406463 [templates][content assist] Ctrl+Space without any starting letter shows to no templates
|
I finally realized that the "empty" CTRL+Space does not show any templates. I think it would be much more helpful if the empty statement show all templates. Example: No line in the editor-> CTRL+Space should display all templates. B-> CTRL+Space shows Browser and Button template. I would assume that this change would be relatively easily, please feel free to guide me to the right class so that I can try to fix that.
|
2013-04-24 12:34:41
| 1,366,820,000
|
resolved fixed
|
8784c4c
| 1,366,890,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/template/java/JavaContext.java
|
JDT
|
60
| 406,478
|
Bug 406478 [implementation][content assist] Use enhanced for loop for CompletionProposalCollector and CompletionProposalCategory
|
I suggest to use the foreach loop in ContentAssistProcessor. Patch to follow soon.
|
2013-04-24 14:14:51
| 1,366,830,000
|
resolved fixed
|
2d5bd89
| 1,366,880,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/CompletionProposalCategory.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ContentAssistProcessor.java
|
JDT
|
61
| 337,680
|
Bug 337680 [inline][getter setter] Fix creation of unnecessary/missing parentheses
| null |
2011-02-20 23:18:29
| 1,298,260,000
|
resolved fixed
|
82e7a99
| 1,366,870,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/SefWorkSpace/SefTests/object_out/TestCompoundWrite2.java org.eclipse.jdt.ui.tests.refactoring/resources/SefWorkSpace/SefTests/object_out/TestCompoundWrite4.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/GetterSetterQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/GetterSetterUtil.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/dom/NecessaryParenthesesChecker.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/sef/AccessAnalyzer.java
|
JDT
|
62
| 400,668
|
Bug 400668 [quick fix] The fix change parameter type to @Nonnull generated a null change
|
In a project with nullity annotations present I have a lot of warnings like: Null type safety: the expression of type AppSession needs unchecked conversion to conform to '@Nonnull AppSession'. On the warning message, click "quick fix" and select "Change parameter type to @Nonnull", select a single file, then press finish. Eclipse comes with a popup stating "an exception occured while applying the quick fix", and the message in the title of this bug report. Selecting multiple files to fix dies without any kind of message, and no files are changed. The log shows (dont't be scared, huge stack trace): !ENTRY org.eclipse.jdt.ui 4 10001 2013-02-13 11:41:55.559 !MESSAGE Internal Error !STACK 1 Java Model Exception: Core Exception [code 0] The fix 'Add Annotations' generated a null change. at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:50) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5332) at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106) at org.eclipse.jdt.internal.ui.text.correction.proposals.FixCorrectionProposal$1.run(FixCorrectionProposal.java:218) at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper.perform(RefactoringExecutionHelper.java:191) at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper.perform(RefactoringExecutionHelper.java:151) at org.eclipse.jdt.internal.ui.text.correction.proposals.FixCorrectionProposal.resolve(FixCorrectionProposal.java:225) at org.eclipse.jdt.internal.ui.text.correction.CorrectionMarkerResolutionGenerator$CorrectionMarkerResolution.run(CorrectionMarkerResolutionGenerator.java:145) at org.eclipse.ui.internal.views.markers.QuickFixPage$11.run(QuickFixPage.java:565) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028) at org.eclipse.ui.internal.views.markers.QuickFixPage.performFinish(QuickFixPage.java:554) at org.eclipse.ui.internal.views.markers.QuickFixWizard$1.run(QuickFixWizard.java:97) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028) at org.eclipse.ui.internal.views.markers.QuickFixWizard.performFinish(QuickFixWizard.java:106) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3705) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3326) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.views.markers.QuickFixHandler.execute(QuickFixHandler.java:165) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:76) at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:277) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:496) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:547) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:368) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:314) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:83) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1552) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1391) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1401) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1428) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:829) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3180) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:758) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2092) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5334) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3566) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4532) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8549) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1241) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2281) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3324) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426) Caused by: org.eclipse.core.runtime.CoreException: The fix 'Add Annotations' generated a null change. at org.eclipse.jdt.internal.corext.fix.CompilationUnitRewriteOperationsFix.createChange(CompilationUnitRewriteOperationsFix.java:106) at org.eclipse.jdt.internal.corext.fix.CleanUpRefactoring.calculateChange(CleanUpRefactoring.java:810) at org.eclipse.jdt.internal.corext.fix.CleanUpRefactoring$CleanUpASTRequestor.calculateSolutions(CleanUpRefactoring.java:305) at org.eclipse.jdt.internal.corext.fix.CleanUpRefactoring$CleanUpASTRequestor.acceptAST(CleanUpRefactoring.java:283) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:892) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:581) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:894) at org.eclipse.jdt.internal.corext.dom.ASTBatchParser.createASTs(ASTBatchParser.java:100) at org.eclipse.jdt.internal.corext.fix.CleanUpRefactoring$CleanUpFixpointIterator.next(CleanUpRefactoring.java:406) at org.eclipse.jdt.internal.corext.fix.CleanUpRefactoring.cleanUpProject(CleanUpRefactoring.java:718) at org.eclipse.jdt.internal.corext.fix.CleanUpRefactoring.checkFinalConditions(CleanUpRefactoring.java:674) at org.eclipse.ltk.core.refactoring.Refactoring.checkAllConditions(Refactoring.java:162) at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper$Operation.run(RefactoringExecutionHelper.java:80) at org.eclipse.jdt.internal.core.BatchOperation.executeOperation(BatchOperation.java:39) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345) at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:5332) at org.eclipse.jdt.internal.ui.actions.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:106) at org.eclipse.jdt.internal.ui.text.correction.proposals.FixCorrectionProposal$1.run(FixCorrectionProposal.java:218) at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper.perform(RefactoringExecutionHelper.java:191) at org.eclipse.jdt.internal.ui.refactoring.RefactoringExecutionHelper.perform(RefactoringExecutionHelper.java:151) at org.eclipse.jdt.internal.ui.text.correction.proposals.FixCorrectionProposal.resolve(FixCorrectionProposal.java:225) at org.eclipse.jdt.internal.ui.text.correction.CorrectionMarkerResolutionGenerator$CorrectionMarkerResolution.run(CorrectionMarkerResolutionGenerator.java:145) at org.eclipse.ui.internal.views.markers.QuickFixPage$11.run(QuickFixPage.java:565) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028) at org.eclipse.ui.internal.views.markers.QuickFixPage.performFinish(QuickFixPage.java:554) at org.eclipse.ui.internal.views.markers.QuickFixWizard$1.run(QuickFixWizard.java:97) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028) at org.eclipse.ui.internal.views.markers.QuickFixWizard.performFinish(QuickFixWizard.java:106) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3705) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3326) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.views.markers.QuickFixHandler.execute(QuickFixHandler.java:165) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:76) at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:277) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:496) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:547) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:368) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:314) at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:83) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1552) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1391) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1401) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1428) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:829) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3180) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:758) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2092) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5334) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:3566) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4532) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8549) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1241) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2281) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3324) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) at org.eclipse.equinox.launcher.Main.run(Main.java:1450) at org.eclipse.equinox.launcher.Main.main(Main.java:1426) !SUBENTRY 1 org.eclipse.jdt.ui 4 0 2013-02-13 11:41:55.561 !MESSAGE The fix 'Add Annotations' generated a null change.
|
2013-02-13 05:49:34
| 1,360,750,000
|
resolved fixed
|
17c7783
| 1,366,810,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/NullAnnotationsQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/FixMessages.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/NullAnnotationsFix.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/NullAnnotationsRewriteOperations.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/NullAnnotationsCorrectionProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/QuickFixProcessor.java
|
JDT
|
63
| 405,376
|
Bug 405376 Open Input action in info views should be disabled if the input is empty/null
|
R3.8. The Open Input action in the info views should be disabled if the input is empty/null. Currently, it is not, and clicking it, gives an error dialog saying: Problem opening editor for '': 'Could not get an editor input for the given element'
|
2013-04-10 11:18:31
| 1,365,610,000
|
resolved fixed
|
b8405fa
| 1,366,290,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/AbstractInfoView.java
|
JDT
|
64
| 198,508
|
Bug 198508 [content assist] Code completion enhancement - semicolon after calls to void methods
|
Why doesn't the code editor code completion automatically put a semicolon upon inserting a call to a void method? That would really save some time, since the cursor is always placed in the parameter list (between the method call brackets), and for void methods you always have to move to the end of the line and put a semicolon. I can't off the top of my head think of a situation where you do not need to manually enter a semicolon upon a call to a void method.
|
2007-08-01 05:48:02
| 1,185,960,000
|
resolved fixed
|
9e44ebc
| 1,366,040,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/CamelCaseCompletionTest.java org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/CodeCompletionTest.java org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/MethodInsertionFormattedCompletionTest.java org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/MethodParameterGuessingCompletionTest.java org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/MethodParamsCompletionTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/FilledArgumentNamesMethodProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaMethodCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/LazyJavaCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ParameterGuessingProposal.java
|
JDT
|
65
| 198,748
|
Bug 198748 [content assist] Pressing ';' should work with all methods
| null |
2007-08-02 18:42:33
| 1,186,090,000
|
resolved fixed
|
4a05030
| 1,365,430,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/AbstractJavaCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaMethodCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ParameterGuessingProposal.java
|
JDT
|
66
| 402,393
|
Bug 402393 TagScanner and markers treat package default members as API
|
In an API type or interface, add a method or field with a package default scope. The javadoc quickfixes will allow you to add a @noreference restriction. The TagScanner will inspect the tags and they will be added to the .api_description file. This isn't correct as a package default level API could only be accessed by another API class in the same package. Since the restrictions are intended for clients, not for the bundle's internal use, there is not value in allowing the restrictions.
|
2013-03-04 17:41:38
| 1,362,440,000
|
resolved fixed
|
0612060
| 1,365,180,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/IJavaColorConstants.java
|
JDT
|
67
| 335,657
|
Bug 335657 [call hierarchy] Refresh does not bring back removed roots
|
I20110127-2034. 1. open CH on foo 2. add bar via DnD 3. delete foo 4. refresh ==> foo is not coming back. However, deleting the last node (so that view is empty) and then refresh, brings back that node. ==> either never bring back a root or always bring them back.
|
2011-01-28 02:57:17
| 1,296,200,000
|
verified fixed
|
8715274
| 1,365,160,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/callhierarchy/RemoveFromViewAction.java
|
JDT
|
68
| 404,879
|
Bug 404879 [typing] Regression on auto-insert of {}
|
Up until M6 given source text such as (@ is the cursor position) @xxxx it was possible to insert type if (yyyy != null) {@xxxx then new line to get if (yyyy != null) { xxxx } Now (in M6) and in eclipse-SDK-I20130402-0800-win32.zip we get if (yyyy != null) { }xxxx Super-irritating.
|
2013-04-04 05:24:42
| 1,365,070,000
|
resolved fixed
|
98de7b5
| 1,365,160,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JavaAutoIndentStrategyTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaAutoIndentStrategy.java
|
JDT
|
69
| 382,703
|
Bug 382703 [search] Exceptions when Search history contains constructor from closed project
|
3.7.1 (worked in 3.7). Looks like a bug in JavaElementLabelComposer or JDT Core. 1. search for references to a constructor which is in source 2. close the project 3. open the Search history ==> Java Model Exception: Java Model Status [_pasted_code_ does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:505) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240) at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504) at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1170) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240) at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:518) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:255) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:241) at org.eclipse.jdt.internal.core.SourceMethod.isConstructor(SourceMethod.java:216) at org.eclipse.jdt.internal.ui.viewsupport.JavaElementLabelComposer.appendMethodLabel(JavaElementLabelComposer.java:375) at org.eclipse.jdt.internal.ui.viewsupport.JavaElementLabelComposer.appendElementLabel(JavaElementLabelComposer.java:267) at org.eclipse.jdt.ui.JavaElementLabels.getElementLabel(JavaElementLabels.java:510) at org.eclipse.jdt.ui.JavaElementLabels.getElementLabel(JavaElementLabels.java:483) at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.getSearchPatternDescription(JavaSearchQuery.java:239) at org.eclipse.jdt.internal.ui.search.JavaSearchQuery.getResultLabel(JavaSearchQuery.java:215) at org.eclipse.jdt.internal.ui.search.JavaSearchResult.getLabel(JavaSearchResult.java:51) at org.eclipse.search2.internal.ui.SearchHistorySelectionDialog$SearchesLabelProvider.getText(SearchHistorySelectionDialog.java:199) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getText(WrappedViewerLabelProvider.java:108) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:164) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152) at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:399) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167) at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:277) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:757) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:649) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:636) at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:592) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:590) at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690) at org.eclipse.search2.internal.ui.SearchHistorySelectionDialog.createDialogArea(SearchHistorySelectionDialog.java:358) at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:760) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089) at org.eclipse.search2.internal.ui.SearchHistorySelectionDialog.create(SearchHistorySelectionDialog.java:283) at org.eclipse.jface.window.Window.open(Window.java:790) at org.eclipse.search2.internal.ui.ShowSearchHistoryDialogAction.run(ShowSearchHistoryDialogAction.java:59) at org.eclipse.search2.internal.ui.SearchHistoryDropDownAction.run(SearchHistoryDropDownAction.java:134) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) at org.eclipse.core.launcher.Main.main(Main.java:34)
|
2012-06-15 03:43:44
| 1,339,750,000
|
verified fixed
|
ac363e0
| 1,363,880,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementLabelComposer.java
|
JDT
|
70
| 403,074
|
Bug 403074 [info views] Regressions from bug 393143
| null |
2013-03-12 12:20:56
| 1,363,110,000
|
verified fixed
|
4040304
| 1,363,180,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/AbstractInfoView.java
|
JDT
|
71
| 403,036
|
Bug 403036 Wrong message is shown when there is no content for Javadoc
|
1.Create a class: public class C1 { String s; } 2. Hover on 'String' and click on the link for 'java' package. The message shown in "Note: The attached Javadoc could not be retrieved as the specified Javadoc location is either wrong or currently not accessible." The javadoc location is specified correctly and is accessible but for 'java' there is no javadoc available and hence no content can be retrieved. The message indicates a problem with the url even though it is correct. Cases for a wrong/Inaccessible url and a url where no content is available is not handled differently.
|
2013-03-12 08:05:28
| 1,363,090,000
|
verified fixed
|
744663f
| 1,363,170,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/packageHover/PackageJavadocTests.java
|
JDT
|
72
| 394,692
|
Bug 394692 [quick fix] Fix several visibility issues
|
Top-Level Bug for several quick-fix visibility bugs which can be fixed in one go.
|
2012-11-20 12:35:19
| 1,353,430,000
|
resolved fixed
|
0e8156a
| 1,363,090,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/ModifierCorrectionsQuickFixTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedMethodsQuickFixTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedTypesQuickFixTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/UnresolvedVariablesQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/dom/Bindings.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/util/JdtFlags.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/ModifierCorrectionSubProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/UnresolvedElementsSubProcessor.java
|
JDT
|
73
| 400,062
|
Bug 400062 [hovering][javadoc] Failure to access attached Javadoc should be shown to the user
| null |
2013-02-06 03:27:57
| 1,360,140,000
|
verified fixed
|
cf103b7
| 1,361,900,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/packageHover/PackageJavadocTests.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/CorextMessages.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/javadoc/JavaDocLocations.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/ProposalInfo.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavaHoverMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
74
| 401,418
|
Bug 401418 [clean up] Add test case for bug 346230
| null |
2013-02-21 07:29:49
| 1,361,450,000
|
resolved fixed
|
79eb9ff
| 1,361,550,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/CleanUpTest.java
|
JDT
|
75
| 119,181
|
Bug 119181 [quick assist] Convert to if-return
|
I have found that it is very common in poorly written code to find very long if statements that can be safely "inverted" in so that the the code is easier to understand and maintain. For example the wrong way is this: public void foo() { if (x) { ...do a bunch of stuff... return; } } When the elided part is long the if statements add considerably to the cognitive effort of holding this code in short term memory. I always refactor such code as such: public void foo() { if (!x) return; ...do a bunch of stuff... } Now you don't have to hold all of that code to be within that if statement in your head, but the code will execute identically. Please add an automated refactoring for this feature.
|
2005-12-03 20:37:18
| 1,133,660,000
|
verified fixed
|
aa32ffa
| 1,361,370,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AssistQuickFixTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/IProposalRelevance.java
|
JDT
|
76
| 395,071
|
Bug 395071 [typing] "Automatically close {Braces}" should not put the } after the rest of the line
| null |
2012-11-26 09:58:59
| 1,353,940,000
|
resolved fixed
|
cf0c4be
| 1,360,940,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/JavaAutoIndentStrategyTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/JavaAutoIndentStrategy.java
|
JDT
|
77
| 398,995
|
Bug 398995 [quick fix] Extract field access to checked local variable
| null |
2013-01-24 12:15:31
| 1,359,050,000
|
resolved fixed
|
9f5838b
| 1,360,760,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/NullAnnotationsQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/FixMessages.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/NullAnnotationsFix.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/NullAnnotationsCleanUp.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/NullAnnotationsCorrectionProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/QuickFixProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/proposals/ExtractToNullCheckedLocalProposal.java
|
JDT
|
78
| 399,997
|
Bug 399997 [hovering] Bracket hover gets messed up when code is folded
|
4.3 M5a. When code is folded then the bracket hover gets messed up. This is because the code does not use the visual/widget offsets where needed. Test Case: 1. paste the attached snippet into the 'Package Explorer' 2. fold 'foo' 3. hover over the closing brace of the class ==> hover is wrong and huge
|
2013-02-05 10:50:04
| 1,360,080,000
|
resolved fixed
|
125bb20
| 1,360,750,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavaSourceHover.java
|
JDT
|
79
| 341,604
|
Bug 341604 Add constant or helper for indenting dependent controls
|
1.0. Controls that depend on a parent control (e.g. check box) are indented. In most cases people use the commonly known value (20) and hard-code it. A few wrongly use IDialogConstants.INDENT as pixel value but that constant is defined as dialog units. For 3.8 we should define a new constant and fix the code that hard-codes 20.
|
2011-04-01 07:08:55
| 1,301,660,000
|
verified fixed
|
46efd24
| 1,360,750,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/InlineConstantWizard.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/code/InlineMethodInputPage.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameInputWizardPage.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/reorg/RenameTypeWizardSimilarElementsOptionsDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/SortMembersMessageDialog.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/fix/CleanUpSaveParticipantPreferenceConfiguration.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackager/JarManifestWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocStandardWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javadocexport/JavadocTreeWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/AbstractConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/AppearancePreferencePage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/CodeAssistConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ComplianceConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaEditorAppearanceConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaEditorColoringConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavadocConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/NameConventionConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ProblemSeveritiesConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PropertiesFileEditorPreferencePage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/formatter/BracesTabPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/buildpaths/SourceAttachmentBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/wizards/dialogfields/LayoutUtil.java
|
JDT
|
80
| 398,648
|
Bug 398648 Javadoc View inserts wrong asterisk when @see contains link with linebreak
| null |
2013-01-21 10:36:29
| 1,358,780,000
|
resolved fixed
|
2fb2b7a
| 1,360,630,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/javadoc/JavadocContentAccess2.java
|
JDT
|
81
| 395,835
|
Bug 395835 [General] Consolidate the code which finds the Javadoc for an element.
|
The code to find the Javadoc for an element is currently duplicated in the classes JavadocView -> getJavadocHtml and JavadocHover -> getHoverInfo. This needs to be consolidated to a common class.
|
2012-12-05 11:11:12
| 1,354,720,000
|
resolved fixed
|
20c463d
| 1,360,600,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/InfoViewMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
82
| 399,665
|
Bug 399665 Part references leak view/editor site after part is disposed
|
In the E4 compatibility layer, part references leak the view/editor site after the part is disposed. Via selection provider, this leaks the whole part. IWorkbenchPartReference is intended to be a lightweight reference to a part that can be kept even after the part has been disposed. E.g. the Search view uses this to keep a reference to the last opened editor, so that it can reuse it when you step through matches. Here's the reference chain: org.eclipse.ui.editors.text.TextEditor this$0 of org.eclipse.ui.texteditor.AbstractTextEditor$SelectionProvider selectionProvider of org.eclipse.ui.internal.EditorSite editorSite of org.eclipse.ui.internal.EditorReference fReusedEditor of org.eclipse.search.internal.ui.text.EditorOpener fEditorOpener of org.eclipse.search.internal.ui.text.FileSearchPage fPage of org.eclipse.search2.internal.ui.basic.views.SetLayoutAction action of org.eclipse.jface.action.ActionContributionItem innerItem of org.eclipse.jface.action.SubContributionItem data of org.eclipse.swt.widgets.MenuItem [8] of org.eclipse.swt.widgets.MenuItem[64] items of org.eclipse.swt.widgets.Display [JNI Global, Stack Local]
|
2013-01-31 12:44:58
| 1,359,650,000
|
verified fixed
|
abdbb0f
| 1,360,160,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/search/SearchLeakTest.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/search/SearchLeakTestWrapper.java
|
JDT
|
83
| 377,141
|
Bug 377141 [hovering] if-else closing bracket hover should always include else
| null |
2012-04-19 01:46:35
| 1,334,810,000
|
verified fixed
|
59830a7
| 1,360,150,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavaHoverMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavaSourceHover.java
|
JDT
|
84
| 397,467
|
Bug 397467 Javadoc hover/view should linkify package
|
Now that we can show package Javadoc, we should also linkify the package segments in Javadoc headers. We already have links for enclosing method/type of an element, and we should extend this to packages. Package links should not span the whole qualified package name, but only simple names. E.g. for java.lang.ref.Reference, - "java" should link to package "java" - "lang" should link to package "java.lang" - "ref" should link to package "java.lang.ref" The advantage of separately linking super packages are that - super packages become accessible - the browser widget still allows the user to select only parts of a package (if the whole qualified name is a single link, then you cannot select "java.lang" any more)
|
2013-01-04 12:57:06
| 1,357,320,000
|
verified fixed
|
3ee8f8c
| 1,360,080,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementLabelComposer.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/viewsupport/JavaElementLinks.java
|
JDT
|
85
| 396,809
|
Bug 396809 [hovering] Write JUnits for the package hovering feature
|
Write JUnit testcases for the package hovering feature.
|
2012-12-18 03:48:07
| 1,355,820,000
|
resolved fixed
|
d79155d
| 1,359,990,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/AutomatedSuite.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/packageHover/PackageJavadocTests.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
86
| 396,823
|
Bug 396823 Use JavaModelUtil.isPackageInfo(ICompilationUnit) util where applicable
|
Use JavaModelUtil.isPackageInfo(ICompilationUnit) util where applicable. This should only be done when the Package hover work is in 'master'.
|
2012-12-18 05:59:39
| 1,355,830,000
|
resolved fixed
|
52ff99e
| 1,359,640,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.java
|
JDT
|
87
| 399,291
|
Bug 399291 JME in Javadoc hover in compare editor (old Git version)
|
I20130122-0800 - close all editors - open a Java editor for a file from a Git repo - select an older revision in the History view and choose Compare with Workspace - hover over a method or field declaration in the right side of the compare editor => Javadoc hover says an exception occurred. Java Model Exception: Java Model Status [<project root> [in ] is not on its project's build path] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:508) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:521) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:258) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:244) at org.eclipse.jdt.internal.core.PackageFragmentRoot.getKind(PackageFragmentRoot.java:481) at org.eclipse.jdt.internal.corext.javadoc.JavaDocLocations.getExplanationForMissingJavadoc(JavaDocLocations.java:647) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo(JavadocHover.java:651) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.internalGetHoverInfo(JavadocHover.java:567) at org.eclipse.jdt.internal.ui.text.java.hover.JavadocHover.getHoverInfo2(JavadocHover.java:559) at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:163) at org.eclipse.jdt.internal.ui.text.java.hover.BestMatchHover.getHoverInfo2(BestMatchHover.java:129) at org.eclipse.jdt.internal.ui.text.java.hover.JavaEditorTextHoverProxy.getHoverInfo2(JavaEditorTextHoverProxy.java:85) at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166)
|
2013-01-28 13:25:25
| 1,359,400,000
|
verified fixed
|
9dbbfa2
| 1,359,470,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
88
| 397,465
|
Bug 397465 [hovering] Open Declaration doesn't work in Javadoc hover on IPackageFragment
|
Open Declaration doesn't work in Javadoc hover on IPackageFragment. This action is available in the toolbar of the Javadoc view and in rich Javadoc hovers. It's also available via the element icon in the Javadoc header (the icon is a clickable link). If there's a package-info.(java|class) or package.html file, then we should open that one in an editor. Otherwise, we should open the Package Explorer and select/reveal the package fragment.
|
2013-01-04 12:34:26
| 1,357,320,000
|
verified fixed
|
e775f37
| 1,359,420,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/JavadocView.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/OpenAction.java
|
JDT
|
89
| 399,087
|
Bug 399087 [push down] search Referencing problem in PushDownRefactoringProcessor
|
the code in the method PushDownRefactoringProcessor.getReferencingElementsFromSameClass(): for (int j= 0; j < results.length; j++) { SearchMatch searchResult= results[i]; result.add(SearchUtils.getEnclosingJavaElement(searchResult)); } It seems results[i] should be results[j].
|
2013-01-25 08:46:37
| 1,359,120,000
|
resolved fixed
|
fc51e8b
| 1,359,370,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/PushDownRefactoringProcessor.java
|
JDT
|
90
| 398,965
|
Bug 398965 [preferences] UI option for syntactic analysis for fields
| null |
2013-01-24 07:52:48
| 1,359,030,000
|
resolved fixed
|
7bf809d
| 1,359,110,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ProblemSeveritiesConfigurationBlock.java
|
JDT
|
91
| 396,808
|
Bug 396808 [hovering] Package hovering shows multiple hyperlinks if the package is present in multiple location in the build path.
|
Hover over the package import java.lang.*; code present in a java file. Make sure the package is present in multiple jars and the jars are included in the classpath of the current project. While hovering multiple links of "java.lang" are displayed in the hover window and all of them point to the same Javadoc content. Duplicate link should not be displayed in the hover window if the Javadoc contents are the same.
|
2012-12-18 03:38:27
| 1,355,820,000
|
resolved fixed
|
b07362b
| 1,358,860,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/hover/JavadocHover.java
|
JDT
|
92
| 398,383
|
Bug 398383 The NewWizardMenu class gets leaked when ever calling a context menu
|
Steps to reproduce: Call a context menu in a view/editor more times. The issue happens in the Java Editor, the Package Explorer, Project Explorer , Navigator views ... Attached is a patch.
|
2013-01-17 07:23:21
| 1,358,430,000
|
verified fixed
|
0fcc8cb
| 1,358,840,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/actions/NewWizardsActionGroup.java
|
JDT
|
93
| 393,719
|
Bug 393719 [compiler] inconsistent warnings on iteration variables
| null |
2012-11-06 17:17:40
| 1,352,240,000
|
verified fixed
|
8090b38
| 1,358,780,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/Java50Fix.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/QuickFixProcessor.java
|
JDT
|
94
| 398,076
|
Bug 398076 Add test cases for bug 357450
| null |
2013-01-14 08:51:37
| 1,358,170,000
|
resolved fixed
|
9a9b9d6
| 1,358,770,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/packageview/ContentProviderTests6.java org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/packageview/PackageExplorerTests.java
|
JDT
|
95
| 397,888
|
Bug 397888 Unused type parameter problem should also depend on option to consider @param tag
| null |
2013-01-10 11:43:50
| 1,357,840,000
|
verified fixed
|
b69e448
| 1,358,770,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ProblemSeveritiesConfigurationBlock.java
|
JDT
|
96
| 398,112
|
Bug 398112 [save actions] Save Actions create inconsistency
|
I activated the save actions in Eclipse 4.3 Integration build (format at save and organization of imports). I'm also using a type filter for java.awt.* and javax.swing.* If I delete the import statements with Ctrl+D and save parts of the imports are created, except the import for the SWT Text widget because Eclipse has several possible imports. So I use Ctrl+O to import the correct package. If I now try to save via Ctrl+S I get the information that the file is out-of-sync and that save failed (see attached screenshot). This is repeatable, sometimes I have to do the whole thing 2-3 times to get this errors. Try the following steps with the attached project: Setup: 1.) Activate Save Actions and Type filter as described above 2.) Import attacshed example project 3.) Open the TodoDetailPart class Test 1.) Delete import statements via Ctrl+D 2.) Ctrl+S 3.) Ctrl+O select the SWT Text widget import 4.) Ctrl+S -> should fail If 4.) does not fail, repeat at least 5 times.
|
2013-01-14 13:17:58
| 1,358,190,000
|
verified fixed
|
51636e9
| 1,358,440,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitDocumentProvider.java
|
JDT
|
97
| 393,161
|
Bug 393161 [type wizards] Pre-fill package name in the new class dialog
|
If the new java class wizard is executed against a project and the project does not have any packages yet then the package field should be prefilled with the named of the project. Reproduce. Create an empty project go to the source folder select new class the package field is empty and it requires a lot of work to fill it in with the name of the project, which should, by convention, be the name of the top level package.
|
2012-10-30 11:35:16
| 1,351,610,000
|
resolved fixed
|
d473e3c
| 1,358,170,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewPackageWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewTypeWizardPage.java
|
JDT
|
98
| 392,946
|
Bug 392946 [quick fix] for unused type parameter
|
Add quick fixes for unused type parameters. This is similar to unused method parameters, so fixes will also be similar (remove, add documentation). Don't add a clean up to remove all, since this would break existing references.
|
2012-10-26 14:50:56
| 1,351,280,000
|
resolved fixed
|
b56753a
| 1,357,850,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/FixMessages.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/fix/UnusedCodeFix.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/CorrectionMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/JavadocTagsSubProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/LocalCorrectionsSubProcessor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/QuickFixProcessor.java
|
JDT
|
99
| 397,842
|
Bug 397842 Class file shown with incorrect content
|
If output folder is equal to source folder, trying to open a class file shows previous content of source file. Steps to reproduce: 1. Create new Java project. Use project folder as root for sources and class files for simplicity. 2. Create new class X. 3. Build project, X.class is generated. 4. Try to open X.class. => ClassFileEditor is opened for X.class showing content of X.java. 5. Modify X.java e.g. add new method. 6. Build project, X.class is regenerated. 7. Try to open X.class. => ClassFileEditor is opened for X.class showing previous content of X.java. In point 4 and 7, if output folder was different than source folder, ClassFileEditor would show "Source not found" message and correct compiled content of X.java.
|
2013-01-10 06:34:04
| 1,357,820,000
|
resolved fixed
|
0d0cfe4
| 1,357,820,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/ClassFileDocumentProvider.java
|
JDT
|
100
| 396,977
|
Bug 396977 [jar exporter] Wrong library order in manifest generating a jar file with "runnable JAR file" option
| null |
2012-12-20 04:10:33
| 1,355,990,000
|
resolved fixed
|
b267310
| 1,357,660,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/FatJarPackageWizardPage.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/FatJarRsrcUrlManifestProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/UnpackJarBuilder.java
|
JDT
|
101
| 396,759
|
Bug 396759 [implementation] Editor saves over changed file
|
I find that if I open a file, make a change but do not save it to disk, then switch branches with egit, I get no prompt or reminder that my edit is incomplete, or that I may corrupt the equivalent file in the switched-to branch. Should it be possible to switch branches with unsaved editing changes?
|
2012-12-17 09:53:50
| 1,355,760,000
|
verified fixed
|
5964182
| 1,357,230,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/CompilationUnitDocumentProvider.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaEditorMessages.java
|
JDT
|
102
| 319,054
|
Bug 319054 Eclipse deletes all files when I cancel a project creation (symlink in project location path)
|
Build Identifier: 20100218-1602 There were a directory (named "prj_it") which had the following structure: aub_o/ bin/ KNF/ src/ The path for prj_it in my file system is: /home/mateus/dev/prj_it In /home/mateus there is also a symbolic link (named "prj_it") that points to dev/prj_it I tried to create a new Java project, using "prj_it" as base. ("Create project from existing source") I selected the symbolic link prj_it (/home/mateus/prj_it) as the path to the project. It appears the message: "The output folder has changed. Do you want to remove the old location 'prj_it/bin' and its content?" So I selected to cancel and I clicked in the "Back" button. Then all files in all subdirectories of prj_it were gone! The subdirectories (aub_o, bin, KNF, and src) are still there, but now they are empty. If I select the complete path (/home/mateus/dev/prj_it) instead of the symbolic link, that error does not happen. Reproducible: Always Steps to Reproduce: 1. Click on menu File -> New -> Java Project 2. Select the option "Create project from existing source" 3. Click on "Browse" button 4. Select a symbolic link that points to the desired directory and click on "OK" button 5. Click on "Next >" button It will appear the message: "The output folder has changed. Do you want to remove the old location 'prj_it/bin' and its content?" 6. Click on "Cancel" button 7. Click on "< Back" button
|
2010-07-06 16:32:32
| 1,278,450,000
|
verified fixed
|
a0d2d3a
| 1,355,930,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewJavaProjectWizardPageTwo.java
|
JDT
|
103
| 395,919
|
Bug 395919 [preferences][syntax coloring] Preview incorrect for parameter variables setting
|
Build id: 20120920-0800 Steps to reproduce: 1. Go to Syntax Coloring [Window -> Preferences -> Java -> Editor -> Syntax Coloring] 2. Enable coloring of parameter variables [Java -> Parameter variables] 3. Turn on strike-through. 4. Check in Preview that the parameter declaration has changed but a reference to the parameter has not. 5. Click Apply. 6. Check in a Java Editor that both parameter declarations and parameter references have changed. There are two settings for local variables, Local variable declarations and Local variable references, so from the way the Preview pane works it seems like there should be a separate setting called Parameter variable references but it is missing.
|
2012-12-06 07:27:44
| 1,354,800,000
|
resolved fixed
|
a8f98a6
| 1,355,140,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/JavaEditorColoringConfigurationBlock.java
|
JDT
|
104
| 395,691
|
Bug 395691 [search] NPE when trying to search for a method declaration
|
3.8.1 M20121003-1000 What steps will reproduce the problem? 1. Ctrl + H 2. Java Search 3. get*raw* 4. Method, Declarations, Source, Workspace These are the exact steps, however I wasn't able to reproduce it once I closed and reopened the dialog. While it was open I was hit by the exception each time I pressed 'Search'. -- Error Details -- Date: Tue Dec 04 12:43:54 CET 2012 Message: Unhandled event loop exception Severity: Error Product: Eclipse SDK 3.8.1.v201210031000 (org.eclipse.sdk.ide) Plugin: org.eclipse.ui Session Data: eclipse.buildId=M20121003-1000 java.version=1.7.0_07 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=pl_PL Command-line arguments: -os win32 -ws win32 -arch x86_64 Exception Stack Trace: java.lang.NullPointerException at org.eclipse.jdt.internal.ui.viewsupport.JavaElementLabelComposer.appendElementLabel(JavaElementLabelComposer.java:258) at org.eclipse.jdt.ui.JavaElementLabels.getElementLabel(JavaElementLabels.java:518) at org.eclipse.jdt.ui.JavaElementLabels.getElementLabel(JavaElementLabels.java:491) at org.eclipse.jdt.internal.ui.search.JavaSearchScopeFactory.getSelectionScopeDescription(JavaSearchScopeFactory.java:254) at org.eclipse.jdt.internal.ui.search.JavaSearchScopeFactory.getSelectionScopeDescription(JavaSearchScopeFactory.java:243) at org.eclipse.jdt.internal.ui.search.JavaSearchPage.performNewSearch(JavaSearchPage.java:331) at org.eclipse.jdt.internal.ui.search.JavaSearchPage.performAction(JavaSearchPage.java:298) at org.eclipse.search.internal.ui.SearchDialog.performAction(SearchDialog.java:476) at org.eclipse.search.internal.ui.util.ExtendedDialogWindow.buttonPressed(ExtendedDialogWindow.java:164) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.search.internal.ui.OpenSearchDialogAction.run(OpenSearchDialogAction.java:54) at org.eclipse.search.internal.ui.OpenSearchDialogAction.run(OpenSearchDialogAction.java:45) at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:289) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1262) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1104) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1100) at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1521) at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4640) at org.eclipse.swt.widgets.Tree.WM_CHAR(Tree.java:5962) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4528) at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:5958) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4989) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2546) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3756) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) at org.eclipse.equinox.launcher.Main.run(Main.java:1438) at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
|
2012-12-04 06:49:45
| 1,354,620,000
|
resolved fixed
|
d51a4f9
| 1,354,630,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/search/JavaSearchPage.java
|
JDT
|
105
| 395,007
|
Bug 395007 [package explorer] Refresh action not available on Java package folders
|
M3. F5 (Refresh) is available as a context menu entry for ordinary source folders but not for Java package folders in the e4 Java Package explorer. Please restore the 3.x functionality.
|
2012-11-24 10:25:34
| 1,353,770,000
|
verified fixed
|
dcacd5c
| 1,353,920,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/actions/RefreshAction.java
|
JDT
|
106
| 394,950
|
Bug 394950 [infer type arguments] AssertionFailedException when there is only an array field
|
Steps to reproduce: 1. Invoke "Infer Generic Type Arguments" on the class below 2. There is an exception thrown ("AssertionFailedException") during check of final conditions class InferGenericTypeArgumentsBug1 { public int[] data; } Few lines from .log file: org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) at org.eclipse.jdt.internal.corext.refactoring.typeconstraints.typesets.SubTypesOfSingleton.<init>(SubTypesOfSingleton.java:29) ...
|
2012-11-22 20:16:19
| 1,353,630,000
|
resolved fixed
|
5add29d
| 1,353,680,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/generics/InferTypeArgumentsConstraintCreator.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/typeconstraints/types/TypeEnvironment.java
|
JDT
|
107
| 394,296
|
Bug 394296 [clean up] Clean up doesn't work if warnings were suppressed
|
I noticed that the "Source > Clean Up..." action doesn't cleanup defects when warnings were suppressed. For example, if I ask the cleanup to add missing Overrides and I have disabled all warnings, then the @Override is not added. If I remove the "@SuppressWarnings("all")", then the @Override is added: @SuppressWarnings("all") public class Test extends java.util.ArrayList<String> { private static final long serialVersionUID = -394398626433235653L; public boolean add(String e) { return super.add(e); } } The same thing happens for "use modifier 'final' where possible", "Change all accesses through subtypes", "Remove unnecessary '$NON-NLS$' tags", etc. rendering the Cleanup action much less useful in the presence of a @SuppressWarnings("all"). -- Eclipse SDK Version: 3.8.1 Build id: M20120914-1540
|
2012-11-14 10:03:31
| 1,352,910,000
|
resolved fixed
|
d357dfb
| 1,352,990,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/cleanup/CleanUpRequirements.java
|
JDT
|
108
| 393,147
|
Bug 393147 Bugs in AdvancedQuickAssistProcessor.getConvertIfElseToSwitchProposals
| null |
2012-10-30 09:49:05
| 1,351,600,000
|
resolved fixed
|
f981ac7
| 1,352,480,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java
|
JDT
|
109
| 393,829
|
Bug 393829 [change method signature] Precondition fails with exception when applying refactoring on a method of an anonyous class passed as argument
|
Steps to reproduce: 1. Invoke "Change Method Signature" on method "a" 2. Reorder parameters "par1" and "par2" (i.e., put "par1" "Down") 3. There is an exception reported in a dialog public class ChangeMethodSignatureBug { public ChangeMethodSignatureBug(Object obj) { } public void m() { new ChangeMethodSignatureBug(new Object() { public void a(Object par1, Object par2) { } }); } }
|
2012-11-07 23:12:18
| 1,352,350,000
|
resolved fixed
|
ed033c1
| 1,352,470,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/ChangeSignature/canModify/A_testAnonymous01_in.java org.eclipse.jdt.ui.tests.refactoring/resources/ChangeSignature/canModify/A_testAnonymous01_out.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/ChangeSignatureTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/TypeContextChecker.java
|
JDT
|
110
| 393,932
|
Bug 393932 [refactoring] pull-up with "use the destination type where possible" creates bogus import of nested type
|
Given this class: package p; public class C { protected class I1 { } protected class I2 extends I1 { protected void foo() { } } void test(I2 i) { i.foo(); } } When pulling up foo() to I1 and enabling "use the destination type where possible" the change in test(..) creates a bogus import of the inner class I1. Result is: package p; import p.C.I1; // BUG public class C { protected class I1 { protected void foo() { } } protected class I2 extends I1 { } void test(I1 i) { i.foo(); } } The bug seems to originate from the fact that SuperTypeRefactoringProcessor.createCorrespondingNode(CompilationUnitRewrite, TType) calls ImportRewrite.addImportFromSignature(String,AST) with no proper ImportRewriteContext.
|
2012-11-08 17:14:05
| 1,352,410,000
|
resolved fixed
|
686e984
| 1,352,470,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/constraints/SuperTypeRefactoringProcessor.java
|
JDT
|
111
| 393,007
|
Bug 393007 AbstractInfoView#selectionChanged(..) calls codeResolve in the UI thread if linking is disabled
|
AbstractInfoView#selectionChanged(..) calls codeResolve in the UI thread if linking is disabled. findSelectedJavaElement(..) is a potentially long-running operation, that's why it's normally called in a background thread. It should also be done in the bg if linking is disabled.
|
2012-10-28 15:55:10
| 1,351,450,000
|
verified fixed
|
cd5dd80
| 1,351,510,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/infoviews/AbstractInfoView.java
|
JDT
|
112
| 392,847
|
Bug 392847 Endless loop in AdvancedQuickAssistProcessor.getConvertIfElseToSwitchProposals
|
Endless loop in AdvancedQuickAssistProcessor.getConvertIfElseToSwitchProposals: void foo(String[] args) { int n = 42; if (n == args.length) // quick assist on 'if' System.out.println(); else { } } "main" prio=6 tid=0x008ebc00 nid=0xcd0 runnable [0x003dd000] java.lang.Thread.State: RUNNABLE at java.util.HashMap.get(HashMap.java:303) at org.eclipse.jdt.core.dom.DefaultBindingResolver.resolveTypeBindingForName(DefaultBindingResolver.java:910) - locked <0x17b345b0> (a org.eclipse.jdt.core.dom.DefaultBindingResolver) at org.eclipse.jdt.core.dom.DefaultBindingResolver.resolveExpressionType(DefaultBindingResolver.java:693) - locked <0x17b345b0> (a org.eclipse.jdt.core.dom.DefaultBindingResolver) at org.eclipse.jdt.core.dom.Expression.resolveTypeBinding(Expression.java:108) at org.eclipse.jdt.internal.ui.text.correction.AdvancedQuickAssistProcessor.getConvertIfElseToSwitchProposals(AdvancedQuickAssistProcessor.jav a:2494) at org.eclipse.jdt.internal.ui.text.correction.AdvancedQuickAssistProcessor.getConvertIfElseToSwitchProposals(AdvancedQuickAssistProcessor.jav a:2439) at org.eclipse.jdt.internal.ui.text.correction.AdvancedQuickAssistProcessor.getAssists(AdvancedQuickAssistProcessor.java:197) ... Furthermore, I saw code like this in that method: IVariableBinding binding= (IVariableBinding) qualifiedName.resolveBinding(); if (binding.isEnumConstant()) { ... }
|
2012-10-25 12:12:46
| 1,351,180,000
|
verified fixed
|
bf49334
| 1,351,300,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/AdvancedQuickAssistTest.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/correction/AdvancedQuickAssistProcessor.java
|
JDT
|
113
| 364,628
|
Bug 364628 [JUnit] Having a plus sign in Eclipse's path causes NPE in the Classpath Variables preferences page
| null |
2011-11-23 12:16:18
| 1,322,070,000
|
resolved fixed
|
f027a63
| 1,351,280,000
|
org.eclipse.jdt.junit.core/src/org/eclipse/jdt/internal/junit/buildpath/P2Utils.java
|
JDT
|
114
| 391,520
|
Bug 391520 [preferences] UI addition: Warning for Unused Generic Parameter
| null |
2012-10-10 06:10:26
| 1,349,860,000
|
verified fixed
|
c6382f8
| 1,351,280,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ProblemSeveritiesConfigurationBlock.java
|
JDT
|
115
| 392,931
|
Bug 392931 Option to not create an @Override annotation when implementing interface method in 1.6
| null |
2012-10-26 12:31:18
| 1,351,270,000
|
resolved fixed
|
8748c9f
| 1,351,270,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility2.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/NameConventionConfigurationBlock.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/PreferencesMessages.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/ProblemSeveritiesConfigurationBlock.java
|
JDT
|
116
| 391,016
|
Bug 391016 [organize imports] null returned even though SharedASTProvider.WAIT_YES was used
| null |
2012-10-03 09:37:35
| 1,349,270,000
|
verified fixed
|
5f6b045
| 1,350,910,000
|
org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/AddImportsOperation.java
|
JDT
|
117
| 387,940
|
Bug 387940 [quick fix] Add unimplemented methods quickfix add incorrect visibility
| null |
2012-08-23 23:15:32
| 1,345,780,000
|
resolved fixed
|
e915fb0
| 1,350,540,000
|
org.eclipse.jdt.ui.tests/ui/org/eclipse/jdt/ui/tests/quickfix/LocalCorrectionsQuickFixTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility2.java
|
JDT
|
118
| 388,078
|
Bug 388078 [inline] inline logical or in and expression goes wrong
|
If I inline a boolean or expression into an and expression, the operator precedence is ignored. boolean doitOr(boolean a, boolean b, boolean c) { boolean or = a || b; return or && c; } Inline local variable 'or' yields the wrong result: boolean doitOr(boolean a, boolean b, boolean c) { return a || b && c; } while plus workd int doitPlus(int a, int b, int c) { int plus = a + b; return plus * c; } resolves correct to: int doitPlus(int a, int b, int c) { return (a + b) * c; }
|
2012-08-27 03:08:43
| 1,346,050,000
|
resolved fixed
|
27b5ebd
| 1,350,540,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/InlineTemp/canInline/A_test48_in.java org.eclipse.jdt.ui.tests.refactoring/resources/InlineTemp/canInline/A_test48_out.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/InlineTempTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/InlineTempRefactoring.java
|
JDT
|
119
| 391,265
|
Bug 391265 [code templates] JavaDoc {@link} and @See are not generated correctly for generic method arguments
|
In JavaDoc blocks, {@link}s to methods in other classes, where the method takes a generic argument, are not identified correctly by (I assume) the parser, resulting in two observed bugs. For example, given these classes: --- package pk1; public class A { /** * Generic */ public <T> void method(T t) {} /** * Generic array */ public <T> void method(T[] t) {} } --- package pk1; /** * {@link pk1.A#method(T)}. * {@link pk1.A#method(T[])}. */ public class B {} --- package pk2; public class T {} --- The following can be observed. 1. The ctrl+click navigation to the methods does not work. For class B you can navigate to class A directly, but there is no active link available for the methods. 2. On origination of imports for class B, the import pk2.T; is brought in. (Additionally this effects the behavior of 1., ctrl+click will go to the correct methods, however the T becomes an active link to class T.) -- Configuration Details -- Product: Eclipse 1.5.1.20120828-0743 (org.eclipse.epp.package.jee.product) Installed Features: org.eclipse.jdt 3.8.1.v20120814-104540-8-8nFqpFNOfwKDRVz-tXOcL5d_83
|
2012-10-05 15:47:27
| 1,349,470,000
|
resolved fixed
|
24f1c49
| 1,349,800,000
|
org.eclipse.jdt.text.tests/src/org/eclipse/jdt/text/tests/contentassist/CodeCompletionTest.java org.eclipse.jdt.ui/core extension/org/eclipse/jdt/internal/corext/codemanipulation/StubUtility.java
|
JDT
|
120
| 390,546
|
Bug 390546 [rulers] Quick fix invoked even if warning/error is not shown in vertical ruler
|
A line of java can have multiple markers, e.g. the yellow warning marker AND the up arrow marker for opening the 'super' declaration. The general annotation preferences can be set such that the yellow warning marker will not appear in the left margin, and then the only thing that appears is the up arrow for opening the supertype declaration. However, if I click that up arrow, what pops up is still the set of proposals to fix the warning. Eclipse simply does not react to what is actually displayed.
|
2012-09-27 07:15:43
| 1,348,740,000
|
verified fixed
|
f412264
| 1,349,260,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaSelectAnnotationRulerAction.java
|
JDT
|
121
| 272,342
|
Bug 272342 [content assist] Content assist in Display, Expressions and Variables views should show Javadoc
|
I20090414-0800 Content assist in Display and Variables views should show Javadoc in the additional info window next to the proposals list.
|
2009-04-15 12:33:08
| 1,239,810,000
|
verified fixed
|
a1bc312
| 1,347,890,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/LazyJavaTypeCompletionProposal.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/CompletionProposalCollector.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/JavaContentAssistInvocationContext.java
|
JDT
|
122
| 388,342
|
Bug 388342 [type wizards] Main Method Stub Check Box in the Class Wizard Stays Checked the Next Time It Loads
|
Back in version 3.7 of the Eclipse Java IDE, when you checked the box "public static void main(String[] args)", it would generate the main method, but the next time you created a class with the wizard, that box would not be checked. Now that I am using version 4.2, I am noticing that the check box stays checked. This is annoying because most of the time, when creating a class, you don't need a main. It is a special case. So the default should be unchecked, not whatever the previous state of the box was. It would be nice if the behaviour returned to the original, that is, that the box always starts out as unchecked.
|
2012-08-29 10:15:12
| 1,346,250,000
|
resolved fixed
|
aa12c6c
| 1,346,680,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewClassWizardPage.java
|
JDT
|
123
| 386,518
|
Bug 386518 [extract method] CCE in ExtractMethodRefactoring#createMethodBody(..)
|
From my logfile: !SESSION 2012-08-02 08:19:17.758 ----------------------------------------------- eclipse.buildId=I20120608-1400 java.version=1.7.0_04 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.jface.text 2 0 2012-08-02 10:10:56.675 !MESSAGE !STACK 0 java.lang.ClassCastException: org.eclipse.jdt.core.dom.ChildPropertyDescriptor cannot be cast to org.eclipse.jdt.core.dom.ChildListPropertyDescriptor at org.eclipse.jdt.internal.corext.refactoring.code.ExtractMethodRefactoring.createMethodBody(ExtractMethodRefactoring.java:1115) at org.eclipse.jdt.internal.corext.refactoring.code.ExtractMethodRefactoring.createNewMethod(ExtractMethodRefactoring.java:960) at org.eclipse.jdt.internal.corext.refactoring.code.ExtractMethodRefactoring.createChange(ExtractMethodRefactoring.java:508) at org.eclipse.jdt.internal.ui.text.correction.proposals.RefactoringCorrectionProposal.createTextChange(RefactoringCorrectionProposal.java:59) at org.eclipse.jdt.ui.text.java.correction.CUCorrectionProposal.createChange(CUCorrectionProposal.java:244) at org.eclipse.jdt.ui.text.java.correction.ChangeCorrectionProposal.getChange(ChangeCorrectionProposal.java:355) at org.eclipse.jdt.ui.text.java.correction.CUCorrectionProposal.getTextChange(CUCorrectionProposal.java:254) at org.eclipse.jdt.ui.text.java.correction.CUCorrectionProposal.getAdditionalProposalInfo(CUCorrectionProposal.java:141) at org.eclipse.jdt.internal.ui.text.correction.proposals.RefactoringCorrectionProposal.getAdditionalProposalInfo(RefactoringCorrectionProposal.java:71) at org.eclipse.jface.text.contentassist.AdditionalInfoController$3.run(AdditionalInfoController.java:106) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
|
2012-08-02 14:39:35
| 1,343,930,000
|
resolved fixed
|
f3a6bb4
| 1,346,090,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/code/ExtractMethodAnalyzer.java
|
JDT
|
124
| 332,635
|
Bug 332635 [nls tooling] Eclipse style NLS: Property key hyperlinks do not work for properties files coming from a JAR
| null |
2010-12-15 09:36:45
| 1,292,420,000
|
resolved fixed
|
a5222bd
| 1,346,080,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/OpenAction.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertyKeyHyperlink.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/propertiesfileeditor/PropertyKeyHyperlinkDetector.java
|
JDT
|
125
| 337,086
|
Bug 337086 [nls tooling] "Source > Externalize strings" throws IAE when .properties file contains invalid unicode escape
| null |
2011-02-13 23:54:46
| 1,297,660,000
|
resolved fixed
|
5241b0d
| 1,345,730,000
|
org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/ExternalizeWizard.java org.eclipse.jdt.ui/ui refactoring/org/eclipse/jdt/internal/ui/refactoring/nls/NLSUIMessages.java
|
JDT
|
126
| 364,539
|
Bug 364539 [generate constructor] Generate constructor using fields globally sets access modifier to private
|
Build Identifier: 20110916-0149 When using 'Generate Constructor using fields...' on an enum with private field the access modifier is disabled and set to private (which is perfectly ok). Afterwards the access modifier is always set to private, even if you use 'Generate Constructor using fields...' on a class. Eclipse should not remember the private access modifier when it is given and disabled. Reproducible: Always Steps to Reproduce: 1. Create an Enum 2. Create a private field 3. Use 'Generate Constructor using fields...' to create the constructor 4. Create a class 5. Create a private field 6. Use 'Generate Constructor using fields...' to create the constructor -> the access modifier is now set to private regardless of the previous setting
|
2011-11-23 02:52:34
| 1,322,030,000
|
resolved fixed
|
3f6103c
| 1,345,660,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/SourceActionDialog.java
|
JDT
|
127
| 387,536
|
Bug 387536 [type wizards] generate main method stub ignores generate comments setting
|
The new class wizard allows to create a main(String[]) method stub. However it ignores the "Do you want to add comments?" setting and always adds a comment.
|
2012-08-18 10:39:53
| 1,345,300,000
|
resolved fixed
|
93d3986
| 1,345,560,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/wizards/NewClassWizardPage.java
|
JDT
|
128
| 172,388
|
Bug 172388 [open type] Open Type dialog shows different JRE libraries with identical text
|
Build ID: I20061214-1445 Steps To Reproduce: 1) Compile your own rt.jar for jdk1.6.0, with all debugging information included, for example. (An exact copy will do for purposes of time.) Name it rt_g.jar. 2) Go to Eclipse Preferences, Java, Installed JREs. Copy existing "jdk1.6.0" to "jdk1.6.0_debug". 3) Edit "jdk1.6.0" debug, including built "rt_g.jar" directly above default "rt.jar". 4) Create 2 projects in workspace, one using the default "jdk1.6.0" JRE, the other using the customized "jdk1.6.0_debug" JRE. 5) Bring up the "Open Type" dialog. Search for java.lang.Object. 2 identical entries will appear: Object - java.lang - [jdk1.6.0] Object - java.lang - [jdk1.6.0] There is no way to differentiate between these two. However, opening either does, in fact, open 2 different files. One opens the Object.class (showing source) for the instance in rt.jar. The other shows the instance from rt_g.jar. 6) These tagged names appear to be the name as entered on the JRE under preferences. Renaming "jdk1.6.0" to "test jdk1.6.0" will result in a repeat of this test showing: Object - java.lang - [test jdk1.6.0] Object - java.lang - [test jdk1.6.0] 7) Now, removing the ORIGINAL "jdk1.6.0" all together (now called "test jdk1.6.0") shows a different result: Object - java.lang - C:\Program FilesJava\jdk1.6.0\jre\lib\rt.jar Object - java.lang - C:\Program FilesJava\jdk1.6.0\rt_g.jar (The above looks much more like what I would like / expect.) 8) Copying the "jdk1.6.0_debug" back to "jdk1.6.0", AND removing the rt_g.jar from the later will reproduce the undesired result: Object - java.lang - [jdk1.6.0] Object - java.lang - [jdk1.6.0]
|
2007-01-31 16:44:05
| 1,170,280,000
|
resolved fixed
|
b224854
| 1,344,860,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/FilteredTypesSelectionDialog.java
|
JDT
|
129
| 386,807
|
Bug 386807 OptionalMessageDialog must not use CANCEL
|
3.8. Code was introduced that uses the CANCEL constant. This does not work for cases where there are more than 2 buttons and 'Cancel' is not at position 1.
|
2012-08-08 04:51:20
| 1,344,420,000
|
verified fixed
|
4aba90b
| 1,344,420,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/dialogs/OptionalMessageDialog.java
|
JDT
|
130
| 386,762
|
Bug 386762 [preferences] Errors/Warnings page garbled when opened via problem hover
|
On the Mac, the Errors/Warnings page comes up garbled when opened via the problem hover (e.g. hover on an unused variable and then click the toolbar button). The page has a big white area on top that doesn't render widgets, but the widgets are there (mouse clicks still work). Resizing the dialog fixes the problem. The problem is the combination of two calls in OptionsConfigurationBlock: - control.setFocus() in #selectOption(Key) - parent.update() in #highlight(..)
|
2012-08-07 12:26:38
| 1,344,360,000
|
verified fixed
|
fdd0314
| 1,344,360,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.java
|
JDT
|
131
| 381,714
|
Bug 381714 [help] Export runnable jar wizard not documented
| null |
2012-06-05 09:44:32
| 1,338,900,000
|
resolved fixed
|
b4e2790
| 1,344,260,000
|
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/IJavaHelpContextIds.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/jarpackagerfat/FatJarPackageWizardPage.java
|
JDT
|
132
| 385,550
|
Bug 385550 [move method] Update reference to inherited field
|
Here is original source codes: public class A { public int i = 0; } public class B extends A{ public void m(C target) { i++; } } public class C { } Now we apply MOVE refactoring to method "m()" with delegate. The result is shown below: public class A { public int i = 0; } public class B extends A{ public void m(C target) { target.m(this); } } public class C { public void m(B b) { i++; //error } } The inherited variable "i" should be updated to "b.i". -- Configuration Details -- Product: Eclipse 1.5.0.20120131-1544 (org.eclipse.epp.package.jee.product) Installed Features: org.eclipse.jdt 3.8.0.v20120525-1249-8-8nFqlFNOfwKDRGz-pXLdGxEM83
|
2012-07-19 16:28:33
| 1,342,730,000
|
resolved fixed
|
6693cd7
| 1,344,010,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/MoveInstanceMethod/canMove/test47/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInstanceMethod/canMove/test47/out/A.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/MoveInstanceMethodTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInstanceMethodProcessor.java
|
JDT
|
133
| 377,318
|
Bug 377318 [encapsulate field] Encapsulate field in an interface introduces methods (therefore compilation errors)
|
Build Identifier: Version: 3.7.2 Build id: M20120208-0800 Encapsulate field in an interface introduces methods, which leads to compilation errors. public interface EncapsulateField { // ENCAPSULATE FIELD F (use default values in the dialog) public static final int F = 1; } Reproducible: Always Steps to Reproduce: 1. Invoke "Encapsulate Field ..." refactoring on field F (from the example) 2. Refactoring introduces methods in the interface
|
2012-04-20 17:50:12
| 1,334,960,000
|
resolved fixed
|
a747793
| 1,344,010,000
|
org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/RefactoringAvailabilityTester.java
|
JDT
|
134
| 385,989
|
Bug 385989 [move method] Existing type used instead of qualifying the moved one
|
I found Eclipse Move refactoring cannot update "import" statement. Here is an example: ----- package a; public class C { public void m(){} } ----- package b; public class C { public void m(){} } ----- package p; import a.C; public class D { public int i; public void d(Visitor v){ i=0; new C().m(); } } ----- package p; import b.C; public class E { public int j; public void d(Visitor v){ j=0; new C().m(); } } ----- package p; public class Visitor { } ----- Now, please try to apply "move" refactoring to methods "d" in class D and E. "Visitor" class makes a semantic error as shown below: package p; import a.C; public class Visitor { public void d(D d){ d.i=0; new C().m(); } public void d(E e){ e.j=0; new C().m(); //error: C should be b.C } } -- Configuration Details -- Product: Eclipse 1.5.0.20120131-1544 (org.eclipse.epp.package.jee.product) Installed Features: org.eclipse.jdt 3.8.0.v20120525-1249-8-8nFqlFNOfwKDRGz-pXLdGxEM83
|
2012-07-25 17:33:09
| 1,343,250,000
|
resolved fixed
|
cfd2520
| 1,344,010,000
|
org.eclipse.jdt.ui.tests.refactoring/resources/MoveInstanceMethod/canMove/test46/in/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInstanceMethod/canMove/test46/in/B.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInstanceMethod/canMove/test46/out/A.java org.eclipse.jdt.ui.tests.refactoring/resources/MoveInstanceMethod/canMove/test46/out/B.java org.eclipse.jdt.ui.tests.refactoring/test cases/org/eclipse/jdt/ui/tests/refactoring/MoveInstanceMethodTests.java org.eclipse.jdt.ui/core refactoring/org/eclipse/jdt/internal/corext/refactoring/structure/MoveInstanceMethodProcessor.java
|
JDT
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.