-Original Message-
From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 01, 2004 5:24 PM
To: Jakarta Commons Developers List
Subject: Re: [lang] Re: cvs commit:
jakarta-commons/lang/src/java/org/apache/commons/lang Validate.java
I'm confused -- why shouldn't
I'm confused -- why shouldn't a class in [lang] have dependencies to
other classes in [lang]? Isn't this taking things too far??
Its part of [lang] being broad and shallow. In effect, [lang] is a loose
grouping of APIs in a similar vein. As such it should be easily broken into
many parts.
ie.
I agree with Michael.
When did this become is this a design goal? I am against it. :-(
It is one thing to say, I'll cut and paste [lang] code /into/ my own
project, and yes, I know about duplicating code, not getting bug fixes,
etc.
It is another to say: Let's inline APIs within [lang] to
Gary Gregory wrote:
Sorry for the flame but this is a 'shake-my-head-in-disbelief' moment
that I find discouraging.
I pretty much agree, but from my POV [lang] stopped moving forward a
while ago anyway. Most new requests
or ideas are rejected as out of scope (which is usually valid), and
the
On Wed, 2004-06-02 at 10:54, Gary Gregory wrote:
I agree with Michael.
When did this become is this a design goal? I am against it. :-(
It is one thing to say, I'll cut and paste [lang] code /into/ my own
project, and yes, I know about duplicating code, not getting bug fixes,
etc.
It
On Tue, 1 Jun 2004, matthew.hawthorne wrote:
Gary Gregory wrote:
Sorry for the flame but this is a 'shake-my-head-in-disbelief' moment
that I find discouraging.
I pretty much agree, but from my POV [lang] stopped moving forward a
while ago anyway. Most new requests
I believe this is
