http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1709
*** shadow/1709 Fri May 11 02:24:48 2001
--- shadow/1709.tmp.26356 Fri May 11 07:40:53 2001
***************
*** 4,10 ****
| Bug #: 1709 Product: Ant |
| Status: NEW Version: 1.3 |
| Resolution: Platform: PC |
! | Severity: Enhancement OS/Version: |
| Priority: Low Component: Core |
+----------------------------------------------------------------------------+
| Assigned To: [EMAIL PROTECTED] |
--- 4,10 ----
| Bug #: 1709 Product: Ant |
| Status: NEW Version: 1.3 |
| Resolution: Platform: PC |
! | Severity: Enhancement OS/Version: All |
| Priority: Low Component: Core |
+----------------------------------------------------------------------------+
| Assigned To: [EMAIL PROTECTED] |
***************
*** 21,24 ****
allows you to do this, but without the search back up the directory
structure.
More tools being created such as AntRunner mean that the current directory
when
the ant script is run cannot be guaranteed to be a specific directory. The
onus
! is now on the ant.bat script writer to push and pop the current directory.
--- 21,46 ----
allows you to do this, but without the search back up the directory
structure.
More tools being created such as AntRunner mean that the current directory
when
the ant script is run cannot be guaranteed to be a specific directory. The
onus
! is now on the ant.bat script writer to push and pop the current directory.
!
! ------- Additional Comments From [EMAIL PROTECTED] 2001-05-11 07:40 -------
! It's a little unclear what you're reporting or asking for.
!
! If you gave -find an absolute pathname, what good would searching upwards be?
! (An absolute pathname is independent of the current directory, so iteratively
! resolving it relative to a list of ancestor directories would always resolve
! to the same file, so searching wouldn't add anything, right?)
!
! Do you mean a relative pathname that's not just a simple file name (e.g.,
! "scripts/build.xml")? That already works, right?
!
! Could you clarify the problem with setting the current directory?
!
! Ant seems to set the current directory to the directory of the build
! file whether you use -find with a simple name (e.g., "build.xml"),
! -find with a non-simple relative name (e.g., "scripts/build.xml"), or
! -buildfile with an absolute name ("C:\...\build.xml"). (Tested with
! " <exec command="pwd"/> ".)
!
! Did you want different behavior? (Or did I not test carefully enough
! and misperceive and misstate what Ant does?)
