On Mon, 17 Jul 2006, Kev Jackson <[EMAIL PROTECTED]> wrote: > I submitted a presentation proposal for ApacheCon Asia a couple of > weeks ago and I've just been accepted (which is nice...).
Great. > I was going to cover the following in the presentation (based on an > article that is in the pipeline at ONJava): > > - Why Antlibs: > - easier for classpath lookups compared to taskdefs > - standard way to distribute new optional components (1.7+) > - decouples optional tasks from ant core This means you'll focus on the Antlibs provided by the Ant project. More than on writing your own Antlibs. Correct? If not, you might want to add things like easy deployment and ease of use by the end-user (just declare a XML namespace in the build file). > - Testing antlibs with AntUnit (new antlib available from > http://x.y.z) Let's say "soon available". > - Refactoring an optional taskdef into an antlib (use VSS task as > example) > > Any ideas on other stuff that really should be mentioned? I like the trick Ant-Contrib uses. It used to provide a properties file for <taskdef resource=.../> and still does. In order to keep this file and the antlib descriptor in sync, the antlib.xml file uses the property file. In addition the Antlib descriptor lists a few tasks that require Ant 1.6+ so Ant 1.5 users can use <taskdef> and Ant 1.6+ users use it as an antlib. It also shows how easy it is to turn your existing library of Ant tasks into an Antlib - just add an antlib.xml. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
