Agreed! I thought the whole point of the various commons libraries was to provide a low-level set of libraries upon which other apps can be built upon. Why then is it such a problem for the different commons project themselves to be interdependent? I can understand not wanting to have interdependencies between different areas of functionality (e.g. [cli], [validator], [betwixt]), but surely we should encourage some of the more specific commons projects to rely on the more general projects (e.g. [lang], [io], [collections]) where appropriate?
-----Original Message----- From: Steven Caswell [mailto:[EMAIL PROTECTED] Sent: 09 September 2004 12:07 To: Jakarta Commons Developers List Subject: Re: [io] find API Was: [IO] DOSFileFilter WildcardUtils look general enough that it could go into commons-lang, but then of course you introduce a dependency, which seems to give some people a lot more heartburn than it gives me. I hate to see classes put into the wrong library just to avoid even dependencies that make sense. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System - after being sent from Granta Design Ltd ______________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
