Ok, now that we've factored out the plug-ins, what is there in build.init.target that *has* to be inline in the plug-in build files, rather than accessed using antcall?
At the moment, I can't see anything other than the setting up of the class path and default properties that *must* be inline in the build file. And we could move the properties stuff to a plug-in build file. Also, I remember in Ant 1.4.1 a way of passing paths around (antcall) using refid. My goal here is to streamline the plug-in process so that we can modularise it even further, and remove the need for bootstrapping. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
