The first test will only tell if the task is loaded, not whether it can run.
Since you can specify a program for the task to run, in each instance (since
it derives from the ExternalProgram base class), it is possible that it
should load even if the default program location is invalid. It would seem
that for now the <al/> task should probably not show as, or simply not be,
loaded under mono (though, under windows you could always us the ms one even
if you are building for mono).
This is a level of granularity which we cannot yet address in nant. It may
be something to think about though.
----- Original Message -----
From: "Rodrigo B. de Oliveira" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Tuesday, January 06, 2004 3:55 PM
Subject: [nant-dev] al task doesn't work under mono
> But nant think it should... Nant is trying to run /usr/bin/al.exe but
> there's no such file.
>
> I was trying to detect the availability of the al task with the stock
trick:
>
> <if test="${not property::exists('nant.tasks.al')}">
> <echo>al task is not available. Satellite assemblies won't be
> built.</echo>
> <property name="skip.satellites" value="True" />
> </if>
>
> But had to resort instead to:
>
> <if test="${'mono-1.0' == nant.settings.currentframework}">
> <echo>al task is not available. Satellite assemblies won't be
> built.</echo>
> <property name="skip.satellites" value="True" />
> </if>
>
> Shouldn't al be disabled under mono?
>
> Best regards,
> Rodrigo
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
