One might be able to do this using an "antLoaderRef", and overriding or adding a typedef declaration for the task in question, like junit. We had a simliar issue where we needed use a task that used xmlbeans, but we didn't want people to have to add the jar to there Ant lib directory. Is this what the runant macro solves? /Daniel Tom Fennelly wrote: Yes, the runant macros are there to make sure that the build has the correct classpath (notably including junit) so that you can just run ant and 'it will work (tm)'. It is only supposed to be used in the public targets so dependencies should not be using those. Kev -- JBoss, a Division of Red Hat Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (USA), Charlie Peters (USA) and David Owens (Ireland) _______________________________________________ esb-dev mailing list esb-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/esb-dev -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.