Summary: | [javadoc] Javadoc reference to constructor of secondary type has no binding / not found by search | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | minor | ||
Priority: | P3 | ||
Version: | 3.1 | ||
Target Milestone: | 3.1 M6 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Markus Keller
2005-01-20 05:23:47 EST
Not a specific 1.5 bug. Enum can be replaced by class A and it fails the same... Fixed. Javadoc parser used main type for implicit reference which was obviously wrong in this case. That's explain this warning and the fact that Search engine didn't find it. Now Javadoc parser stores first type declaration found in parser ast stack and starts from it to bind the reference. If reference is not found, try to resolve in enclosing type or as a constructor call instead of a message send. Also search engine now allows ConstructorLocator to accept message send reference and verify while resolving if it can be bound to a constructor. [jdt-core-internal] Modifications done in SourceElementParser, ContructorLocator, MethodLocator, JavadocAllocationExpression and JavadocMessageSend. Test cases added in JavadocBugsTests and JavaSearchJavadocTests Verified in I20050330-0500 |