http://nagoya.apache.org/bugzilla/show_bug.cgi?id=861
*** shadow/861 Tue Mar 6 09:35:07 2001 --- shadow/861.tmp.21652 Tue Mar 6 09:35:08 2001 *************** *** 0 **** --- 1,28 ---- + +============================================================================+ + | Ant task can't integrate the resulting environment of spawned tasks. | + +----------------------------------------------------------------------------+ + | Bug #: 861 Product: Ant | + | Status: NEW Version: 1.3 | + | Resolution: Platform: All | + | Severity: Enhancement OS/Version: Other | + | Priority: High Component: Core tasks | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + Ideally, a build process or processes could be initialized through the use of + the Ant task by calling a target on an environment.xml-type file. This way, all + of a set of build.xml's would get the same initial build environment, without + having to duplicate the checks and init's in all build files. + + I propose to put an additional attribute in the Ant taskdef to allow the + preservation of this child environment, and integration back into the parent. + The added attribute could be optional and default to "false", to avoid breaking + existing code. + + This change would further modularize an already modularized project, and could + help take it from a procedural analogy to an OO analogy of a build process.
