+1 Another great idea!

I think that Dan's suggested approach makes the most long-term sense, because we may (as he said,) want to customize the behavior of an @Alias for each name with which it is invoked.

~Lincoln

On Tue, May 8, 2012 at 9:24 PM, George Gastaldi <gegastaldi@gmail.com> wrote:
Sounds good. Or we could follow the same principle the guys in
Hibernate Validation takes: create a @List inside @Alias containing an
array of @Alias.

Anyway, taking this approach would enable the creation of an @Alias
for each locale. That would rock :)

Regards,

George Gastaldi


2012/5/8 Dan Allen <dan.j.allen@gmail.com>:
> brilliant. +1
>
> It's possible to introduce an @Aliases annotation that accepts a collection
> of @Alias annotations.  this reads nicer and leaves the door open for
> per-alias customizations if we should need them.
>
> --
> Sent from my CyanogenMod-powered
> Android device, an open platform for
> carriers, developers and consumers.
>
> On May 8, 2012 2:55 PM, "George Gastaldi" <gegastaldi@gmail.com> wrote:
>>
>> Hi,
>>
>> I was wondering if it makes sense for a plugin to have multiple alias.
>> Like, for example, the help plugin could be invoked by calling "help"
>> or simply "?".
>>
>> I believe that the @Alias annotation should receive a String[]
>> instead. That could be extended to other use cases as well.
>>
>> WDYT ?
>>
>> Regards,
>>
>> George Gastaldi
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>

_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev



--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."