[
https://issues.apache.org/jira/browse/SCM-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960629#comment-17960629
]
ASF GitHub Bot commented on SCM-165:
------------------------------------
jira-importer opened a new issue, #441:
URL: https://github.com/apache/maven-scm/issues/441
**[John
Didion](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jdidion)**
opened
**[SCM-165](https://issues.apache.org/jira/browse/SCM-165?redirect=false)** and
commented
The PerforceChangeLogCommand as written does not work if the update was done
with the client spec generated by the checkout/update command. The attached
diff will fix the problem.
---
**Affects:** 1.0-beta-3
**Attachments:**
-
[PerforceChangeLogCommand.diff](https://issues.apache.org/jira/secure/attachment/12718644/PerforceChangeLogCommand.diff)
(_1.61 kB_)
-
[svn.diff](https://issues.apache.org/jira/secure/attachment/12718491/svn.diff)
(_3.66 kB_)
1 votes, 1 watchers
> PerforceChangeLogCommand needs to use the same clientspec as the update
> command
> -------------------------------------------------------------------------------
>
> Key: SCM-165
> URL: https://issues.apache.org/jira/browse/SCM-165
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.0-beta-3
> Reporter: John Didion
> Assignee: Mike Perham
> Priority: Critical
> Fix For: 1.0-beta-4
>
> Attachments: PerforceChangeLogCommand.diff, svn.diff
>
>
> The PerforceChangeLogCommand as written does not work if the update was done
> with the client spec generated by the checkout/update command. The attached
> diff will fix the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
