ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yves Martin <>
Subject Re: Patch proposal for 1.6.3: parse a Ant project from a resource
Date Tue, 01 Feb 2005 13:17:19 GMT
"Jose Alberto Fernandez" <> writes:

>> From: Peter Reilly [] 
>> The problem is that this will not set the basedir correctly. 
>> (The basedir will be set to something like: 
>> File(url_string).getParentFile().getAbsolutePath()).
>> This will cause all sorts of problems and is the reason why 
>> <import url="..."/> has not been implemented.
> Maybe we could require a "basedir" attribute in such cases
> that must correspond to an existent, full directory location.

 And I have set the basedir before parsing my resource file.

> Of course, if such a place needs to exists for you to
> store the other files in your project, then the question
> is why don't you put the buildfile there as well?

 Good question. Here is the context:
 - I'm writing a build system with a 'pure' Ant (that may be open-sourced as
   soon as internal politic debates are over)
 - My build system plugin structure is simple: a jar with compiled classes and
   one or many Ant build file as resources. Of course such build file must
   fulfill constraints to work properly.

 At the moment, I'm using Ant 1.6.2 with a little patch already in CVS, to get
 a valid buildfile location instead of null. I'm waiting for 1.6.3 to get the
 build system work with an official release.

 The BuildException thrown by ProjectHelper2 when parsing a URL is annoying for
 me now. If my patch proposal is not accepted when 1.6.3 comes out, I will have
 to copy/paste the ProjectHelper2 in my core classes to disable that exception

 Thanks for your help
Yves Martin

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

View raw message