We checkout a fixed set of directories using CVS module aliases. This works okay and the build completes successfully. When tagging the build, however, each file that is to be tagged returns an error such as:

Using locally configured password for connection to :pserver:bbergquist@cvs.canoga.com:/srv/cvs/software
cvs server: modules file missing directory for module csem-pkg9145eLB-pkg/csem-pkg9145eLB/csem-pkg9145eLB-api/src/com/canoga/nms/pkg/pkg9145eLB/v4_00/device/command/Module9420_302UNIPortConfigLoadCmd.java

Usage: cvs rtag [-abdFflnR] [-r rev|-D date] tag modules...
-a Clear tag from removed files that would not otherwise be tagged.
-b Make the tag a "branch" tag, allowing concurrent development.
-B Allows -F and -d to disturb branch tags. Use with extreme care.
-d Delete the given tag.
-F Move tag if it already exists.
-f Force a head revision match if tag/date not found.
-l Local directory only, not recursive.
-n No execution of 'tag program'.
-R Process directories recursively.
-r rev Existing revision/tag.
-D Existing date.
(Specify the --help global option for a list of other help options)

Note that this same setup works correctly on Hudson which uses the "cvs tag" and not "cvs rtag" command. I believe it has something to do with the "cvs rtag" trying to specify resolve through the aliased module names.

I would be happy if the Tag This Build gave the option to use "cvs tag" (the old method).

I have attached my "modules" file so that you can see the structure. In this case I checked out "csem-pkg9145eLB-pkg" which as you can see has many modules and aliases reflected through it.