Holger Rauch wrote:
Hi Peter!
Thanks a lot for your quick reply!
On Tue, 15 Mar 2005, Peter Reilly wrote:
One can have a top-level fileset on unix.
What happens on Windows? Do I have to use some other value for dir there?
There is no top-level directory on windows. Each file system
has i
Hi Peter!
Thanks a lot for your quick reply!
On Tue, 15 Mar 2005, Peter Reilly wrote:
> One can have a top-level fileset on unix.
What happens on Windows? Do I have to use some other value for dir there?
> [...)
> However, the filename specs in the includes still need to be relative
> so they
One can have a top-level fileset on unix.
However, the filename specs in the includes still need to be relative
so they cannot include a leading directory separator.
files: ${files.converted}
files2: ${files2.converted}
outputs:
top:
[echo] files: etc/passwd
[echo]
I've never used a top level fileset before, didn't think you could do
that. I would use a which contained the fileset.
Holger Rauch wrote:
Hi!
I've run into a problem using filesets whose members contain absolute path
names. The following short build script illustrates the problem.
My ques
Hi!
I've run into a problem using filesets whose members contain absolute path
names. The following short build script illustrates the problem.
My questions are:
Why is the property files.converted (supposed to hold the fileset's contents)
empty even though the files actually exist on my system?
