deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jakob Korherr <jakob.korh...@gmail.com>
Subject Re: [DISCUSS] [DELTASPIKE-8] @Veto
Date Fri, 30 Dec 2011 11:38:41 GMT
I agree with Gerhard. We should definitely start a vote in which every
one can vote for ONE favorite and then pick the one with the most +1s.

Regards,
Jakob

2011/12/30 Gerhard Petracek <gerhard.petracek@gmail.com>:
> the easiest way in this case is a formal vote about @Veto vs @Exclude vs
> @Unmanaged/@NotManaged
>
> regards,
> gerhard
>
>
>
> 2011/12/30 Dan Allen <dan.j.allen@gmail.com>
>
>> On Wed, Dec 28, 2011 at 11:55, Marius Bogoevici
>> <marius.bogoevici@gmail.com>wrote:
>>
>> >  I suggested @Unmanaged (or even @NotManaged, or anything that refers to
>> > "class as a managed bean" in the spirit of 3.1.1). Overall, I think that
>> > @Unmanaged is a better fit, for the reasons I explained previously. I
>> think
>> > that renaming is not such a big issue, in the light of a DeltaSpike
>> > migration.
>> >
>>
>> I agree. The best suggestion yet, esp since we seem to be at an impasse
>> between @Veto and @Exclude.
>>
>> I think that @NotManaged reads better than @Unmanaged, but I would be happy
>> with either one.
>>
>> -Dan
>>
>> --
>> Dan Allen
>> Principal Software Engineer, Red Hat | Author of Seam in Action
>> Registered Linux User #231597
>>
>> http://google.com/profiles/dan.j.allen
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>>



-- 
Jakob Korherr

blog: http://www.jakobk.com
twitter: http://twitter.com/jakobkorherr
work: http://www.irian.at

Mime
View raw message