ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen McConnell" <mcconn...@dpml.net>
Subject RE: Resource.getURL()
Date Mon, 25 Sep 2006 20:26:19 GMT
 

> -----Original Message-----
> From: Matt Benson [mailto:gudnabrsam@yahoo.com] 
> Sent: Tuesday, 26 September 2006 4:28 AM
> To: Ant Developers List
> Subject: RE: Resource.getURL()
> 
> --- Stephen McConnell <mcconnell@dpml.net> wrote:
> [SNIP]
> > 
> > Some thoughts after digging though Resource and associated 
> classes ...
> > 
> > Of particular interest to me is the ability to declare 
> > resources that can be used as arguments to a Path 
> > definition - however, as things currently stand the Path
> > datatype explicitly excludes resource collections that 
> > are not file based (which seems to me to defeat the 
> > purpose of Resource - but I'm hoping this is resolvable).
> > 
> 
> We could come back to this; in my opinion relaxing this 
> restriction in the future would not hurt anything.  However, 
> in the ResourceCollection refactoring, 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.  Path further supports its 
> historical API e.g. <pathelement>, list().  But to get back 
> to the point, in general a <union> can be used where a 
> filesystem-agnostic <path> is desired.

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?

/Steve.

--------------------------
Stephen McConnell
mailto:mcconnell@dpml.net
http://www.dpml.net
 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message