Make some target the extension of some defined -extension point. It will make the -list of targets dependencies of the extension point.
- -This target is useful when you want to have a target participate to another -build workflow, build workflow which explicitly expose an extension point for -that kind of insertion. But the target to bind and the extension point to -bind to are both declared in some imported build files. Modifying directly the -target dependency graph of these external build files may have a side effect -on some other project which import them. This task helps then to modify the -target dependencies but only in your context. -
- -Note: this task is quite equivalent to the definition of an intermediate -target which will be the bridge between the target to bind and the extension -point. For instance: -
--is quite equivalent to: -<bindtargets targets="jar,javadoc" extensionPoint="dist" />
-<target name="bind-to-dist" depends="jar,javadoc" extensionOf="dist" />
-This task basically avoid the creation of a target. -
- -The bindtargets task may only be used as a top-level task. This means that -it may not be used in a target. This is making the target dependency graph static -and predictable as soon as every build file is loaded.
- -Since Apache Ant 1.8.2
- -| Attribute | -Description | -Required | -
| targets | -a comma separated list of target names to bind. | -Yes | -
| extensionPoint | -the name of the extension point to bind the targets to. | -Yes | -
| onMissingExtensionPoint | -What to do if this target tries to extend a missing - extension-point. ("fail", - "warn", "ignore"). | -No. Defaults to fail |
-
- - - + + + + + + +-<bindtargets targets="build-jar,build-src-jar" extensionPoint="dist" /> -
Make some target the extension of some defined +extension point. It will make the +list of targets dependencies of the extension point.
+ +This target is useful when you want to have a target participate to another +build workflow, build workflow which explicitly expose an extension point for +that kind of insertion. But the target to bind and the extension point to +bind to are both declared in some imported build files. Modifying directly the +target dependency graph of these external build files may have a side effect +on some other project which import them. This task helps then to modify the +target dependencies but only in your context. +
+ +Note: this task is quite equivalent to the definition of an intermediate +target which will be the bridge between the target to bind and the extension +point. For instance: +
++is quite equivalent to: +<bindtargets targets="jar,javadoc" extensionPoint="dist" />
+<target name="bind-to-dist" depends="jar,javadoc" extensionOf="dist" />
+This task basically avoid the creation of a target. +
+ +The bindtargets task may only be used as a top-level task. This means that +it may not be used in a target. This is making the target dependency graph static +and predictable as soon as every build file is loaded.
+ +Since Apache Ant 1.8.2
+ +| Attribute | +Description | +Required | +
| targets | +a comma separated list of target names to bind. | +Yes | +
| extensionPoint | +the name of the extension point to bind the targets to. | +Yes | +
| onMissingExtensionPoint | +What to do if this target tries to extend a missing + extension-point. ("fail", + "warn", "ignore"). | +No. Defaults to fail |
+
+ + ++<bindtargets targets="build-jar,build-src-jar" extensionPoint="dist" /> +