> From: Peter Reilly [mailto:[EMAIL PROTECTED]
>
> Jose Alberto Fernandez wrote:
>
> >
> >As the URI protocol "antlib:" provides a shortcut for the <typedef/>
> >above, I am just thinking on providing something similar for the
> >classpath declaration when needed.
> >
> ><classpath id="foo.bar">.....</classpath>
> >
> >
> >
> I have been doing a little thinking about this.
> What about a task to specify the classpath to use if the "antlib:"
> shortcut is triggered
> for a particular uri:
>
> something like:
>
> <antlibclasspath uri="antlib:foo.bar" [path attributes]
> [loaderref attribute]>
> [path elements]
> </antlibclasspath>
>
> This would be a relatively low-cost task - it does not
> trigger reading the antlib.xml resource until the "antlib:"
> shortcut is triggered - so it could be placed in a common xml
> file imported by a site's build.xml files.
>
I think we are in the same wavelength here. I was trying to use
just <classpath/> or the new <classloader/> tasks directly
rather than having special versions of them.
I see the documentation value of what you propose, though
(specially with the URI attribute).
In any case, if we have an specific task for this, I would suggest
calling renaming it <antlibloader/> with syntax similar to yours:
<antlibloader uri="antlib:foo.bar"
[{classpathref="..."| loaderref="..."}] [id="..."] >
[<classpath>....</classpath>]
[<classloader>...</classloader>]
</antlibloader>
Jose Alberto
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
