[
https://issues.apache.org/jira/browse/SCM-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960249#comment-17960249
]
ASF GitHub Bot commented on SCM-94:
-----------------------------------
jira-importer opened a new issue, #358:
URL: https://github.com/apache/maven-scm/issues/358
**[Mike
Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)**
opened
**[SCM-94](https://issues.apache.org/jira/browse/SCM-94?redirect=false)** and
commented
Small patch to fix the case where the same clientspec is used as the last
release. Perforce returns a slightly different message which the consumer did
not recognize.
Recursive release:prepare and release:perform are now working!
---
**Affects:** 1.0-beta-2
**Attachments:**
-
[checkout.txt](https://issues.apache.org/jira/secure/attachment/12718731/checkout.txt)
(_883 bytes_)
> Checkout does not handle case where clientspec is unchanged
> -----------------------------------------------------------
>
> Key: SCM-94
> URL: https://issues.apache.org/jira/browse/SCM-94
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-2
> Reporter: Mike Perham
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-beta-2
>
> Attachments: checkout.txt
>
>
> Small patch to fix the case where the same clientspec is used as the last
> release. Perforce returns a slightly different message which the consumer
> did not recognize.
> Recursive release:prepare and release:perform are now working!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
