+1 for @Exclude(ifProjectStage=...) etc Thus @Exclude will replace @Veto as well.
LieGrue, strub ----- Original Message ----- > From: Pete Muir <[email protected]> > To: [email protected] > Cc: > Sent: Wednesday, January 4, 2012 12:05 PM > Subject: Re: [DISCUSS] merging of features (@Veto, @ProjectStageActivated and > @ExpressionActivated) > > +1 > > This is a significant improvement over what was in Seam and OWB IMO so really > great to see! > > On 4 Jan 2012, at 00:22, Jason Porter wrote: > >> +1 >> >> On Tue, Jan 3, 2012 at 17:09, John D. Ament <[email protected]> > wrote: >> >>> This is very readable. +1 >>> On Jan 3, 2012 4:52 PM, "Gerhard Petracek" > <[email protected]> >>> wrote: >>> >>>> as discussed with mark we could think about details like > inProjectStage >>> vs >>>> ifProjectStage, however, basically +1 >>>> >>>> regards, >>>> gerhard >>>> >>>> >>>> >>>> 2012/1/3 Gerhard Petracek <[email protected]> >>>> >>>>> 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 >>>>> >>>> >>> >> >> >> >> -- >> Jason Porter >> http://lightguard-jp.blogspot.com >> http://twitter.com/lightguardjp >> >> Software Engineer >> Open Source Advocate >> Author of Seam Catch - Next Generation Java Exception Handling >> >> PGP key id: 926CCFF5 >> PGP key available at: keyserver.net, pgp.mit.edu >
