[
https://issues.apache.org/jira/browse/SCM-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960635#comment-17960635
]
ASF GitHub Bot commented on SCM-165:
------------------------------------
jira-importer commented on issue #441:
URL: https://github.com/apache/maven-scm/issues/441#issuecomment-2964594734
**[Mike
Perham](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mperham)**
commented
This patch fails when running the changelog command in standalone mode. Use
the SCM plugin to run a changelog on some directory "mvn scm:changelog
-DconnectionUrl=XXX" where XXX is your developerConnection string in the POM
and you will find that the command fails due to the clientspec not existing.
This is because your patch assumes it is always run after an update.
Nonetheless, I'm inclined to think this is better than before since
Continuum is the major user of the changelog command and it wasn't working for
Continuum before. I'm assuming that most people don't use the SCM plugin
except for testing.
Emmanuel, do you have any opinion here? Would you rather see the changelog
command only work as part of an update/checkout or not work with those but work
standalone?
> 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)
