Below are all the online learning materials available for AntX’s Value URI functionality. Note that this information will always be complemented by the AntX javadocs; if you cannot find the information in the pages listed below, please try the associated value uri’s javadoc pages (which will be listed in the “Related Topics” on each page and may be more up-to-date for new features if we’re in the beta phase of a new version). If you find a mistake or a typo, please please let us know so we can correct it.
Common Functionality
- Because all value uris are embedded as part of standard property references, if they fail the enclosing property dereference acts as if the property does not exist. In other words, the result of the property is the uri string itself (just like actual missing properties). You can force some uri handlers to signal a build error if they are unable to process a fragment; see each handler’s javadocs for more information.
- You can load all of the AntX value uris by loading a single antlib file as described in the How-To section of this site. Alternatively, you can load only the uri handlers you want. You can also install and uninstall a value uri handler at any time– you do not have to manage them collectively.
- You can pipeline the results of value uris into each other using a single “|” delimiter between uri scheme markers like: $var:filelist|$stripws:|$uppercase:. The result of the preceding uri is prepended to the fragment portion of the next uri before that handler is invoked. If any handler returns null the entire evaluation is aborted (as if a property reference is missing).
- When you supply multiple arguments in a uri, you must separate them using two commas like “,,”. See each uri’s guide page for details.
Builtin Value URIs Index
