Thats one way. Another option is if your patternset is a simple string to assign it to a property and use it in both cases that way.
Or perhaps the new Selector stuff could be leveraged with a <not> in one case? Stevens, Brigham wrote: > OK... I think I have the answer: using includesfile and excludes file > instead of a pure patternset... This would allow me to use the same list > in multiple places, but toggle... > > Is this the best/only way to do it? I would rather keep it all inline in > the build file. > > -----Original Message----- > From: Stevens, Brigham > Sent: Wednesday, August 14, 2002 11:11 AM > To: [EMAIL PROTECTED] > Subject: patternset - including/excluding toggle... > > I have a pattern set that I want to be included in one step (both in jar > and copy tasks), but then the same patternset to be excluded in a > different task (again both in jar and copy). The goal is to have a task > that builds and deploys only a subset of the project, where the rest of > the project always exludes these same files. I didn't see on a fileset > how a patternset could be used, toggling the include/exclude. > > Thanks in advance, > --brigham > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
