Solved!
Here's what was going on: I have a project, and I create all of my
build output under the "target" directory. Under this directory, I
usually create a archive folder and I put my tarball under that
folder.
In this particular project, I placed all of the files I wanted to
archive into the target folder, and then tar'd up all the files
(except the archive folder).
What was going on is that the user wanted to do was copy the client
files directly into the target folder, so they'd all be in the base of
the tarball. One of these folders was called "archive", so all the
files in this folder were copied under my archive folder which I then
excluded.
We solved this issue by creating a folder called target/work, moved
all the files that should be in the tarball under this folder, and
then tar'd up this directory. No muss, no excludes needed.
--
David Weintraub
[EMAIL PROTECTED]
On Wed, Oct 29, 2008 at 1:16 PM, David Weintraub <[EMAIL PROTECTED]> wrote:
> I have a fileset that looks like this:
>
> <fileset dir="${target.dir}>
> <exclude name="archive/**/>
> </fileset>
>
> The problem is that I have the following structure:
>
> ${target.dir}
> archive
> tarball.tar.gz
> work
> clients
> archive
> tarball.tar.gz
> foo
>
> The purpose of the fileset was to exclude the "archive" directory
> directly under ${target.dir} (and the tallballs in it), but I do want
> to include the "archive" directory under the "clients" directory.
> However, my fileset now excludes both. Anyway I can specify to keep
> one, but not the other?
>
> --
> David Weintraub
> [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
