I'll check on that... in order to do that, however, how can I dump what is in
the fileset (for debugging) ? And why do absolute paths not work? That seems
like an odd restriction...
On Thu, 27 Jan 2005 16:27:53 -0600, Dominique Devienne <[EMAIL PROTECTED]>
wrote:
From: michael sorens [mailto:[EMAIL PROTECTED]
I had an open question on this issue several days ago for which no one
has
taken up the gauntlet.
Well, in fact I did answer...
To make it very brief, I want to use a set of files in two places:
inside
an <uptodate> checker,
and as <arg>s to a <java> task. The build file fragment shown here
works
for the <uptodate> check, but the js.plain.files property comes out
empty.
Why?
And the reason is that your include patterns are incorrect most likely.
If you have /usr/foo/bar/bar.js, you should have a fileset like so:
<fileset dir="/usr/foo">
<include name="bar/bar.js" />
</fileset>
while yours is probably like so:
<fileset dir="/usr/foo">
<include name="/usr/foo/bar/bar.js" />
</fileset>
which isn't correct. The pattern must be relative to dir. --DD
<fileset dir="." id="plain.files">
<include name="${jslib}/Util/Version.js"/>
<include name="${jsmenu}/ccmenu.js"/>
<include name="${jslib}/Util/NavKeys.js"/>
</fileset>
So again, your use of ${jslib} and ${jsmenu} are the likely culprit why
your fileset is empty. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
