[
https://issues.apache.org/jira/browse/SCM-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960638#comment-17960638
]
ASF GitHub Bot commented on SCM-165:
------------------------------------
jira-importer commented on issue #441:
URL: https://github.com/apache/maven-scm/issues/441#issuecomment-2964594751
**[Mike
Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)**
commented
Here's my understanding of the requirements:
1) Continuum needs to be able to run update/checkout and changelog in the
same VM when running a build. Since this uses a persistent clientspec, the
changelog command needs to reuse the same clientspec. That's what this bug is
about and it should work with my changes 3 days ago.
2) The changelog mojo needs to be able to run the changelog command as a
standalone feature. The command should default to NO clientspec but allow the
user to pass in a clientspec on the command line.
3) The user should be able to run 'mvn scm:update scm:changelog' to get
results similar to (1) and 'mvn scm:changelog' to get results similar to (2).
Any comments? Any other usecases?
> 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)
