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=18940>. 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=18940 Proposal for making antcall with parameters less "bulky" Summary: Proposal for making antcall with parameters less "bulky" Product: Ant Version: 2.0 spec Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When making a build file more modular, I found that using the normal <antcall><param name="a" value="b"/> syntax is a bit bulky. My proposal is simple: Allow for inserting any attribute in a <antcall> element and make these attributes available as parameters inside the target ant task. Example: Current: <antcall target="ftp.get.lib"> <param name="src" value="${cvs.export}/junit/junit-3_8_1"/> <param name="file" value="junit.jar"/> </antcall> After: <antcall target="ftp.get.lib" src="${cvs.export}/junit/junit-3_8_1" file="junit.jar"/> </antcall> Of course common attribute analyse comes first, i.e. "target" is an attribute consumed by the <antcall> task itself - but name clashes of this kind should not be an issue. Although this is only a slight change - it would make my build files more readable and clear.
