commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Gaspar" <paulo.gas...@krankikom.de>
Subject RE: Commons Validator Packaging/Content
Date Mon, 07 Jan 2002 01:37:39 GMT
I do NOT mean that way. You have the itch.

Make it visible in the Commons and let the developers decide.

The decision should always be made for the best code base and not
just for the older.


Have fun,
Paulo Gaspar

> -----Original Message-----
> From: Jon Scott Stevens [mailto:jon@latchkey.com]
> Sent: Monday, January 07, 2002 2:14 AM
> To: Jakarta Commons Developers List
> Subject: Re: Commons Validator Packaging/Content
>
>
> on 1/6/02 5:23 PM, "Paulo Gaspar" <paulo.gaspar@krankikom.de> wrote:
>
> > Maybe the way to go is just to move such components to the Commons.
> > Why not moving Intake now?
>
> That is my question. Why doesn't David work towards integrating
> Intake into
> Struts instead of working on pulling what is duplicated from
> Struts out into
> Commons? The answer is simple...it is David's itch to scratch and
> it is the
> simplest thing for him to do. That is the current failure of Jakarta in my
> eyes. Jakarta has become no better than Sourceforge. It is a
> place where you
> can dump your least common denominator.
>
> Instead of Struts working to use Turbine code and then move it
> into Commons.
> Struts came up with their own validation framework, made it
> stable in Struts
> land and is now dumping it into Commons. There is a complete lack of
> communication there.
>
> -jon
>
>
> --
> To unsubscribe, e-mail:
> <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:commons-dev-help@jakarta.apache.org>
>


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


Mime
View raw message