Re: [nant-dev] RE: copy task

[Ian M. <ianm@ActiveState.com>]

OK,
I've got it done now. The copy task will now handle :
    <copy file="${dir.build}\NAnt.exe" todir="${dir.dist}\bin"/>
    <copy todir="${dir.dist}">
            <fileset dir=".">
                <includes name="NAnt.build"/>
                <includes name="NAnt.key"/>
                <includes name="README.txt"/>
                <includes name="COPYING.txt"/>
            </fileset>
        </copy>


but not yet:
         <copy todir="${dir.dist}\examples">
            <fileset basedir="examples">
                <includes name="**"/>
                <excludes name="**\CVS\*"/>
            </fileset>
        </copy>

although that will come from the mapper implementation. I'm assuming 
that FileSet.GetFileNames will be the place to handle mappings ie

**/* wildcards. The move task should be basically similar. I'll get to 
that shortly - after I take next week off that is.

Gerry Shaw wrote:

>Attached is the my ideal Nant build file - it makes heavy use of the
>copy task.  Currently Nant cannot handle this but I think we should work
>to getting it too.
>
>Having **/* support with filesets along would be really powerful.  I
>think I'll just directly port the stuff Ant and see how that goes.  The
>classes I'm thinking are FileSet, PatternSet and Mapper (along with the
>standard mappers Ant implements).
>
>
>