Return-Path: <anonymous@nagoya.betaversion.org>
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 63235 invoked from network); 4 Mar 2003 01:29:58 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 4 Mar 2003 01:29:58 -0000
Received: (qmail 28427 invoked by uid 50); 4 Mar 2003 01:31:43 -0000
Date: 4 Mar 2003 01:31:43 -0000
Message-ID: <20030304013143.28426.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@ant.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 17625] New:  -
    COPY task on Win NT across Network drive fails
X-Spam-Rating: daedalus.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
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17625>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17625

COPY task on Win NT across Network drive fails

           Summary: COPY task on Win NT across Network drive fails
           Product: Ant
           Version: 1.5.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: rxh@gers.com


When you use an empty <copy> task with todir and file attrbutes and the todir
folder is on a Mapped drive on another windows system, but the copy is initiated
from an NT system, the copy fails with no errors or warnings.

For example:
<copy file="c:/temp/local.jar" todir="M:/test"/>
Where M is a mapped drive to another Windows system.

The above task will report no errors or warnings, but will also not run.
If you modify this slightly:
<copy todir="M:/test">
  <fileset dir="c:/temp">
    <include name="local.jar"/>
  </filest>
</copy>

The modified version works.

I can work with the modified version, it just gets to be a pain because the
error only happens when you initiate the copy from a Windows NT system and we
have many because we need to validate that the software works on NT for our
customers.  The same copy that failed above on NT will work on Windows 2000 and
XP (haven't tested on other platforms)

Thanks,
Rey