@java.lang.Deprecated misses not only the description text but also a 'since' 
field.

It would be really important to know since when a method is deprecated...

LieGrue,
strub



----- Original Message -----
> From: Olivier Lamy <ol...@apache.org>
> To: Maven Developers List <dev@maven.apache.org>
> Cc: 
> Sent: Thursday, May 10, 2012 9:34 PM
> Subject: Re: Plugins with Annotations ETA
> 
> 2012/5/10 Jesse Glick <jesse.gl...@oracle.com>:
>>  On 05/09/2012 12:56 PM, Olivier Lamy wrote:
>>> 
>>>  we still need to do some javadoc parsing for @deprecated
>> 
>> 
>>  Just look for @Deprecated - the real annotation - instead. (Note that javac
>>  will warn you if you have the Javadoc tag without the annotation.)
>> 
>> 
>>>  @since and comments for class/field description. So if annotations 
> comes
>>>  from
>>>  reactor module (easy to scan sources) but if comes from a dependency I
>>>  try to get the sources from the artifact with try to resolve the same
>>>  artifact with classifier sources.
>> 
>> 
>>  Would be simpler to define true annotations (marked @Documented) for the
>>  things you use, e.g. @Since or @Description. Then there is no need to look
>>  for sources of binary dependencies, and no need to parse them. You are also
>>  insulated against Java language changes, and can interoperate properly with
>>  other JVM languages compatible with JSR 175.
> 
> I have this idea first too using only annotations but I don't have
> text in this anno @Deprecated("because bla bla")
> Agree on @Since,
> @Description looks nice but I found a bit ugly something like
> 
> @Description("
> The role names of mojo extractors to use. If not set, all mojo
> extractors will be used. If set to an empty extractor name, no mojo
> extractors will be used. Example:
> <!-- Use all mojo extractors -->
> <extractors/>
> 
> <!-- Use no mojo extractors -->
> <extractors>
>      <extractor/>
> </extractors>
> 
> <!-- Use only bsh mojo extractor -->
> <extractors>
>      <extractor>bsh</extractor>
> </extractors>
> ")
> 
> And furthermore published javadoc won't as nice as today :-)
> 
> Others ?
> 
>> 
>> 
>> 
>>  ---------------------------------------------------------------------
>>  To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>  For additional commands, e-mail: dev-h...@maven.apache.org
>> 
> 
> 
> 
> -- 
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to