> The current file attribute of the import task is meant to act
> in the same way as href in html- - i.e relative to the
> directory that the importer file is in.
>
> THe import task could easily use urls in the same way - but
> some internals in ant assume that build files are Files and
> only Files.
Excatly. Which is why I think adding href support could be a means to
retain existing BC, while changing some Ant internals to switch
between the current behavior and a new one what wouldn't assume File.
But I think Peter that I meant having not only <import> be relative
(you're rigth it already is), but also other tasks like <property
file> or <loadfile>. Currently they behave relative to the importing
build's basedir, not the imported build's "href". Having new href
attributes would imply the relative to current build file's "href"
behavior, while traditional file/location attributes would continue to
mean "relative to ${basedir}".
BC would be retained, and the new behavior has to be explicitly used
to come into play, using the "standard" attribute name (href) which
behaves the "standard" way. The best of both worlds? --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
