On Apr 8, 2005 4:53 PM, Clayton Harbour <[EMAIL PROTECTED]> wrote: > Hi Marcin, looks like a good outline. If I could offer a suggestion though > it might be better to concentrate on the new tasks for the rewrite and get a > good framework in place for them before moving on to the rewrite. There are > a couple of good reasons for doing that: > - can add patches or new functionality quite easily (i.e. quiet attribute) > while new framework is being implemented > - have a working interface in place to write unit tests for
Hi Clayton! Your proposal sounds very good. I have also been thinking of creating a little framework for making it easier to: * execute SVN commands, * parsing the results. The second objective is not very relevant in as far as tasks I mentioned before are considered. However, such a functionality may become crucial when it comes to implementing unit tests (verifying the results) and intercepting task execution results for any purpose (for example: to assign it to a property, I can think of situation when it could be a useful feature). I remember that you told me once that AbstractSourceControlTask was not received very well. Could you please remind me why? Or just give me a clue where to look for proper comments? Do you think that this discussion should be continued here or should be moved to Nant-developer mailing list? -- Marcin Hoppe http://hopson.blogspot.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ NAntContrib-Developer mailing list NAntContrib-Developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nantcontrib-developer
