ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: Feature Request - import task use environment variable
Date Tue, 01 Dec 2009 05:17:20 GMT
On 2009-11-19, Kantor, H Steve Jr CIV NSWC PC <harry.kantor@navy.mil> wrote:

> The idea of the ANT_IMPORT_PATH is to provide a list of possible
> locations to import a file from.  Our shop places software either in
> $HOME/local (if you're compiling from source and do an "ant install"),
> $HOME/rpm (if you've installed from an rpm), or / (if installed as
> root).  This setup would allow me to set ANT_IMPORT_PATH to
> "$HOME/local:$HOME/rpm:/" and include the file with a simple import
> statement.

I see.

Another approach could be to add ANT_IMPORT_PATH to CLASSPATH and use a
<javaresource> to import it, this would work without any changes to
Ant trunk.

Ant isn't using environment variables anywhere outside of the wrapper
scripts and I'd be reluctant to using them - in particular given Java's
history of supporting or not supporting environment variables at all,
just look at the code Ant uses to read the environment on different
platforms.

Since you have opened a bugzilla issue for this - thanks! - people are
free to try it out and voice their opinion.  I for one am not convinced
this would belong in Ant's core, but wouldn't stand in the way if
another committer wanted to apply your patch.

Cheers

        Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message