Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4BF5110C43 for ; Wed, 31 Jul 2013 18:59:59 +0000 (UTC) Received: (qmail 19772 invoked by uid 500); 31 Jul 2013 18:59:57 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 17554 invoked by uid 500); 31 Jul 2013 18:59:51 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 16524 invoked by uid 99); 31 Jul 2013 18:59:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Jul 2013 18:59:48 +0000 Date: Wed, 31 Jul 2013 18:59:48 +0000 (UTC) From: "Shon Vella (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (VFS-481) Default moveTo does not work for non-empty directories when it can't be done via renaming. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Shon Vella created VFS-481: ------------------------------ Summary: Default moveTo does not work for non-empty directories when it can't be done via renaming. Key: VFS-481 URL: https://issues.apache.org/jira/browse/VFS-481 Project: Commons VFS Issue Type: Bug Affects Versions: 2.0 Reporter: Shon Vella The default implementation of moveTo in AbstractFileObject has no chance of working for a non-empty folder in cases where it can't be done via a rename. This is because it calls it calls copyFrom with Selectors.SELECT_SELF which will not copy the descendants and doDelete, which is documented as only supposed to be called when "This file has no children, if a folder." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira