ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 598] New - Execute does not properly change drive for Windows
Date Wed, 14 Feb 2001 00:50:59 GMT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=598

*** shadow/598	Tue Feb 13 16:50:58 2001
--- shadow/598.tmp.13149	Tue Feb 13 16:50:59 2001
***************
*** 0 ****
--- 1,28 ----
+ +============================================================================+
+ | Execute does not properly change drive for Windows                         |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 598                         Product: Ant                     |
+ |       Status: NEW                         Version: 1.3 Beta 1              |
+ |   Resolution:                            Platform: PC                      |
+ |     Severity: Normal                   OS/Version: Windows NT/2K           |
+ |     Priority:                           Component: Core                    |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: ant-dev@jakarta.apache.org                                   |
+ |  Reported By: d.rees.l@usa.net                                             |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ Execute (and hence the java task and perhaps
+ others) does not properly change the active drive when the execute directory's 
+ drive is different than the
+ current directory's drive.
+ 
+ As an example, if your current directory is c:\build and your run directory is 
+ d:\run, previously only a "cd d:\run" was performed and the active drive was 
+ not changed (because of the Windows directory per drive "feature"). Therefore 
+ the execute actually still runs in c:\build. The patches cause the needed 
+ active drive change as well.
+ 
+ A patch has been submitted to ant-dev.

Mime
View raw message