While obviously CoC is something that is really beneficial to the user's productivity, I do not think we could find a real justification for adding another complex API for a pluggable rule set (it would be counter-productive since it is another thing to learn and support). There are other items besides CoC of much higher and global interest in our stack, so we should keep things simple in this area and just think over a few places where CoC makes really sense instead of doing rocket science.
> -----Original Message-----
> From: Marek Potociar [mailto:marek.potociar_at_oracle.com]
> Sent: Freitag, 8. April 2011 15:22
> To: jsr339-experts_at_jax-rs-spec.java.net
> Cc: Bill Burke
> Subject: [jsr339-experts] Re: Annotations CoC [Was: Convention Over
> Configuration]
>
> On 04/06/2011 07:11 PM, Bill Burke wrote:
> >
> >
> > On 4/6/11 11:27 AM, Guilherme Silveira wrote:
> >> Would we really force just one convention over all java projects?
> The
> >> user who wants to change it will have to change everything
> >>
> >
> > I don't really care to much whether we have this flexibility or not,
> but there's a million other things I'd rather focus
> > on implementing/defining than this.
> >
>
> I tend to agree with Bill on this one. CoC IMHO makes more sense if
> there is a single set of rules to follow. I don't
> see the great benefit of creating CoC framework that would be
> configurable per project or organization. And I really
> think that such task is out of scope.
>
> Marek
>