ant script annoyances

[Herve Quiroz]

Ernst,

Although I was quite fond of the current behaviour when you implemented
it, I just faced the problem last night and I found it very annoying.

But you're right, many people (just as me) are used to this feature now.
So there should be a quick and simple way to have ant continue to
include all installed JARs in the classpath.

What about a simple ANT_CLASSPATH_ALL variable ?

If defined, the ant shell script adds the JARs from JAVASHAREDIR in the
classpath (as it does in the current implementation). If not, the script
acts as the original ant script (the one from Apache's former release).

Then adding ANT_CLASSPATH support would be easy (and transparent to the
final user).

Herve


On Thu, 11 Sep 2003, Ernst de Haan wrote:

> Jonathan, Herve,
>
> Okay, if this behaviour is really causing Ant to behave incompatible on
> FreeBSD, which it is, then we should rollback. We all agree on this.
>
> On the other hand, it must be _very_ easy to keep the current behaviour, if
> a person would like this. (S)he should only have to make a one-time change
> to get this behaviour for a single account or for all accounts on the
> machine. Do you agree?
>
> The easiest way to implement this, is to have a single environment variable
> that enables this behaviour if set. A person can then set this in
> /etc/profile or in ~/.profile. I know this is notas nifty as an ant-config
> command, but it's simple and effective. What do you think of this
> alternative?
>
> Ernst