Re: Passing list of classes to exclude from build as macrodef attribute

2012-03-09 Thread Scot P. Floess
I'm fairly certain you may be able to avoid the duplication... From the documentation for javac, "This task forms an implicit FileSet and supports most attributes of (dir becomes srcdir) as well as the nested , and elements." You can probably come up with a way to reuse the notation...

Re: Passing list of classes to exclude from build as macrodef attribute

2012-03-09 Thread Noam Postavsky
On Fri, Mar 9, 2012 at 10:18 AM, Scot P. Floess wrote: > >     >         >     > >     >         >     > > > > Arguably, a little uglier notation... I'm not worried about notation, but I'd like to avoid repetition; using this method I would need to do repeat every excluded class name twice: onc

Re: Passing list of classes to exclude from build as macrodef attribute

2012-03-09 Thread Scot P. Floess
You'll need to do something like this... Then you can do things like: Arguably, a little uglier notation... On Fri, 9 Mar 2012, Noam Postavsky wrote: On Fri, Mar 9, 2012 at 8:20 AM, Scot P. Floess

Re: Passing list of classes to exclude from build as macrodef attribute

2012-03-09 Thread Noam Postavsky
On Fri, Mar 9, 2012 at 8:20 AM, Scot P. Floess wrote: > > Why not just use a child element for the macrodef?  Something like: Ah, I didn't realize that was possible. > >     >     > That's better, but I also need to get rid of the class files (convert is JavaCard converter and it takes all th

Re: Passing list of classes to exclude from build as macrodef attribute

2012-03-09 Thread Scot P. Floess
Why not just use a child element for the macrodef? Something like: Then you can do things like: On Thu, 8 Mar 2012, Noam Postavsky wrote: I have a build.xml with some targets that are identical except for some excluded classes. C