the import task (shipped with 1.7 and - as far as i can tell - in trunk)
accepts 'file' and 'optional' parameters. i quite often use this is set
up template builds with common targets for modules which can then
override when necessary. i use a lot of macro's and factoring these into
antlibs helps
i'm using ant 1.7.0 and antunit to integration test a antlib task. the
tests are factored into separate build scripts. these run fine
individually but i'd like to include them in a comprehensive
build-and-test target in a master build file.
ATM i'm using exec to call ant so that i can pass a -lib
