Ian wrote: [snip] > so yes it needs some work but we are working on it.
I consider NAntContrib to be a playing ground for contributing _developers_ to create new tasks, before these enter the main repository. For this purpose, it functions perfectly. In fact, I wish that the solution task, which is still heavily under development, would have followed the NAntContrib route. It would have made it a lot easier to make the final 0.8.3 release. Initially, it took me a while to set NAntContrib up, but I learned many valuable lessons about the internal workings of Nant during this phase. People who do not wish to learn these lessons should wait for a NAnt release, which contain the NAntContrib files. However, and I think no one disagrees with this, the situation could be better. For instance, a couple of weeks ago, the Windows Installer tasks simply would not compile. I created a patch, sent it to nant-dev, and the issues were resolved. That's how open source works, people: you _contribute_. Either with a bug report, a tracelog, a patch, some documentation, or a reply to people with problems you solved before. Whining is not contributing. I consider NAnt & NAntContrib to be quite mature and 'corporate-ready' (whatever that means). We use Nant, NAntContrib and CruiseControl.NET in our build environment, and after running for two months, building every 15 minutes, it hasn't failed me yet. That's more than I can say about some closed software products. Sorry for the rant, but in contrast to all remarks about NAntContrib made on this list recently, I wished to shed a different light on this issue. Cheers, Arjen ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
