|
From: Steve F. <st...@m3...> - 2007-05-03 22:17:16
|
Sorry Mike, but I put my time in on that project and handed it off in the hope it would get looked after. I don't have a .Net environment at the moment so it's hard for me to do serious work. I added the last committer because he needed updates to keep NMock in his project. The issue is not that NMock uses strings (although c.f. the work that Nat has been doing in jMock), the issue is whether the project is still live and responsive. From the traffic I've seen, many people in the .Net world assume that it's dead. S. On 3 May 2007, at 22:43, Mike Mason wrote: > On 5/3/07, Steve Freeman <smg...@gm...> wrote: >> >> This is part of a string of similar messages on the TDD list. >> >> Looks like NMock is dead in the water. Any of the committers still >> there? >> > > There are 18 committers on the SourceForge project, including > yourself. I > believe at least two of those have been recently added in response > to a call > for people who have time they can devote to applying NMock patches, > etc. > > The discussion over on the TDD group is fair -- NMock doesn't use > record/playback like Rhino does, and so gets caught out when you > refactor > method names or add/remove parameters. This isn't going to change, > and if > people really want refactoring support that's better than > ReSharper's "also > look in strings" option, they should pick Rhino. > > I do agree that NMock's error messages and general friendliness > could be > improved, and it'd be great to see people such as yourself committing > changes to help out. > > Cheers, > Mike. |