commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <gudnabr...@yahoo.com>
Subject Re: [validator] Direction of validator implementation based on JSR 303
Date Fri, 23 Oct 2009 15:32:39 GMT
+1

--- On Fri, 10/23/09, Mohammad Nour El-Din <nour.mohammad@gmail.com> wrote:

> From: Mohammad Nour El-Din <nour.mohammad@gmail.com>
> Subject: Re: [validator] Direction of validator implementation based on JSR  303
> To: "Commons Developers List" <dev@commons.apache.org>
> Date: Friday, October 23, 2009, 4:35 AM
> +1
> 
> Actually this is even better to start from scratch. I am in
> Niall.
> 
> On Fri, Oct 23, 2009 at 9:48 AM, Niall Pemberton
> <niall.pemberton@gmail.com>
> wrote:
> > On Fri, Oct 23, 2009 at 8:27 AM, Simone Tripodi
> > <simone.tripodi@gmail.com>
> wrote:
> >> Hi guys,
> >> I don't have the rights to express votes but at
> least please let me
> >
> > Anyone can vote - it may end up we don't agree - but
> votes are appreciated.
> >
> >> say that sounds great, commons-validation has to
> be the proper home
> >> for JSR303, I'd like to contribute in this project
> since I already
> >> started studying the spec :)
> >
> > Great - I'm assuming you're not an existing ASF
> committer, so it'll
> > have to be patches via JIRA tickets:
> >
> > http://commons.apache.org/validator/issue-tracking.html
> >
> > Probably best to ping the list before starting work so
> that we don't
> > end up duplicating effort.
> >
> > Niall
> >
> >> All the best,
> >> Simone
> >>
> >>
> >> On Fri, Oct 23, 2009 at 8:58 AM, Henri Yandell
> <flamefew@gmail.com>
> wrote:
> >>> +!
> >>>
> >>> On Thu, Oct 22, 2009 at 11:17 PM, Paul
> Benedict <pbenedict@apache.org>
> wrote:
> >>>> +1
> >>>>
> >>>> On Thu, Oct 22, 2009 at 9:33 PM, Niall
> Pemberton
> >>>> <niall.pemberton@gmail.com>
> wrote:
> >>>>> The current trunk in the validator2
> sandbox is a copy of the Validator
> >>>>> 1.4 code from "commons proper" - but I
> think we should dump all the
> >>>>> existing validator framework code and
> just retain the "routines"
> >>>>> package. Trying to maintain any sort
> of compatibility with the
> >>>>> existing validator framework would be
> alot more work and code and
> >>>>> create a real mess IMO and I think it
> would be better to not to even
> >>>>> try. The "routines" package was
> refactored realtively recently(!) and
> >>>>> can stand on its own.
> >>>
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >>> For additional commands, e-mail: dev-help@commons.apache.org
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> http://www.google.com/profiles/simone.tripodi
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
> 
> 
> 
> -- 
> Thanks
> - Mohammad Nour
> - LinkedIn: http://www.linkedin.com/in/mnour
> ----
> "Life is like riding a bicycle. To keep your balance you
> must keep moving"
> - Albert Einstein
> 
> "Writing clean code is what you must do in order to call
> yourself a
> professional. There is no reasonable excuse for doing
> anything less
> than your best."
> - Clean Code: A Handbook of Agile Software Craftsmanship
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 
> 


      

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message