[
https://issues.apache.org/jira/browse/SCM-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960637#comment-17960637
]
ASF GitHub Bot commented on SCM-165:
------------------------------------
jira-importer commented on issue #441:
URL: https://github.com/apache/maven-scm/issues/441#issuecomment-2964594753
**[Mike
Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)**
commented
Posted a release candidate with my small changes to allow these usecases.
I'm still afraid there will be edge cases I've missed - Emmanuel, can you point
me to the changelog plugin and the documentation on how to use it so I can
test it here?
> 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)
