I would externalize (huge amounts of) macrodefs in their own files. a) into a buildfile and re<import> that b) into an antlib.xml and use xmlns declarations.
my.jar!/org/my/antlib.xml <antlib> <presetdef name="hello"><echo message="hello"/></presetdef> </antlib> build.xml (having my.jar on the classpath) <project xmlns:my="org.my"> <my:hello/> </project> Additional note: Lets say you have a larger hierarchy "A imports B; B imports C". Then A contains all macros and targets from B _and_ from C. When working with xmlns "A imports B; B uses xmlns-C" A only contains B. Xml namespaces are not imported. Jan > -----Ursprüngliche Nachricht----- > Von: Scot P. Floess [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 14. Dezember 2007 03:49 > An: Ant Users List > Betreff: Re: Divide And Conquer Ant Question > > I do the same thing... However, I am partial to macrodef's... I do > have a build script that may use those macrodef's... However, my > macrodef's are sorta like functions from which I can then > script/glue/call from my "scripts" > > > > Z W wrote: > > Hi > > > > I'm using Ant as a scripting tool much like a shell script > to do various > > tasks of a project, not for a build purpose. > > I like to get opinions from the gurus here about this. > > > > I have various tasks written in a single build file. > However, this file has > > become very large. > > I like to break this file up into multiple files, putting > different targets > > into various build files, > > much like breaking a single large C file into multiple files. > > > > What's the best approach to this while minimizing script > > rewriting/maintainability ? (using antcall, import or > something else) > > > > Thanks > > > > > > -- > Scot P. Floess > 27 Lake Royale > Louisburg, NC 27549 > > 252-478-8087 (Home) > 919-754-4592 (Work) > > Chief Architect JPlate http://sourceforge.net/projects/jplate > Chief Architect JavaPIM http://sourceforge.net/projects/javapim > QA Engineer OpenQabal http://openqabal.dev.java.net > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
