Apache Ant Copy + FileSet Include Issue: Why Comma-Separated include name Fails

If your Apache Ant <copy> task seems to skip files when you use <include>, the problem is usually pattern syntax, not the copy task itself. This guide explains why one style fails, why the other works, and how to write include rules that are predictable.

Originally published on 2009-06-20; fully revised and updated.

Source scenario: DevOpsSchool original post.

Why Program 1 fails and Program 2 works

In a <fileset>, a nested <include name="..."/> expects one pattern per include element. It does not automatically split a comma-separated string into many names. By contrast, the includes="..." attribute supports a list, so comma-separated values are parsed as multiple patterns.

Failing style (single nested include with commas)

<copy todir="${Temp}/uaw/Uaw_compilescripts">
    <fileset dir="${SVNCheckout}/scripts/compilescripts">
        <include name="BuildSh,Compsh,vsamc,buildc.sh,script,compl2,main.sh,makefile,makepl1,script"/>
    </fileset>
</copy>Code language: HTML, XML (xml)

This is treated as one literal pattern string. Unless a real filename matches that entire comma-joined value, no files are copied.

Working styles

<!-- Option A: one nested include per pattern -->
<copy todir="${Temp}/uaw/Uaw_compilescripts">
    <fileset dir="${SVNCheckout}/scripts/compilescripts">
        <include name="BuildSh"/>
        <include name="Compsh"/>
        <include name="vsamc"/>
        <include name="buildc.sh"/>
        <include name="script"/>
        <include name="compl2"/>
        <include name="main.sh"/>
        <include name="makefile"/>
        <include name="makepl1"/>
    </fileset>
</copy>

<!-- Option B: includes attribute with a list -->
<copy todir="${Temp}/uaw/Uaw_compilescripts">
    <fileset dir="${SVNCheckout}/scripts/compilescripts"
             includes="BuildSh,Compsh,vsamc,buildc.sh,script,compl2,main.sh,makefile,makepl1"/>
</copy>Code language: HTML, XML (xml)

How Ant processes include patterns

flowchart TD
    A[copy task runs] --> B[fileset reads base directory]
    B --> C{Pattern source}
    C --> D[includes attribute list]
    C --> E[nested include elements]
    D --> F[List split into multiple patterns]
    E --> G[Each include name is one pattern]
    F --> H[Matching files copied]
    G --> I[Comma joined name usually no match]
    I --> J[Copy seems to fail]

Comparison of include approaches

Debugging and verification commands

When copy behavior is unclear, run Ant in verbose or debug mode to inspect resolved file patterns and copied files.

ant -v copy-scripts
ant -d copy-scripts

<target name="copy-scripts">
    <copy todir="${Temp}/uaw/Uaw_compilescripts" overwrite="true">
        <fileset dir="${SVNCheckout}/scripts/compilescripts"
                 includes="BuildSh,Compsh,vsamc,buildc.sh,script,compl2,main.sh,makefile,makepl1"/>
    </copy>
</target>Code language: HTML, XML (xml)

Best practices

• Use includes="..." for compact lists, or one nested <include> per pattern.
• Avoid duplicates in include lists (for example, repeated script entries) to keep builds readable.
• Prefer explicit filenames or well-scoped wildcards so copy behavior is deterministic.
• Use ant -v or ant -d whenever file selection does not match expectations.

Rajesh Kumar

I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.

I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.