OK, that's good to know. If I can't find a way around it I may give that a
go.
Thanks,
Dhruva
On 6/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Not all tasks can work with nested paths in prior to Ant 1.7.
With 1.7 we are introducing "ResourceCollections" which is a supertype a
,
Not all tasks can work with nested paths in prior to Ant 1.7.
With 1.7 we are introducing "ResourceCollections" which is a supertype a
, and others. I'm not sure if supports that, but
most of the tasks are converted ...
Yep - inherits inherits . And supports RCs [1].
So your life will be
Dhruva:
Have you considered using path with id...like:
...
...
Then just use the refid "MY_PATH"...
Dhruva Reddy wrote:
Hello,
We have a target that builds an EAR using the ear task. Fed into the
task
is a rather large number of fileset's. What I would like to do is use
the
sa
Hello,
We have a target that builds an EAR using the ear task. Fed into the task
is a rather large number of fileset's. What I would like to do is use the
same fileset's for another task (I want to copy those elements into the app
server without building the EAR).
Is there any way to aggregate