Answering my own question, it appears that any datatype can be given an
"id" attribute. However, each task that allows a reference id
determines what datatypes can be referenced. As for "property", it
assumes that the referenced object has a meaningful toString() method
and uses its value to set the property.
For the pathconvert task that I posted, I can enhance it to deal with
referenced filesets in addition to paths.
Is this something people would want?
"Larry V. Streepy, Jr." wrote:
>
> After a quick scan of the build.xml parsing code, it appears that all
> datatypes implicitly support an "id" attribute. Is this correct?
>
> --
> Larry V. Streepy, Jr.
> Chief Technical Officer and VP of Engineering
>
> Health Language, Inc. -- "We speak the language of healthcare"
>
> 970/626-5028 (office) mailto:[EMAIL PROTECTED]
> 970/626-4425 (fax) http://www.healthlanguage.com
--
Larry V. Streepy, Jr.
Chief Technical Officer and VP of Engineering
Health Language, Inc. -- "We speak the language of healthcare"
970/626-5028 (office) mailto:[EMAIL PROTECTED]
970/626-4425 (fax) http://www.healthlanguage.com
