>>>>> "CM" == Conor MacNeill <[EMAIL PROTECTED]> writes:
>> (1) <src> would take different attributes and had no idea what >> "a/b:c/d" would mean. CM> sourcepaths may come from the external environment (although CM> probably unlikely). I've not thought of this, thanks. >> (2) Each <src> would have its own set of include/exclude patterns >> - which might be a good thing or not. And we could reuse patterns >> previously defined via fileset's <patternsetref> element. CM> This tends to move from compiling classes in the package space to CM> compiling file in the filesystem. I wonder how, given a fileset, CM> you can know where the package root is? (I'm not yet that CM> familiar with filesets, though) Each fileset has its own "dir" attribute, making up for a package root of its own. It still lives in the package space - at least that's how I've looked at it. Stefan
