Community
Participate
Working Groups
package p1; /** * Bla {@link #method(Object[]...)}. * * Auto-complete here # */ public class Test { public void method(Object[]... args) {} public void method2(int arg) {} } - In the above example, press Ctrl+space after # at the specified location. - CompletionProposal.getReplaceStart() for the received proposals returns the offset before the first #. As a result, we get wrong pattern in AbstractJavaCompletionProposal.getPatternMatchRule(String pattern, String string). Here, string is: {@link #method(Object[]...)} - Test and, pattern is: #method(Object[]...)}. * * Auto-complete here # This results in SIOOBE. - In 4.6 M3 build, before AbstractJavaCompletionProposal#getPatternMatchRule was introduced, we used to get incorrect result and the text from the first # onwards was eaten up by applying the proposal.
Initial Analysis: Though the symptoms are similar to the bug 488363, the root cause is different. Here instead of CompletionOnJavadocFieldReference a CompletionOnJavadocMessageSend node is created with reference to "@link #method(Object[]...)}" in Eclipse.4.6M7PLUS [Eclipse Application] org.eclipse.equinox.launcher.Main at localhost:59224 Thread [main] (Suspended (breakpoint at line 20 in CompletionOnJavadocMessageSend)) CompletionOnJavadocMessageSend.<init>(JavadocMessageSend, int) line: 20 CompletionJavadocParser.syntaxRecoverArgumentType(Object, List, Object) line: 860 CompletionJavadocParser.parseArguments(Object) line: 453 CompletionJavadocParser(AbstractCommentParser).parseMember(Object) line: 763 CompletionJavadocParser(AbstractCommentParser).parseReference() line: 1204 CompletionJavadocParser.parseReference() line: 543 CompletionJavadocParser(JavadocParser).parseTag(int) line: 593 CompletionJavadocParser.parseTag(int) line: 556 CompletionJavadocParser(AbstractCommentParser).commentParse() line: 242 CompletionJavadocParser.commentParse() line: 99 moving to 4.7
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
