[
https://issues.apache.org/jira/browse/LUCENE-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795340#action_12795340
]
Steven Rowe commented on LUCENE-2185:
-------------------------------------
The justification for using @Deprecated, AFAICT, is that conforming compilers
are required to issue warnings for each so-annotated class/method, where
compilers are *not* required to issue warnings for javadoc @deprecated tags,
and although Sun compilers do this, other vendors' compilers might not.
Another (similarly theoretical) argument in favor of using @Deprecated
annotations is that, unlike @deprecated javadoc tags, this annotation is
available via runtime reflection.
A random information point: MYFACES-2135 removed all @Deprecated annotations
from MyFaces code because an apparent bug in the Sun TCK flags methods bearing
this annotation as changing method signatures.
> add @Deprecated annotations
> ---------------------------
>
> Key: LUCENE-2185
> URL: https://issues.apache.org/jira/browse/LUCENE-2185
> Project: Lucene - Java
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Trivial
> Fix For: 3.1
>
> Attachments: LUCENE-2185.patch
>
>
> as discussed on LUCENE-2084, I think we should be consistent about use of
> @Deprecated annotations if we are to use it.
> This patch adds the missing annotations... unfortunately i cannot commit this
> for some time, because my internet connection does not support heavy
> committing (it is difficult to even upload a large patch).
> So if someone wants to take it, have fun, otherwise in a week or so I will
> commit it if nobody objects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
