[EMAIL PROTECTED] wrote:
Why do you put libs in ANT_HOME/lib ?
All classes there are added to Ants classpath by Ants launcher class.
And only tasks and external libraries for tasks make little sence
here.
Because the ant library folder is the obvious place to
put custom ant tasks.
Ok, thats
>> Why do you put libs in ANT_HOME/lib ?
>> All classes there are added to Ants classpath by Ants launcher class.
>> And only tasks and external libraries for tasks make little sence
here.
>
>Because the ant library folder is the obvious place to
>put custom ant tasks.
Ok, thats new - you are s
On 15 maj 2006, at 19.42, Dominique Devienne wrote:
[...] javac might find a previous version of any implementation
classes used
Look up the 'includeAntRuntime' and 'includeJavaRuntime' attributes
of .
I always used false for these myself. --DD
This will work in most cases, but for t
[...] javac might find a previous version of any implementation classes used
Look up the 'includeAntRuntime' and 'includeJavaRuntime' attributes of .
I always used false for these myself. --DD
-
To unsubscribe, e-mail: [EMAIL
On 15 maj 2006, at 15.59, <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> wrote:
Inside the buildfile you could use s, e.g.
I have tested this. It does not work. I tested by
creating a dummy class, and installing it's jar in the
standard ant library directory. Even when I explicitly tell
>> Inside the buildfile you could use s, e.g.
>>
>>
>> > classpathref="classpath"/>
>I have tested this. It does not work. I tested by
>creating a dummy class, and installing it's jar in the
>standard ant library directory. Even when I explicitly tell
>ant to ignore this jar in the
