+1
This seems the reasonable choice.
Costin Manolache wrote:
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.
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.
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 ).
Since most ant files are currently using the build file as base - I think
that must be the default, with explicit overrides permitted.
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 ).
I can start working on an impl this weekend - unless someone else
wants to do it or a different solution is proposed.
Costin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
Nick Chalko Show me the code.
Centipede
Ant + autodownloadable build plugins + needed jars autodownload.
http://krysalis.org/centipede
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
