[
https://issues.apache.org/jira/browse/SCM-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964363#comment-17964363
]
Olivier Lamy commented on SCM-128:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#408|https://github.com/apache/maven-scm/issues/408].
> Unable to do release:prepare with cvs provider
> ----------------------------------------------
>
> Key: SCM-128
> URL: https://issues.apache.org/jira/browse/SCM-128
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0-beta-3
> Environment: xp, cvs
> Reporter: Dan Tran
> Priority: Blocker
> Fix For: 1.0-beta-3
>
>
> release:prepare throws this error
> [INFO] [release:prepare]
> [INFO] Verifying there are no local modifications ...
> [INFO] Executing: cvs -f -n -q update -d
> [INFO] Working directory: C:\dev\continuum\working-directory\12
> [INFO] Checking lineage for snapshots ...
> [INFO] Checking dependencies for snapshots ...
> [INFO] Checking plugins for snapshots ...
> [INFO] What is the release version for
> "com.borland.optimizeit.win32:agent-win32
> "? [1.0.0-1]
> [INFO] Transforming com.borland.optimizeit.win32:agent-win32 to release
> [INFO] What tag name should be used? [agent-win32-1_0_0-1]
> [INFO] Checking in modified POMs
> Provider message:
> The cvs command failed.
> Command output:
> cvs commit: Server attempted to update a file via an invalid pathname:
> cvs [commit aborted]: `C:/dev/continuum/working-directory/12/pom.xml'.
> Possible problem:
> - cvs does not like full path
> - cvs does not like java path on window
> Note it passes localvalidation step, so the URL is good
> What can i do?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
