Worked for me, too, on Windows NT with the last stable release of Ant (no CVS stuff).
---------- Craig S. Cottingham [EMAIL PROTECTED] PGP key available from: <http://pgp.ai.mit.edu:11371/pks/lookup?op=get&search=0xA2FFBE41> PGP ID=0xA2FFBE41 PGP fingerprint=6AA8 2E28 2404 8A95 B8FC 7EFC 136F 0CEF A2FF BE41 > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 08, 2000 10:15 AM > To: [EMAIL PROTECTED] > Subject: Re: Using built in task ant with > > > >>>>> "RD" == Roderick Dunne <[EMAIL PROTECTED]> writes: > > RD> The problem is now gone. It was resolved by using absolute paths > RD> instead of relative paths when using the mkdir built in task (os > RD> = Windows). > > I'm not convinced. I have a testcase I ask you to try. In an empty > directory place the buildfile > > <project name="test" default="testsubprog"> > <target name="testsubprog"> > <ant dir="sub" /> > </target> > </project> > > and create a subdirectory named sub. Into sub place a buildfile > > <project name="sub" default="mk"> > <target name="mk"> > <mkdir dir="test" /> > </target> > </project> > > This creates sub/test for me - on Linux with the latest CVS sources > and a whole bunch of private patches that shouldn't affect your > problem. > > I'm still suspicious it might be the properties. A property task in > the main file will override all property tasks - for the same name - > in your sub projects. > > Stefan >
