When generating @deprecated automatically, I would suggest the following
template:
@deprecated since minor.major TODO document deprecation.
The developers could later scan for "TODO document deprecation" and add
the necessary comments.
Also, some methods do have the @deprecated keyword in they documentation
header, are indicated at least by Eclipse editor as deprecated but due
some strange
reason are still criticized as "non deprecated" in japi tests. Probably
japi is sensitive to the
tag order or something like that.
Stuart Ballard wrote:
Looking at the current japi results (which once again blew my mind
with the sheer magnitude of the improvement) I noticed that quite a
lot of (minor) errors are of the form 'deprecated in jdk1x, but not
deprecated in classpath'. It occurred to me that with the output from
japicompat, a copy of the classpath sources and a little perl, it
might be possible to come up with a script that can automatically add
"@deprecated" in the appropriate place on any such class or member,
hence getting an almost instant 0.3% improvement in japi scores which
incidentally would push us over 90% of 1.4, which is a nice little
psychological milestone :)
_______________________________________________
Classpath mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/classpath
