I reaffirm my -1. Since there is overlap between the three plugins, I suggest either a new plugin is created that merges all their respective features, or one of the existing plugins should absorb the others.
Paul On Wed, May 14, 2008 at 9:05 AM, Jeromy Evans < [EMAIL PROTECTED]> wrote: > I haven't tested the latest Convention plugin yet so I can't vote yet, but > I'd probably give a [-1] because I don't like the options provided. > > I support moving Convention plugin from the sandbox to become the > recommended convention for new users, replacing ZeroConfig and CodeBehind. > However, I don't support deprecation of ZeroConfig or CodeBehind until the > REST plugin is fully migrated to use it (if possible) and there's a clear > and minimal migration path for existing users (anyone mention API > compatibility recently?). I would support deprecation later in the 2.1.x > series, but not all in one go. > > Musachy Barroso wrote: > >> With the addition of @IntereceptorRefs to the Convention plugin, it is >> now possible to do most of the action mapping using annotations. Also >> having 2 plugins to do the same thing is really confusing for users, >> so we should deprecate Zero Config (good thing is that it was always >> "experimental"). >> >> If you have had a chance to look at the Convention plugin, please vote: >> >> [+1] Move the Convention plugin to trunk and deprecate Zero Configuration >> plugin >> [-1] Leave it in sandbox. (reasons?) >> >> >> regards >> musachy >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
