Mariano Benitez wrote:
do you imply here that when you use with an already defined
uri, being that an antlib uri, that it will add those definitions to
the antlib uri?
Yes, this is the way it works.
For example:
is the same as:
and:
Peter
in your sample you are adding
do you imply here that when you use with an already defined
uri, being that an antlib uri, that it will add those definitions to the
antlib uri?
in your sample you are adding definitions to the antlib you are defining
there, is that correct?
MAriano
Peter Reilly wrote:
Hi Mariano,
You are rig
Hi Mariano,
You are right that one can specify the classpath within an antlib,
and it is incorrectly silently ignored.
There would be a problem with using properties as one would need
to be very carefull to specify them before the antlib auto reading
is triggered.
With the current ant implementatio
[mailto:[EMAIL PROTECTED]
Sent: 05 March 2004 18:22
To: Ant Developers List
Subject: Re: taskdefs inside an antlib and their classpath
would it be very crazy to add a classpath atlibdefinition
that would add
jars to the antlib classpath instead of getting ALL the jars from a
directory.
My
> -Original Message-
> From: Mariano Benitez [mailto:[EMAIL PROTECTED]
> Sent: 05 March 2004 18:22
> To: Ant Developers List
> Subject: Re: taskdefs inside an antlib and their classpath
>
>
> would it be very crazy to add a classpath atlibdefinition
> that woul
would it be very crazy to add a classpath atlibdefinition that would add
jars to the antlib classpath instead of getting ALL the jars from a
directory.
My problem is that I would like to keep only the task definitions in the
antlib directory and the other dependent jars in a common lib director
