On Tue, 23 Aug 2005, Steve Loughran <[EMAIL PROTECTED]> wrote:
> One change I have also checked in to Definer.java is some extra
> logic for naming antlibs. Instead of just
>
> antlib:org.example.package
>
> you can go
>
> antlib://org/example/package/file.xml
I don't like that ant
I was thinking of having another attribute (like
antlib="antlib:org.smartfrog.tools.ant")
to set the uri and resource.
It may be a good idea however to do this by default with just the uri
attribute - if the user has not
specified the resource/filename.
Peter
Steve Loughran wrote:
Why do
Dominique Devienne wrote:
From: Steve Loughran [mailto:[EMAIL PROTECTED]
One change I have also checked in to Definer.java is some extra logic
for naming antlibs. Instead of just
antlib:org.example.package
you can go
antlib://org/example/package/file.xml
and have that file's d
> From: Steve Loughran [mailto:[EMAIL PROTECTED]
> One change I have also checked in to Definer.java is some extra logic
> for naming antlibs. Instead of just
>
> antlib:org.example.package
>
> you can go
>
> antlib://org/example/package/file.xml
>
> and have that file's declaration
Stefan Bodewig wrote:
On Mon, 22 Aug 2005, Steve Loughran <[EMAIL PROTECTED]> wrote:
Why do you have to repeat the full path to an antlib in ,
when declaring into an antlib url.
antlib descriptor, you mean?
If so, I agree with you, we should magically provide a default for the
resource att
On Mon, 22 Aug 2005, Steve Loughran <[EMAIL PROTECTED]> wrote:
> Why do you have to repeat the full path to an antlib in ,
> when declaring into an antlib url.
antlib descriptor, you mean?
If so, I agree with you, we should magically provide a default for the
resource attribute if uri has been s
