ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Loughran <>
Subject Re: Ivy task to import common build tasks
Date Tue, 16 Oct 2007 08:57:29 GMT
Gilles Scokart wrote:
> I have also seen something similar in the plan for ant 1.8 [1]:
> - import improvements (url support, searchpath support)
> I don't know if it includes also searching build file into a jar.  But I
> think that if you combine this futur demand with the ressources of 1.7, it
> should.

 > [1]

the main thing I'd thought of there was resource enabling <import>, so 
it would pull in a file from any resource, rather than just the filesystem.

<import >
   <zipentry archive="build/lib/" name="myproject/build.xml" />


<import >
   <url  url="" />

with the obvious security risks in the latter. (maybe I should extend 
url with an md5sum option)

One change we'd have to make to the resources is to allow resources to 
implement a relative-resource-source interface, so that when I import a 
URL, I can then do a relative resolution on its nested <import> 
statements to pull down other artifacts. zipentries would get at other 
zips, etc. We'd have to extend every ant project to track the resource 
it came from, instead of just its base dir.

I like the idea of pulling down specific versions of a library via ivy. 
If we made the resource enhancements to Ant, Ivy would have to match 
this with a resource that let you declare group/artifact/ entry

<import >
   <ivyentry org="org.apache" name="example" 
version="${example.version}" name="org/apache/example/build.xml" />

or, to load in files from a set of JARs:

<import >
   <ivyentry ivyconf="main" conf="test" 
name="org/apache/example/build.xml" />

Steve Loughran        
Author: Ant in Action 

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

View raw message