Hi all.
Generally, environment variables are case-insensitive. However,
nant properties are not. So you may get into some trouble when
using the <sysinfo> task.
E.g. we use a environment variable on the development machines
to set the root source directory named BuildBase:
set BuildBase=d:\src
Then I'm able to use it in my build file:
<sysinfo />
<echo message="BuildBase is ${sys.env.BuildBase}" />
Well, I name it BuildBase. Some colleagues have named it BUILDBASE,
some buildbase. Unfortunately, the build script cannot handle that,
because properties are case-sensitive.
Therefore, I propose to add another flag to the <sysinfo> task,
e.g. envuppercase="True". Following the example above, I could right
<sysinfo envuppercase="True" />
<echo message="BuildBase is ${sys.env.BUILDBASE}" />
without having to respect the different cases.
What do you think?
Regards,
Thomas
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
