Project: JDT
Bug 153245 [content assist] Must better handle evil javadocCompletionProcessor
Reported: 2006-08-09 04:25:48 | Status: verified fixed

I20060809-0010. Currently an evil javadocCompletionProcessor contribution that takes a long time to complete results in a dialog and there is no way to - detect which processor causes it - disable the bad processor At a minimum for 3.2.1 we must - list all possible candidates - provide a way to disable the LegacyJavadocCompletionProposalComputer

Files changed in fix:
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/text/java/CompletionProposalComputerDescriptor.java org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/java/IJavadocCompletionProcessor.java