hmm. keeping backwards compatible with an incorrect implementation seems like the wrong thing to do.I fixed this issue and the testers locally, but I'm not sure if I can commit them as these changes would break backwards compatibily.
I say we fix it. I remember this issue or somthing like it coming up a while ago. Did it just not get fixed at that time or has somthing else changed ? I'll have a look thru the archives.
But I still think we should fix the issue and make sure the change is well documented in the release notes.
Ian, what do you think ?
Ian
v
------------------------------------------------------- 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
