that is ok, it is just that I normally have the same basedir for all builds to always do the same kind of file usages, (${basedir}/src/${module}).

It was just a question, it is ok, and I've read the note, but I wanted the reason, that's all.

MAriano

Stefan Bodewig wrote:

On Wed, 11 Feb 2004, Mariano Benitez <[EMAIL PROTECTED]> wrote:



Why the file attribute of the import task is not considering files
relative to the basedir?



This is because you may use <import> in a file that itself gets <import>ed and then basedir would be that of the outer-most project and not the one of the file you are looking at.

See this note from the manual

,----
| Important: We have not finalized how relative file references will be
| resolved in deep/complex build hierarchies -such as what happens when
| an imported file imports another file. Use absolute references for
| enhanced build file stability, especially in the imported files.
`----

which is no longer completely true since we are bound by backwards
compatibility after we've released 1.6.

use <import file="${ant.file.pepe}/../include.xml"/>

instead of



<project name="pepe" basedir="..">
<import file="include.xml"/>



Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to