Adrian Custer a écrit :
> 1645 @source
> doesn't recognize the tag which means that the custom taglet may
> need to be tweaked. This could also be a problem with my
> install.
@source work on my side (on trunk) using the javadoc tools bundled in JSE 5. I
believe that the taglet API changed between J2SE 1.5 and JSE 5, so I suspect
that out custom taglets work only with JSE 5.
> 625 @return
> most of these are simply blank
I would like to remove those blank @return. I find a little bit annoying to
have
so many warning in javadoc.
By the way, what should we do about the "DOCUMENT ME!" texts that appears there
and there?
> 125 @value
> Martin, this is you. It's about @value being for constants. See
> the file attached.
This is again a J2SE 1.4 versus JSE 5 issue; it compile fine with JSE 5.
J2SE 1.4 introduced the [EMAIL PROTECTED] inline tag, which was allowed only in
constant
fields. JSE 5 extended this tag in order to accept the [EMAIL PROTECTED] #ref}
syntax,
where #ref is a reference to a constant field and only this reference need to
be
constant. The reported warnings are actually J2SE 1.4 not recognizing the
extended [EMAIL PROTECTED] #ref} syntax.
> 7 @uml.property
> perhaps points are invalid in custom tags.
Its look like a tag inspired from old GeoAPI practice (we were using a @UML
javadoc tag in early GeoAPI days. We switched to annotations later). I'm not
sure that it apply to Geotools...
Thanks for all your work on javadoc :)
Martin
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
