Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
We have CVSNT 1.11.53 and Maven 2.0.7. The Maven SCM Plugin has a CVS module, but it relies on the .cvspass file to have a cached password for each repository. That .cvspass file is expected to be in the home directory (docs and settings/myuser1/.cvspass) but all CVSNT clients store their passwords in the registry or proprietary files. If we could run the "cvs login" command using a cvs executable, that would create the .cvspass file for Maven to use. However, both Maven and CVS expect a forward slash after the repository URL, and the CVSNT server path is "c:\cvsrepo\", which doesn't start with a forward slash. Both CVS and Maven throw up an exception about an incorrect connection string when the c: begins the path instead of a standard forward-slash Unix path. That keeps us from generating the .cvspass file and would stop Maven from being able to connect as well. We seem to require a workaround that forces CVSNT to interpret a path starting with a forward slash instead of c:\. Chris Terenzi Disclaimer for DataPath This electronic message, together with any attachments, is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is privileged or confidential and is the intellectual property of the sender. If you are not the named addressee, you are expressly prohibited from reading, printing, retaining, copying, distributing or disseminating this message or any part of it or any attachments or any information contained therein. Doing so may be actionable under state or federal laws. If you have received this message in error, please notify the sender immediately either by phone (866-855-3800) or reply to this e-mail and immediately delete all copies of this message and any attachments. All electronic messages and attachments sent and received are subject to monitoring, reading and archival by DataPath. The recipient of this electronic message is responsible for ensuring that it and any attachments are free from "viruses" or other software or defects that may affect any computer system into which it is received or opened. DataPath accepts no responsibility for any damage that may arise from the receipt or use of this electronic message or any attachments.