build.sysclasspath worked this way in Ant 1.3, but is ignored by ANT 1.4 and 
up. If you want a full description see the ant mailing list for why. 
Basically, build.sysclasspath is used only for building the path used by the 
AntClassloader - But the AntClassloader uses the system classpath before using 
the custom built classpath - so this setting does not affect the order used 
when loading classes via the AntClassloader.

So setting this has ZERO affect on the issue at this point. Maybe in the 
future ANT will allow this setting to work the way it is expected to work. I 
have included an except from a recent discussion on a seperate mailing list 
regarding this issue when using Ant within an IDE. Maybe it'll help clarify 
this for y'all a little.

>> Andrew wrote:
>> I did lots more reseach into the problem, playing with the ANT source code.
>> The problem is caused by some missing funtionality of ANT. Setting the
>> sysclasspath to IGNORE does nothing to modify the load order - basically 
ANT
>> by default always loads from the system classpath first. Althought there is 
a
>> boolean value in the AntClassloader to change this functionality - there 
are
>> no documented tags allowing this to be set in the build.xml file.

>I guess that's true, classloading from Ant by default does use the system
>classpath. At least for ant.jar and optional.jar, this is necessary, else you
>could not load tasks at all. But IMHO other classpath items should not be 
made >available to tasks when build.sysclasspath=ignore. It is a bit thorny.
>
> - Jesse

>===== Original Message From "Martin van den Bemt" <[EMAIL PROTECTED]> 
=====
>See http://jakarta.apache.org/ant/manual/sysclasspath.html on how to do
>that...
>
>Mvgr,
>Martin
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]On Behalf Of Daniel Rall
>> Sent: Friday, March 01, 2002 21:47
>> To: Turbine Developers List
>> Subject: Re: FWD: [torque-3.0-dev] Ant Tasks and build.xml
>>
>>
>> Andrew <[EMAIL PROTECTED]> writes:
>>
>> > Build/Running with Torque and ANT 1.4.1 as of 3/01/2002. Ant
>> Tasks in 1.4.x by
>> > default loads from the system.classpath BEFORE the Task
>> classlist. This causes
>> > problems in environments where older versions of dependencies
>> already exist in
>> > the java environment. Especially when ANT is run from an IDE
>> (ex: netbeans).
>> >
>> > Temporary solution: modify build.xml to force Ant to use a reverse order
>> > classloader with tasks. This can be done by adding
>> 'reverseloader="true"' to
>> > the taskdef tags. I have verified this works with ANT 1.4.1
>> >
>> > I am not sure how you guys want to handle this - whether
>> mentioning in torque
>> > docs, changing it in src, or suppling two build.xml files with torque.
>>
>> IMO, Torque tasks shouldn't use the system classpath at all.  They
>> should only use the classpath configured by their calling build.xml.
>> Thoughts?
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <mailto:[EMAIL PROTECTED]>
>> For additional commands, e-mail:
><mailto:[EMAIL PROTECTED]>
>
>
>
>--
>To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Andrew Ballanger


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to