ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <>
Subject Re: Importing and caching build files from a URL
Date Tue, 29 Nov 2005 15:48:01 GMT
--- Dominique Devienne <> wrote:

> On 11/29/05,
> <> wrote:
> > It would fit better into Ant´s future if the
> existing <import> would
> > support <resources> - e.g. <urlresource>s.
> We've had this debate before...
> I'd be all for allowing to <import> resources
> instead of files, except
> for the way <import> was designed to not do things
> relative to its
> parent directory, like HTML and XSL hrefs. I can't
> see how we could
> have a clean "relative" import model like HTML/XSL
> while retaining BC.
> Yes, we could probably import easily a resource of
> the "first level",
> but it would be kludgy at best for this imported
> build to refer to
> other resources in the same jar file for example.
> So really we have to choose between limiting ourself
> to our current
> design for import, or extend it to resources but in
> such a way that I
> feel is unnatural, inconsistent, and a bit of a
> hack. But maybe I'm
> just missing the point somewhere, or my view that
> import is flawed is
> what flawed in fact ;-) --DD

Taking into account Jose Alberto and Benjamin
Burgess's input RE DLing & caching import files, sure,
great, but what's the point?  The point of resolving
paths blah blah is that files declared in the
<import>ed "resource" can be located.  Thus if the
whole context of the import file isn't also
downloaded, nothing will be accomplished.  I think we
should allow import to work as it always has or in
some extended manner, but basically we can start by
importing arbitrary resources and failing when an
attempt is made to resolve a file relative to the
location of a non-file import.  Then perhaps we can
examine how to allow resources to declare a context in
some manner.  This might involve the use of the
nearly-forgotten ResourceFactory interface.  No doubt
I have missed something, but at least dialogue is a
good catalyst to expose such...

Just out of curiosity, how many people other than
Peter and myself have ever started to modify <import>
to allow non-file imports?  :)


> To unsubscribe, e-mail:
> For additional commands, e-mail:

Yahoo! Music Unlimited 
Access over 1 million songs. Try it free.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message