ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From peter reilly <peter.rei...@corvil.com>
Subject Re: [Patch] namespace and antlib
Date Tue, 12 Aug 2003 12:15:24 GMT
On Tuesday 12 August 2003 12:36, Stefan Bodewig wrote:
> On Fri, 1 Aug 2003, peter reilly <peter.reilly@corvil.com> wrote:
> >   <typedef resource="net/sf/antcontrib/antlib.xml"
> >            uri="antlib:net.sf.antcontrib"
> >            classpath="/tmp/ant-contrib.jar"/>
>
> wouldn't the resource attribute be redundant in that case?

Not in this case. The automatic lookup of uri="antlib:net.sf.antcontrib" to
net/sf/antcontrib/antlib.xml resource currently is done once when the
ns prefix is encountered the first time - it does not take place at
the <typedef/> task.

>
> > 3) reserved uri's
>
> +1 on reserving the ant* protocol.

I have changed this to ant:*, as I found when testing
that the current code reserves antcontrib: and antelope: ....

>
> > 5) antlibs in the classpath
>
> I'm leaning towards a repository of antlibs, say ANT_HOME/antlibs with
> classloader isolation between different antlibs and discovery on
> demand here.  I.e. don't force the antlib to live on Ant's core
> classloader - and avoid scanning of the repository unless an antlib:*
> URI has been used.

This makes sense, but would involve some messing with classloaders and
scanning of the jar files in ANT_HOME/antlibs. Each time I look at
classloaders, my head melts down....

>
> > 6) adding new definitions to a uri
>
> What about overriding a definition?  Print a warning and succeed like
> <taskdef> would do now?
Yes, there is no difference.
>
> +1 on the proposal in general.

Excellent.
Peter


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message