ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antoine Levy Lambert <>
Subject Re: Unexpected mkdir and id behaviour
Date Mon, 25 Nov 2013 04:09:59 GMT
Hello Tom,

the id attribute in ant is generally used to reference types, for instance <fileset dir="src"

yo need to define properties to do what you want like :

<property name="contact.root" location="${toString:output}/contact-sheet"/>
<property name="" location="${contact.root}/${id}"/>
<property name="contact.metainf" location="${}/META-INF"/>
<property name="contact.oebps" location="${}/OEBPS"/>
<mkdir dir="${contact.root}"/>
<mkdir dir="${}"/>
<mkdir dir="${contact.metainf}"/>
<mkdir dir="${contact.oebps"/>



On Nov 22, 2013, at 5:45 AM, Tom Cleghorn wrote:

> Hi,
> I tried to use the following in 1.9.2:
> <mkdir dir="${toString:output}/contact-sheet" id="contact.root"/>
> <mkdir dir="${toString:contact.root}/${id}" id=""/>
> <mkdir dir="${}/META-INF" id="contact.metainf"/>
> <mkdir dir="${}/OEBPS" id="contact.oebps"/>
> where $output is a plain text property supplied to the build, expecting to 
> get four new directories, each created under the previous, and to have 
> four accompanying ids to refer back to them later with.
> Instead the ids resolve to things like 
> "C:\outputpath\\1234" (for 
> $ where $id is 1234). Echoing either $ or 
> $ returns the same in both cases. I haven't yet tried 
> previous Ant versions.
> Is this the correct behaviour? If so, what am I misunderstanding? Thanks!

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message