> ----- Original Message -----
> From: "Castro, Edwin Gabriel (Firing Systems Engr.)" <[EMAIL PROTECTED]>
> To: "Gert Driesen" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Wednesday, December 01, 2004 5:57 PM
> Subject: RE: [Nant-users] Re: FileSet Behavior
>
> > > >
> > > ><delete>
> > > > <fileset basedir="${folder}">
> > > > <include name="**\bin" />
> > > > <include name="**\obj" />
> > > > </fileset>
> > > ></delete>
> > > >
> > > >Unfortunately, NAnt doesn't delete the folders. I suspect
> > > that this is
> > > >because the folders are not empty.
> >
> > Yeps
> >
> > > The help suggests that I can specify
> > > >a folder to be deleted with all of its sub-folders. This obviously
> is
> > > >not true when using a fileset. I haven't tested this using the
> 'dir'
> > > >attribute.
> >
> > The base directory of the fileset itself will never be removed.
> >
>
> What I meant is that the documentation seems to imply (at least to me)
> that the snippet above would match all bin and obj directories
> underneath the ${folder} base directory and delete them, even if they
> are not empty.
> But as you say, they are not deleted because they are not
> empty. I was just trying to point out a potential point of confusion for
> users in the documentation.
I agree that the docs aren't very clear on this topic, but you indeed use
this to accomplish that (once that bug is fixed) :
<delete>
<fileset basedir="${folder}">
<include name="**/bin/**" />
<include name="**/obj/**" />
</fileset>
</delete>
Gert
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
