Hello, I'm trying to perform a 'mvn release:prepare' on our SCM (CVS 1.11.17) and I get the following error:
[INFO] Checking in modified POMs... [INFO] Executing: cvs -z3 -f -d :ext:[EMAIL PROTECTED]:/cvs/yyy -q commit -R -F D:\DOCUME~1\xxx\LOCALS~1\Temp\scm-commit-message59827.txt pom.xml [INFO] Working directory: D:\workspace\project_path [INFO] Tagging release with the label project_path-1_0... [INFO] Executing: cvs -z3 -f -d :ext:[EMAIL PROTECTED]:/cvs/yyy -q tag -F -c project_path-1_0 [INFO] Working directory: D:\workspace\project_path [WARNING] Unknown status: '? '. [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Unable to tag SCM Provider message: The cvs tag command failed. Command output: cvs tag: failed to create lock directory for `/cvs/yyy/project_path/src ' (/cvs/yyy/project_path/src /#cvs.lock): No such file or directory cvs tag: failed to obtain dir lock in repository `/cvs/yyy/project_path/src ' cvs [tag aborted]: read lock failed - giving up [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 20 seconds [INFO] Finished at: Mon Oct 09 16:27:40 CEST 2006 [INFO] Final Memory: 6M/10M [INFO] ------------------------------------------------------------------------ The problem may be around a carriage/return at the end of the directory name and before the /#cvs.lock filename. I actually found a workaround by removing the trailing blank line at the end of the CVS/Repository file in the project root, but it now appears that I would have to do the same thing for all the subfolders of all my projects (developped under the latest Eclipse 3.2.1/WTP1.5.1). However, changing all those files that are supposed to be managed by Eclipse does not suit me so much... Did anyone have the same problem ? Could the release-plugin manage to escape the empty line ? Thank you in advance Xavier
