Hi, > > the naming is clearer I suppose but there is a certain amount of > > inertia > > - there are a lot of build files out there wil the current naming. > > I know, that why I'm asking ... we'll see how others respond > ... we could ofcourse have both of them coexist, and then > deprecate includes/excludes later ...
I would prefer it if the two co-existed for a release (or two even), with the <includes /> element deprecated (and warnings during the build process). It gives people fair enough warning before their build files stop working. Also, there was also talk about adding a "strict" switch to the commandline awhile back which. This might be a good notification feature when this goes away. Has anyone done any work on this? I could probably take a stab at it if someone gave me a high level on the project load process. Cheers, Clayton ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id%62&alloc_ida84&op=click _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
