> -Original Message-
> From: Antoine Levy Lambert [mailto:anto...@gmx.de]
> Sent: Wednesday, December 09, 2009 6:43 AM
> To: Ant Users List
> Subject: Re: ANT Property substutition in log4j.properties
>
> Hello Jim,
>
> log4j understands system properties, not ant properties.
>
> So most
When using
ANT_ARGS="-lib $LOG4J -Dwork.dir=somepath -listener
org.apache.tools.ant.listener.Log4jListener"
where $LOG4J points to a directory containing log4j.jar, with a
log4j.properties including:
log4j.appender.LogFile.file=${work.dir}/build.log
On Windows ${work.dir} in log4j.pro
> -Original Message-
> From: Stefan Bodewig [mailto:bode...@apache.org]
> Sent: Wednesday, June 03, 2009 3:03 AM
> To: user@ant.apache.org
> Subject: Re: Clarification on definition of "reference"
>
Stefan, thanks very much for the reply.
Part of my confusion came from trying to underst
The ANT docs use the term "reference" in a way that, at least to me, is a
little confusing. The term "reference" seems to mean both the act of referring
to an object defined elsewhere (as in "refid=...") and also the object being
referred to. Are the following correct?
1. A "Property" is a
I've inherited a VERY complex ant-based build that is currently running on
1.6.0RC1, and I'm in the process of upgrading ANT to 1.7.1.
I've run into some curious behavior that looks like a bug in 1.6, that does not
occur in 1.7.1, and the build scripts seem to depend on this anomalous behavior.
