ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Garrison <Jim.Garri...@troux.com>
Subject Clarification on definition of "reference"
Date Tue, 02 Jun 2009 19:10:59 GMT
The ANT docs use the term "reference" in a way that, at least to me, is a little confusing.
 The term "reference" seems to mean both the act of referring to an object defined elsewhere
(as in "refid=...") and also the object being referred to.  Are the following correct?

 1.  A "Property" is a name-value pair defined with the <property> tag, and its identifier
is the value of the "name=..." attribute
 2.  A "Reference" is defined by any object definition using its "id=..." attribute (is this
aka a "Type"?)
 3.  By default (without inheritRefs and nested reference tags), <ant> and <antcall>
establish a new scope for reference objects. That is:
    *   At the point in the calling buildfile where the sub-ant is invoked, there exists a
set of visible reference objects
    *   In the called buildfile, that set of reference objects is NOT visible
 4.  Reference objects can be made visible inside the sub-build using inheritRefs="true",
or by providing explicit nested <reference> tags inside the <ant> or <antcall>
that invoked the sub-build.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message