Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 12640 invoked from network); 18 Feb 2004 22:23:52 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 18 Feb 2004 22:23:52 -0000 Received: (qmail 85635 invoked by uid 500); 18 Feb 2004 22:23:28 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 85602 invoked by uid 500); 18 Feb 2004 22:23:28 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 94215 invoked from network); 18 Feb 2004 20:25:26 -0000 Message-Id: <200402182025.i1IKPFbp031282@yoda.savarese.org> X-Mailer: exmh version 2.5 10/15/1999 with nmh-1.0.4 To: Jakarta Commons Developers List cc: "'Ant Developers List'" Subject: Re: Incorrect documentation of FTP task [net] In-reply-to: Your message of "Wed, 18 Feb 2004 09:14:04 CST." <830BF4914C3C4B4EB1C438D93ABF897A04D8B5@lgchexch011.ad.lgc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Feb 2004 15:25:15 -0500 From: "Daniel F. Savarese" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N In message <830BF4914C3C4B4EB1C438D93ABF897A04D8B5@lgchexch011.ad.lgc.com>, Dom inique Devienne writes: >Probably not... I simply try to avoid having twice the same functionality on >my classpath, and JDK1.4+ fulfills my regexp needs (albeit simple) just >fine. I've read a few times that ORO is superior to the JDK's regexp impl, >so it's not a question of merit, but simply to avoid duplication (I used >java.util.regex with the REX/Shallow Parser expressions, and it worked fine, >so that's good enough for me.) What I'm getting at is tht oro is not a regex engine. It is a collection of regex engines and additional text processing features. It provides generic interfaces for pattern matching. Why reinvent generic interfaces, when they are already there? So I implemented the glue last night to make that evident. I could just go all the way and add the java.util.regex wrapper and J2SE 1.4 autodetection, in which case I would hope the point would become moot since you'd have the desired functionality. Although, I'd prefer for other to get involved to at kibitz about the glue (implementing the java.util.regex wrapper is just a matter of setting aside a little time). If oro were a part of commons would this even be an issue? I think a desire for Commons Net to use a regex engine abstraction other than oro may be more of a perceptual issue than an engineering issue. I'm not suggesting Ant change it's wrapper since it's already there. It's just that Steve indicated it wasn't quite general enough for Commons Net and I already know that the code changes to Commons Net will be minimal with oro because it already uses PatternMatcher and PatternCompiler. >I understand Jakarta libraries must run on many JDKs, so cannot require JDK >1.4+, but OTOH, it's annoying to have useful OS projects you're interested >in pick up so many other dependencies, often for just a few convenient >classes, thus using 1% of that dependency, which often has a large overlap >with other libraries from the JDK or other libraries one's forced to use >(thru indirect dependencies). Too true. daniel --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org