in view of all who participated in the original threads, it looks like we already have a majority concerning the basic idea. if there are no objections, i'll start merging it tomorrow. i'll use the names of the original suggestion. (if needed) we can change the details later on (btw. we can discuss them in parallel).
regards, gerhard 2012/1/4 Matthias Wessendorf <[email protected]> > +1 I like it > > On Tue, Jan 3, 2012 at 10:50 PM, Gerhard Petracek > <[email protected]> wrote: > > hi @ all, > > > > we came up with a new idea to merge @Veto, @ProjectStageActivated and > > @ExpressionActivated. > > arne combined [1] some of the previous suggestions and the result would > > solve the @Veto naming discussion as well. > > > > if we merge those features, we would get something like: > > @Exclude > > @Exclude(inProjectStage=Production.class) > > @Exclude(notInProjectStage=UnitTest.class) > > @Exclude(onExpression="myProperty==myValue") > > @Exclude(onExpression="[my custom expression syntax]", > > interpretedBy=CustomExpressionInterpreter.class) > > > > regards, > > gerhard > > > > [1] http://markmail.org/message/6rbzbrtzye3y65lu > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf >
