[
https://issues.apache.org/jira/browse/SCM-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964488#comment-17964488
]
Olivier Lamy commented on SCM-323:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#535|https://github.com/apache/maven-scm/issues/535].
> generateReleasePoms fails after first release:prepare
> -----------------------------------------------------
>
> Key: SCM-323
> URL: https://issues.apache.org/jira/browse/SCM-323
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0
> Reporter: Patrick Schneider
> Assignee: Patrick Schneider
> Priority: Major
> Fix For: 1.1
>
>
> See line 38 of PerforceAddConsumer.
> The regexp assumes a "#1" is appended to depot location when adding a file.
> This is only true for files that have never been in the depot before. When
> using generateReleasePoms, the release-pom.xml gets committed and then
> deleted during release:prepare. Upon subsequent prepares, the revision
> number will not be "#1".
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
