diff --git a/docs/manual/CoreTasks/import.html b/docs/manual/CoreTasks/import.html index 32848e93e..d1af0ad7e 100644 --- a/docs/manual/CoreTasks/import.html +++ b/docs/manual/CoreTasks/import.html @@ -30,44 +30,43 @@ that are not possible with entity includes:
  • special properties

    • -Target overriding
    -
    -    If a target in the main file is also present in at least one of the -imported files, it takes precedence.
    -
    +Target overriding
    +
    +If a target in the main file is also present in at least one of the +imported files, it takes precedence.
    +
    So if I import for example a docsbuild.xml file named builddocs, -that contains a "docs" target, I can redefine it in my main -buildfile and that is the one that will be called. It makes it easy to -keep the same target name, that has the same dependencies (so it is -still called by the other targets), but use a different implementation.
    -
    -The original target is still available though, and is called "builddocs.docs". -This means that in my new implementation, I can still call the old -target, making it possible to enhance it with tasks called -before or after it.
    -
    -Special Properties
    -
    -    Imported files are treated as they are present in the main +that contains a "docs" target, I can redefine it in my main +buildfile and that is the one that will be called. This makes it easy to +keep the same target name, so that the overriding target is still called +by any other targets--in either the main or imported buildfile(s)--for which +it is a dependency, with a different implementation. The original target is +made available by the name "builddocs.docs". +This enables the new implementation to call the old target, thus +enhancing it with tasks called before or after it.
    +
    +Special Properties
    +
    +Imported files are treated as they are present in the main buildfile. This makes it easy to understand, but it makes it impossible for them to reference files and resources relative to their path. Because of this, for every imported file, Ant adds a property that contains the path to the imported buildfile. With this path, the imported buildfile can keep resources and be able to reference them -relative to its position.
    -
    +relative to its position.
    +
    So if I import for example a docsbuild.xml file named builddocs, I can get its path as ant.file.builddocs, similarly to the ant.file -property of the main buildfile.
    -Note that "builddocs" is not the filename, but the name attribute -present in the imported project tag.
    -
    +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.
    - 
    +imported files.
    + 

    Parameters

    @@ -77,36 +76,36 @@ imported files.
    - - -
    Required
    file
    +     		file
    		The file to import.
    +     		The file to import.
    		 Yes
    optional
    +     		optional
    		 if true, do not issue stop the build if the file does not exist, - default is false.
    + default is false.
    		 No
    -


    +


    Examples

    -
      <import file="../common-targets.xml" />
    -
    +
      <import file="../common-targets.xml" />
    +
    Imports targets from the common-targets.xml file that is in a parent -directory.
    -
    -
      <import file="${deploy-platform}.xml" />
    -
    -Imports the project defined by the property deploy-platform
    -
    -
    +directory.
    +
    +
      <import file="${deploy-platform}.xml" />
    +
    +Imports the project defined by the property deploy-platform
    +
    +

    Copyright © 2003-2004 Apache Software Foundation. All rights