maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Milos Kleint <mkle...@gmail.com>
Subject Re: plugin annotations retention policy
Date Thu, 28 Jun 2012 09:55:45 GMT
why not use jdk's own annotation processors (which get compiled by
javac are we save ourselves an extra mojo execution)?

Milos

On Thu, Jun 28, 2012 at 11:50 AM, Olivier Lamy <olamy@apache.org> wrote:
> Hi,
> We use asm to collect annotations from compiled classes (so scope compile )
> Makes sense ?
>
> 2012/6/28 Milos Kleint <mkleint@gmail.com>:
>> Hello,
>>
>> I'm in the process of rewriting the nbm-maven-plugin at mojo to use
>> the new annotations instead of javadoc tags. It appears to be working
>> fine, but I'm wondering why the retention policy is CLASS. Since it's
>> only used to generate the xml file, it could be turned into SOURCE and
>> the annotation dependency could be made "provided". Am I missing
>> something?
>>
>> Regards
>>
>> Milos Kleint
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

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


Mime
View raw message