ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Alberto Fernandez" <jalbe...@cellectivity.com>
Subject RE: Import basedir
Date Fri, 24 Jan 2003 12:50:05 GMT
> From: Costin Manolache [mailto:cmanolache@yahoo.com]
> 
> I don't know if a conclusion has been reached - but 
> I think it is clear that we need a way to support the various
> options - regardless of what default is chosen.
> 

fine.

> The best solution ( IMO ) is to associate each UnknownElement
> with a Source - the file ( or URL, InputSource, etc ) that was
> used to read it. The source will be a lightweight Project - with
> basedir, name, file, etc.
> 
> Resolving relative paths will be based on the Source or Project-
> based on some policy. 
> 

OK.

> The real problem IMO is the overloading of basedir - too many
> options. 
> 
> There are 2 intuitive behaviors: 
> - resolve a relative path based on the file where it was included
> - resolve it based on some base dir ( like PWD on unix ).
>

I would suggest refracing the above 2 options:
 - resolve a relative path based on the basedir of the file where it was included
 - resolve it based on some other base dir (like PWD on unix).
 
> Since most ant files are currently using the build file as 
> base - I think
> that must be the default, with explicit overrides permitted.
> 

I.e., Ant files currently use a basedir of "." which is relative to the buildfile,
this is the default for the basedir attribute on <project>.
But if we have <project basedir=".."> all current buildfiles expect to go
to use the parent directory.

> Disambiguating is another solution - just use a separate property
> to describe the "top" file, and use it explicitly in files written
> specifically for import ( like fragments ). 
> 

If we doit this way then we can deal with the issue of using the importer
basedir by just allowing something like:

	<import basedir="${basedir}" ..../>

> I can start working on an impl this weekend - unless someone else
> wants to do it or a different solution is proposed.
> 
> Costin 
> 

Jose Alberto
> 
> --
> To unsubscribe, e-mail:   
> <mailto:ant-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: 
> <mailto:ant-dev-help@jakarta.apache.org>
> 
> 

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


Mime
View raw message