From 1f6f45aebb95ddf56779db1609bf7bfcd4eddcb3 Mon Sep 17 00:00:00 2001 From: Peter Reilly Date: Thu, 29 Apr 2004 10:13:17 +0000 Subject: [PATCH] Describe relative file behaviour in task. git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@276426 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/CoreTasks/import.html | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/docs/manual/CoreTasks/import.html b/docs/manual/CoreTasks/import.html index 6345f13b2..bc1627543 100644 --- a/docs/manual/CoreTasks/import.html +++ b/docs/manual/CoreTasks/import.html @@ -62,12 +62,6 @@ property of the main buildfile.
Note that "builddocs" is not the filename, but the name attribute present in the imported project tag.

-Important: We have not finalized how relative file references -will be resolved in deep/complex build hierarchies -such as what -happens when an imported file imports another file. Use absolute -references for enhanced build file stability, especially in the -imported files.

Parameters

@@ -81,7 +75,9 @@ imported files.
file @@ -90,7 +86,7 @@ imported files.
optional
- The file to import. + The file to import. If this is a relative file name, the file name will be resolved + relative to the importing file. Note, this is unlike most other + ant file attributes, where relative files are resolved relative to ${basedir}. Yes
- if true, do not issue stop the build if the file does not exist, + If true, do not stop the build if the file does not exist, default is false. No