Jacques Le Roux wrote: > Thanks Adam, > > I did not notice it, and only replicated the old @deprecated comment. > There are 45 such changes (@deprecated comment without any javaDoc > information) to do in current code. If everybody agree I will do > it. In other words I will replace /** @deprecated */ by @Deprecated > > But reading in > http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/deprecation/deprecation.html > > > _I notice :_ > You are strongly recommended to use the Javadoc @deprecated tag with > appropriate comments explaining how to use the new API. This ensures > developers will have a workable migration path from the old API to the > new API. For more information, see Using the @deprecated Javadoc Tag. > NOTE: The Java Language Specification requires compilers to issue > warnings when classes, methods, or fields marked with the @Deprecated > annotation are used. Compilers are not required by the Java Language > Specification to issue warnings when classes, methods, or fields marked > with the @deprecated Javadoc tag are accessed, although the Sun > compilers currently do so. However, there is no guarantee that the Sun > compiler will always issue such warnings.
Then why did they add a @Deprecated, if @Deprecated is itself @Deprecated? /me shoots someone
