DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=22269>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=22269 ------- Additional Comments From [EMAIL PROTECTED] 2005-11-06 00:02 ------- Since the <subant> task has similar functionality, perhaps that existing implementation would make enhancing <import> like this easier? I also mention <subant> because some folks finding this bug/rfe might find that it can do what they want (without this feature). In my case, the target overriding special features of <import> are expecially important to my efforts. Stephan Bodewig's excellent OTN article on Ant 1.6... http://www.oracle.com/technology/pub/articles/bodewig_ant1.6.html ...illustrates one approach to using <import>, <subant> and <macrodef> for "auto-discovery of build files". But near the end he states that adding "ordering [of] the builds according to their interdependencies" requires a custom Ant task like <buildlist>. I've had good success with a slightly different approach, which first imports all the (package-level) build files in a project. Hierarchical target invocations can then be more naturally specified in the depends="..." attributes of targets. For example: <target name="compile" depends="strutil.compile,util.compile"> In this case, I need to use something like this: <import> <fileset dir="." includes="*/build.xml"/> </import> Currently I have to list each build file with a separate <import> task, which is tedious and brittle. I believe this feature would give Ant a powerful and natural way to represent build dependencies throughout a tree of build files. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
