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
If you have any questions you can drop me a line.
Cheers,
Clayton
-----Original Message-----
From: Marcin Hoppe [mailto:[EMAIL PROTECTED]
Sent: Thu 4/7/2005 3:19 PM
To: NAntContrib-Developer@lists.sourceforge.net
Cc:
Subject: [NAntC-Dev] Subversion tasks enhancement
NAnt Subversion Tasks Ehnancement Proposal
Rationale
=========
Currently there are only a few Subversion tasks supported:
* generic SVN task,
* SVN update task,
* SVN checkout task.
These tasks do not provide explicit support for some options (for
example: "quiet") and do not cover all the tasks that are expected to
be available for everyday's work.
An idea
=======
To circumvent current limitations of NAnt Subversion tasks it would be
preferrable to redesign and rewrite SVN tasks from scratch (AFAIK
they've been written to mimic CVS tasks, so maybe there are things
that could be done better).
I suggets implementing following types of SVN tasks:
* generic SVN task (with syntax similar to <exec> task),
* SVN update task,
* SVN commit task,
* SVN copy task.
In next stages of development the above list should be extended with:
* SVN checkout task,
* SVN import task,
* other tasks that NAnt users would like to have.
In first stages of development all the interaction with Subversion
should be done via the Subversion command line tool. In later stages,
Subversion's client library could be used.
Problems
========
One of the biggest problems are unit tests. They require either local
test repository or some remote test repository. It is advisable that
unit tests could be somehow configured not to run on machines that do
not have proper configuration (for example: not having Subversion
installed at all) or to create test environment themselves (for
example: creating a test repository).
Further proposals
=================
I believe that this proposal should be discussed on NAntContrib
mailing list. If NAnt users and developers want to have Subversion
tasks rewritten and redesigned, I'll try to handle this task with
pleasure. All help is of course greatly appreciated!
If you feel that this message should be forwarded to Nant-developer
mailing list or any particular person, please let me know.
Best regards!
Marcin
-------------------------------------------------------
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
