On 21/05/2012, at 8:48 AM, Barrie Treloar wrote:
> On Sun, May 20, 2012 at 8:12 PM, Hervé BOUTEMY <[email protected]> wrote:
>> bingo: you got it!
>> ok, now I understand, you're right, I was focused at my property vs
>> expression
>> task and forgot the most normal way of configuring plugins...
>>
>> I'll revert and improve the docs
>
> I've been lurking on this discussion, so I'm not sure my ideas are
> fully baked...
>
> Before you revert, isn't Robert's example behaving like @Inject?
> i.e. you would not use @Parameter any more on these objects.
Right, that was a point I was trying to make in an earlier post, but I confused
it by my last sentence. @parameter default-value="${project}" sounds wrong
because it implies you can actually configure a different project.
I think we want to:
- create a new annotation/attribute to obtain the maven-internal bits; and if
that has happened then...
- move @required to be an attribute of @parameter, as it makes no sense for the
other annotations
- drop @readonly, as it's redundant on every type of annotation
Cheers,
Brett
--
Brett Porter
[email protected]
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
