On Wed, 11 Feb 2004, Dominique Devienne <[EMAIL PROTECTED]> wrote:
> Why go for 'ant.library.dir' instead of 'ant.library.dirs'?
OK, I've had a second look.
It seems as if we could do that with some simple changes in Launcher,
namely adding ~/.ant/lib and ${ant.library.dirs} to the libPaths list
and skip the special treatment and array copying for them completely.
With this the PATH tokenization logic would apply to the system
property as well.
The only thing that has to be looked into is that now ANT_HOME/lib is
used as ant.library.dir system property if the property hasn't been
set or points to something that doesn't exists. We'd need to modify
the checks for that second part.
So the change would be simple, but it is too late in the release
schedule for 1.6.1 to make it, since I think it should get discussed
before. This also means we'll have ant.library.dir as a
(undocumented) system property in 1.6.1, that will only work for a
single directory. We can always deprecate it later.
Does anybody have any thoughts on the original subject? Do we want to
allow a system property that contains a complete path instead of a
single directory to override ANT_HOME/lib?
Stefan
PS:
> Given that your get URL[], it obviously accepts several dirs,
No, the method returns the URLs of the jars in that (single) dir.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
