Trouble with ExportCommand - more info

OK, this must be a tough one.  So, looking at the following exception
stack, you see that the exception occurs during the
SetStickyResponse.process.  But, I am not using sticky tags.  Why would
SetStickResponse.process get called?

I've been able to determine that SetStickyResponse.process thinks that the
/CVS path exists and it's trying to create the tag file.  The exception is
occuring when the tag file cannot be created.  The weird thing is when I
type in an identical export command (cvs export -r my_tag my_module) from a
cvs client, the /CVS path does not get created in the local path.  So, why
does this API try to create the /CVS path on an export?  Better yet, how do
I stop it from trying?

  java.io.IOException: The file exists.

    boolean java.io.Win32FileSystem.createFileExclusively(java.lang.String)
    boolean java.io.File.createNewFile()

    void
org.netbeans.lib.cvsclient.response.SetStickyResponse.process(org.netbeans.lib.cvsclient.util.LoggedDataInputStream,
 org.netbeans.lib.cvsclient.response.ResponseServices)
    void org.netbeans.lib.cvsclient.Client.handleResponse()
    void org.netbeans.lib.cvsclient.Client.processRequests(java.util.List)
    void
org.netbeans.lib.cvsclient.command.export.ExportCommand.postExpansionExecute(org.netbeans.lib.cvsclient.ClientServices,
 org.netbeans.lib.cvsclient.event.EventManager)
    void
org.netbeans.lib.cvsclient.command.export.ExportCommand.execute(org.netbeans.lib.cvsclient.ClientServices,
 org.netbeans.lib.cvsclient.event.EventManager)
    void
org.netbeans.lib.cvsclient.Client.executeCommand(org.netbeans.lib.cvsclient.command.Command,
 org.netbeans.lib.cvsclient.command.GlobalOptions)
    void cvs_test.cvs_test.<init>()
    void cvs_test.cvs_test.main(java.lang.String[])
  Process exited with exit code 0.