ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: adding custom tasks without repackaging ant.jar
Date Wed, 09 Jun 2004 05:05:12 GMT
> > thanks for the response.
> > I'm using ant 1.5 which does not support antlib.
> > But even with antlib, I still need to define <typedef file="antlib
> > file"> in the build script.
> Not if you're using XML namespaces and the special antlib: URIs.

<project xmlns:ac="net.sf.antcontrib">

> > Is there a way such that I can go about without defining 
> anything new in
> > the build script and the custom tasks can be used with out modifying
> > ant.jar?
> No, and this is by design. It is better to have everything in 
> the open and rather than implicitly loading custom tasks. This is 
> almost what the antlib: magic URI does, except the XML namespace still
makes it
> explicit.
> What's wrong with a <typedef>/<taskdef> at the top level of a 
> build script?

And you´ll know that the buildscripts depends on your custom tasks. 


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message