Java Mailing List Archive

http://www.ant-tasks.com/

Apache Ant Archive

» Ant Users List
» Ant Developers List
Task help

Task help

2006-10-19       - By peter reilly
Reply:     1     2     3     4     5     6     7     8     9  

On 10/19/06, Jan.Materne@(protected) <Jan.Materne@(protected)> wrote:
> >I am thinking of adding:
> >
> >  <project xmlns:ac="antlib:net.sf.antcontrib">
> >     <typedef antlib="antlib:net.sf.antcontrib"
> >                   classpath="${PATH_TO_ANTCONTRIB.JAR}"/>
> >
> >which would be equilivent to
> >  <typedef uri="antlib:net.sf.antcontrib"
> >                resource="net/sf/antcontrib/antlib.xml"
> >                classpath="${PATH_TO_ANTCONTRIB.JAR}"/>
>
>
> Would it be easier to have
>
> <typedef
>     antlib="net.sf.antcontrib"      no need for antlib: protocoll as its
> the only
>     xmlns="ac"                      no need for name-equality between
> <project xmlns> and <typedef>
>     resource+uri                    together with xmlns: if you dont use
> antlib+xmlns attribute
>     classpath                       as before (also support of nested
> <resources>?)
> />

I would rather use the same value as the xmlns binding attribute,
i.e. the XML namespace that the antlib is placed in.

The idea of antlibs is to use standard XML namespaces to handle namespace
issues of having multiple antlibs.

Peter

>
>
> Jan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@(protected)
> For additional commands, e-mail: user-help@(protected)
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@(protected)
For additional commands, e-mail: user-help@(protected)


©2008 ant-tasks.com - Jax Systems, LLC, U.S.A.