John,
This, I presume, feeds into the Ant "build.sysclasspath" property. The
values control how the system classpath, ie. the classpath in effect when
Ant is run, affects the behaviour of classpaths in Ant. This comes into
play in a few situations such as, for example, executing an external Java
class with the <java> task. The values and their meanings are
only
Only the system classpath is used and classpaths specified in build files,
etc are ignored. This situation could be considered as the person running
the build file knows more about the environment than the person writing the
build file
ignore
The system classpath is ignored. This situation is the reverse of the
above. The person running the build trusts the build file writer to get the
build file right
last
The classpath is concatenated to any specified classpaths at the end. This
is a compromise, where the build file writer has priority.
first
Any specified classpaths are concatenated to the system classpath. This is
the other form of compromise where the build runner has priority.
Unfortunately this is not currently documented in the Ant user manual.
Conor
----- Original Message -----
From: "John Morrison" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, March 03, 2001 10:13 PM
Subject: [GUMP] sysclasspath
> Hi all,
>
> Could somebody please tell me what the line...
>
> <build sysclasspath="only"/>
>
> in the controlling xml does, and what options other than 'only' I can
use?
>
> Thanks,
>
> John.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
