Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I added basic support for the rtag command to sharpcvslib. This command
operates on the entire repository and tags all active (i.e. not files in
the attic, although there is an option to tag these as well) files
recursively by default. There are a number of command options for the
rtag but I only had the time right now to fill in the delete option, so
you have functionality to add a tag to a module and to remove a tag from
a module. =20
The basic approach I am taking with the options are to specify a true/
false value and have a private class hold constants for the argument
list which are then used to populate an ArgumentRequest. I might change
the class name from Options to Arguments tomorrow but in the meantime I
am just curious if anyone has comments or ideas on this as a general
approach to adding arguments?
I have also added a partial implementation of the fileset attributes.
The basic idea though is to pass in a list of files from the filesystem
(or a directory which will default to a recursive search). The manager
will then search the filesystem and populate objects that represent the
files in the cvs file (i.e. using the Entries, Entry, Folders, Folder,
Tag, Root, Repository, etc.) these will then be used to send information
on what needs to be updated to the cvs server.
I am going to try to hook it up to the update command tomorrow and will
add a better description of use then (probably to the netdoc).
PS: I also fixed a bug in the logging configuration