Bugzilla – Full Text Bug Listing
| Summary: | [1.5][javadoc][dom] Type references in javadocs should have generic binding, not raw | ||
|---|---|---|---|
| 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 | CC: | eric_jodet, martinae |
| Version: | 3.1 | ||
| Target Milestone: | 3.1 M5 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
Fixed. Now List resolve to a generic type ITypeBinding. [jdt-core-internal] Changes done in internalResolveType(Scope) method of JavadocSingleTypeReference and JavadocQualifiedTypeReference. Test case #testBug80257 added in ASTConverterJavadocTest. Verified in I20050214-0927 for 3.1M5 Bug 83127 showed that all references to generic types in Javadocs should in fact have *raw* bindings. This includes type references. Eric told me he would like to release a patch for bug 209936 which reverts the effects of the fix for this bug. I now agree with that. It looks like I didn't completely understand how the Javadoc tools works when I wrote comment 0. (In reply to comment #3) While implementing the fix for bug 209936, modified the following test case (initially added while fixing this one) in order to conform with the new behavior (all references to generic types in Javadocs will in fact have *raw* bindings): org.eclipse.jdt.core.tests.model ASTConverterJavadocTest#testBug80257() |
I20041201-1139 Type references in javadocs should have a generic binding, not a raw one. In the example below, List in {@link java.util.List} should resolve to an ITypeBinding whose isGenericType() is true (currently: isRaw() is true). That would be in line with the type binding for the references in the import statement, which is also a "general reference" to List. package p; import java.util.List; class A { /** * @return a {@link java.util.List} */ List<String> getList() { return null; } }