On 4/21/2016 7:02 PM, Stuart Marks wrote:
On 4/21/16 4:51 PM, Paul Benedict wrote:
Well, my point was that it becomes redundant coding to specify both
the annotation and the Javadoc tag. It would just seem better, in my
opinion, if doing a @j.l.Deprecated(since="9") triggered whatever
output i
On 4/21/16 4:51 PM, Paul Benedict wrote:
Well, my point was that it becomes redundant coding to specify both the
annotation and the Javadoc tag. It would just seem better, in my opinion, if
doing a @j.l.Deprecated(since="9") triggered whatever output is necessary
during doc generation. It doesn
Well, my point was that it becomes redundant coding to specify both the
annotation and the Javadoc tag. It would just seem better, in my opinion,
if doing a @j.l.Deprecated(since="9") triggered whatever output is
necessary during doc generation. It doesn't make sense to me to require
both. The lang
On 4/21/16 9:51 AM, Paul Benedict wrote:
Is there a requirement that the new "since" attribute on @j.l.Deprecated
lead to an automatic JavaDoc @deprecated in the doc generation? It's a bona
fide replacement, right?
I'm just curious because I think, if that's true, @j.l.Deprecated should
mention
