On 2011-12-15, Vinodh Kumar wrote:
> Can someone let me know why the /${${env}.test} value not printed as
> testest1/
http://ant.apache.org/faq.html#propertyvalue-as-name-for-property
Stefan
-
To unsubscribe, e-mail: user-unsub
Hi,
Can someone let me know why the /${${env}.test} value not printed as
testest1/
*cmd*:ant -f build.xml -Denv=IT1
*build.xml*
${env}
${${env}.test}
*build.properties*
IT1.test=testest1
*OUTPUT:*
task:
[echo] IT1
[echo] $
On Fri, Dec 16, 2011 at 2:40 PM, Perrier, Nathan wrote:
> http://ant.apache.org/manual/targets.html
>
>
>
> Anyone have an example of where they found extension points useful?
>
One way of thinking of extension-points is as a somewhat Maven-esque
view of a build, whereby you can define a basic "l
http://ant.apache.org/manual/targets.html
Anyone have an example of where they found extension points useful?
I have to maintain a fairly large Ant framework, but I'm not quite of a
good use-case for them.
Thanks,
-Nathan
On Thu, Dec 15, 2011 at 4:45 PM, Perrier, Nathan wrote:
> You can't do that! Double interpolation doesn't work.
>
> Fortunately, you can use a macro to accomplish it:
>
>
>
>
>
>
>
>
>
Another possibility is the nested PropertyExpander provided by
http
On Thu, Dec 15, 2011 at 11:06 PM, redspider red wrote:
> Hello,
> I want to use ant build latex code. the destination
> file is demo.pdf, but ANT can not compare the time stamp between tex
> and pdf, so ANT build pdf always.
>
> How can I resolve it.
Timestamp comparison is something typically
