Hello all, I am new to this mailing list.
I have a question about avoiding redundancy when declaring paths and filesets. A lot of times I declare a <classpath> and then I reference it from other targets. That's OK, but what about targets like <copy>. How can I reuse the defined <classpath>? As far as I know I cannot set a path in the <copy> target. Unfortunately, in that case I define multiple filesets and I use them within the <copy> target. What I could do is to have a global <fileset> but this cannot be done regarding the nature of the project I am involved with. There is not a starting directory for <fileset>. So at the end I have to update all filesets and classpaths whenever I add or remove a library or resource :( Do you know how I can tackle that problem? How do you avoid such kind of redundancies? How do you keep a central point of filesets/paths? Thank you in advance, Kostas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
