On Wed, 17 Sep 2003, peter reilly <[EMAIL PROTECTED]> wrote:
> On Wednesday 17 September 2003 12:17, Stefan Bodewig wrote:
>> OK, if I nest <import> into a target, something like
>>
>> <target name="define-paths" depends="detect-platform">
>> <import file="${platform.specific.paths}"/>
>> </target>
>>
>> and this would import a file that had only <path> definitions - the
>> definitions are platform specific - will it work as expected?
> using <import> within a target does not work as the code
> that was placed in to handle top-level tasks/types does
> not work in this case (it assumes the pre-condition).
OK, this is an issue with the current implementation.
Shall we make this ("Thou Shalt Not Use <import> Inside <target>s") a
rule for <import> in general and enforce it? Or is my use-case above
a valid one and we change the implementation to deal with it?
Note that I'm not sure how I'd answer that myself. 8-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
