issue with tar and filesets

[ma...@pncbank.com]

I have a backup task:
        <property name="pnc.build.backup.filename" value="backup" />
        <property name="pnc.build.backup.include" value="**"/>
        <property name="pnc.build.backup.exclude" value="logs/**,
**/EmbeddedLDAP.lok,**/*.tar" />
. . .
        <!--Backups Specific for UNIX OS-->
        <target name="backupUnix" description="backup the specified files
for a unix OS" if="pnc.build.os.unix">
                <!--tar the files up-->
                <tar tarfile="${pnc.build.backup.basedir}/
${pnc.build.backup.filename}.tar.gz" compression="gzip">
                        <tarfileset dir="${pnc.build.backup.basedir}">
                                <exclude name="
${pnc.build.backup.exclude}"/>
                                <include name="
${pnc.build.backup.include}"/>
                        </tarfileset>
                </tar>
        </target>
and is started with -Dpnc.build.backup.basedir=/app/ba

this it the -debug output
backupUnix:
Tar$TarFileSet: Setup scanner in dir /app/ba with patternSet{ includes:
[**] excludes: [logs/**,**/EmbeddedLDAP.lok,**/*.tar] }
      [tar]  added as /app/ba/backup.tar.gz doesn't exist.
      [tar] applications added as /app/ba/backup.tar.gz doesn't exist.
      [tar] applications/.wlnotdelete_ba1 added as /app/ba/backup.tar.gz
doesn't exist.
      [tar] applications/.wlnotdelete added as /app/ba/backup.tar.gz
doesn't exist.
      [tar] logs added as /app/ba/backup.tar.gz doesn't exist.
      [tar] ba1 added as /app/ba/backup.tar.gz doesn't exist.
      [tar] ba1/ldap added as /app/ba/backup.tar.gz doesn't exist.
      [tar] ba1/ldap/ldapfiles added as /app/ba/backup.tar.gz doesn't
exist.
      [tar] ba1/ldap/replicadata added as /app/ba/backup.tar.gz doesn't
exist.
      [tar] ba1/ldap/log added as /app/ba/backup.tar.gz doesn't exist.
      [tar] ba1/ldap/backup added as /app/ba/backup.tar.gz doesn't exist.
.
.
.
      [tar] logs/access.log added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stdout.log added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stderr.log added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/weblogic.log added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stdout.log.0 added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stderr.log.0 added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stdout.log.1 added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stderr.log.1 added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stdout.log.2 added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stderr.log.2 added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stdout.log.3 added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stderr.log.3 added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/mydomain.log added as /app/ba/backup.tar.gz doesn't exist.
      [tar] logs/stdout.log.4 added as /app/ba/backup.tar.gz doesn't exist.

according to the file scanner I should not see any files in the log
directory, EmbeddedLDAP.lok, or *.tar files but as you can see from the
output this information is being added.

any ideas why?

Mark Russell
PNC
412-768-9603

Re: issue with tar and filesets

[Stefan Bodewig <bo...@apache.org>]

On Thu, 22 May 2003, mark russel <ma...@pncbank.com> wrote:

>         <property name="pnc.build.backup.exclude" value="logs/**,
> **/EmbeddedLDAP.lok,**/*.tar" />

>  <exclude name="${pnc.build.backup.exclude}"/>

is the problem.

The name attribute of <exclude> wants a single pattern, you give it a
list of patterns.  Either use three <exclude> elements ot the excludes
attribute of <fileset>.

Stefan