Hi Ian, > > I'm not saying we should actually always use the latest version, but when > > possible (and after enough testing) yes. > Agreed. > > In my opinion, we should really try to use only binary releases of other > > projects and work with those other teams to get bugs fixed (or functional > > changes introduced). We should consider NDoc as just another tool, it's not > > because the source is available that we should go ahead and create our own > > version. > Actually this is what we are doing. You'll notice that there is no ndoc > source inside the NAnt tree. > > What we have done is create a custom documenter for creating the NAnt > docs. This is just for 'our' build process not for users of NAnt. I > think Scotts previous post about "custom changes to the msdn documenter" > are based on misunderstanding this. It shouldn't take too much work to > fix the custom documenter to work with the current version.
I'm glad to hear this !! > > > > It should actually be possible not to include Ndoc assemblies in the NAnt > > distribution at all and just tell users to get version xx.xx of NDoc and > > copy assembly x and y to directory z. I'm not saying we > > should do it like that, but we should actually make this possible. > Yes and it will be. Probably is now - you just have to use ndoc v1.0 > binaries. Ofcourse, no problem with that. I think it's just something that should be looked into for future releases. > > > For users, it should always be clear which version of NDoc, NUnit, > > SharpZipLib and so NAnt uses (or requires / supports). > > Somthing more for the docs/faq. We need to be careful that we update > included binaries when each project has a stable version of we think > about supporting multiple versions so people don't upgrade NAnt and > suddenly find all their unit tests don't work. SharpZipLib probably > isn't a big concern - as long as it produces valid zip archives users > probably won't care what version we're using :) It's not just about users, what exact version of the third-party tools NAnt uses should be available to everyone (including, and perhaps most important, the developers). > > hmm maybe we could have somthing like nant -help tasks which would > output specific version info for each task. As well as having it the > help for each task. That would definitely be great, but I'm not just talking about the assembly build numbers, I think actual version number should also be used. Do you know what NDoc version 1.1.1116.1236 is ? 1.1a, 1.1b, 1.1c, you know what I mean ... Gert ------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
