On 28 June 2012 11:33, Igor Fedorenko <[email protected]> wrote:
> What about inheritance?

+1000 inheritance is one of the reasons we moved to annotations from
javadoc tags (though I agree that plugin.xml merging could solve that
somewhat, it's messy and ties us back rather than forward

> Other tools that may want to do something
> with the annotations?
>
> --
> Regards,
> Igor
>
>
> On 12-06-28 6:06 AM, Olivier Lamy wrote:
>>
>> could be better maybe.
>> But means 1.6 required.
>>
>> Do you want to work on a branch with this change ?
>>
>> 2012/6/28 Milos Kleint <[email protected]>:
>>>
>>> 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 <[email protected]> wrote:
>>>>
>>>> Hi,
>>>> We use asm to collect annotations from compiled classes (so scope
>>>> compile )
>>>> Makes sense ?
>>>>
>>>> 2012/6/28 Milos Kleint <[email protected]>:
>>>>>
>>>>> 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: [email protected]
>>>>> For additional commands, e-mail: [email protected]
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> Talend: http://coders.talend.com
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to