root cause of remaining javadoc failures
Werner Dietl
wdietl at gmail.com
Wed May 8 16:41:37 PDT 2013
Jon,
I expanded on the test case in this changeset:
http://hg.openjdk.java.net/type-annotations/type-annotations/langtools/rev/f90d05a438f4
If an annotation has @Target TYPE_PARAMETER, I would not expect it to
influence the type field of the TypeVariableSymbol. Still, those
declaration annotations do not seem to show up in the generated
javadoc.
It looks like something else is not quite right with how javadoc
handles type parameters. Please let me know if you see what's wrong.
Thanks,
cu, WMD.
On Tue, May 7, 2013 at 2:39 AM, Jonathan Gibbons
<jonathan.gibbons at oracle.com> wrote:
> Werner,
>
> I have tracked down the root cause of the remaining javadoc failures.
>
> Although TypeVariableSymbol implements methods like getAnnotationMirrors, I
> don't think its type field gets set to an AnnotatedType. Therefore, when
> javadoc uses Type.isAnnotated(), it gets a "false" result, causing javadoc
> to believe there are no annotations on the type parameter.
>
> How hard will it be to update the type field on a TypeVariableSymbol, once
> you have determined there are annotations present on the declaration?
>
> -- Jon
>
>
--
http://www.google.com/profiles/wdietl
More information about the type-annotations-dev
mailing list