On Tue, 26 Sep 2006, Stephen McConnell <mcconnell@dpml.net> wrote:
>> From: Matt Benson [mailto:gudnabrsam@yahoo.com]
>> Path's inheritance hierarchy was altered such that its immediate
>> superclass is the new Union resource collection. So the only
>> difference between the two is, for all practical purposes, the
>> filesystem-only restriction.
>
> Meaning that tasks such as javac (and others) that take classpath
> definitions as Path arguments could be changed to take a Union as an
> argument?
If you look through Ant 1.7.0 you will see that most tasks that
supported <filesets> or <paths> or ... now support arbitrary resource
collections. Tasks that supported nested <path> elements in Ant 1.6.5
now automatically support nested resources as child elements of that
<path>.
In the case of <javac> the compiler itself doesn't deal with anything
but file resources, so the tasks must ensure only Fileresources are
added - and <path> guarantees just that.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
|