DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12896>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12896 Clean Build All Support Without Declarative Programming Summary: Clean Build All Support Without Declarative Programming Product: Ant Version: 1.5 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Ant does not use declarative programming constructs (e.g. if, for, etc) but deals with this by using dependencies, and by allowing most tasks to work over configurable filesets. However, the common requirement for a build all facility for large numbers of modules is not yet managed cleanly, requiring each module to be defined, creating a large administrative overhead. This problem is exacerbated, when optional modules are used, where the list needs to be defined twice (once for <availability> and once for <ant>). A solution to this, that is in keeping with the Ant methodology, is to allow external dependencies to be created. For example: <target externalDependency="module1/build.xml"> to create a dependency on the complete script, or <target externalDependency="module1/build.xml[subset]> to create a dependency on a subset of the script. The problem of optional modules, requires the use of wildcarding. For example: <target externalDependency="**/build.xml[optionalModule]"> to create a dependency on all optional modules that are currently present. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
