Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 28342 invoked from network); 11 Aug 2005 15:09:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 11 Aug 2005 15:09:22 -0000 Received: (qmail 72865 invoked by uid 500); 11 Aug 2005 15:09:19 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 72837 invoked by uid 500); 11 Aug 2005 15:09:18 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 72822 invoked by uid 99); 11 Aug 2005 15:09:18 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Aug 2005 08:09:18 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id 3A411EB; Thu, 11 Aug 2005 17:09:17 +0200 (CEST) From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Subject: DO NOT REPLY [Bug 34942] - [VFS] no vfs_cache cleanup after ant task completed X-Bugzilla-Reason: AssignedTo Message-Id: <20050811150917.3A411EB@ajax.apache.org> Date: Thu, 11 Aug 2005 17:09:17 +0200 (CEST) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34942 ------- Additional Comments From hoju@visi.com 2005-08-11 17:09 ------- Cool, the main thing is making sure the docs don't get out of sync with project.xml, otherwise confusion ensues. >> Also, you build against commons-net-1.4.0 according to project.xml. > Same story. Its often better to use more recent versions but we should > take care not to break backward compatibility too fast. > Now that commons-net has a new parsing engine there are arguments to > break it, so we can go that way. Yes please file a new bugzilla ticket with your > patch - as enhancement - we can apply it after release 1.0 Will do, sometime tonight >> Now, one more thing. I'd like to add Ant-1.6+ antlib functionality. > Sure, we can to it. > Isnt the main advantage of it to have a namespace? So we could name your vfs > tasks simply copy, move, ... > In ant one can use > xmlns:vfs="antlib:org.apache.commons.vfs.tasks" and then > Or am I wrong? No, that's pretty much right on, although you can use namespaces without using antlib. Another advantage is that you don't even need to the VFS tasks if they are in the classpath already since antlib does it for you. So, you can just do... Notice the lack of an explicit taskdef! Keeps things clean and nearly as easy to use as the core ant tasks. Jake -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org