[
https://issues.apache.org/jira/browse/SCM-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964311#comment-17964311
]
Olivier Lamy commented on SCM-164:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#406|https://github.com/apache/maven-scm/issues/406].
> PerforceUpdateCommand fails with NPE
> ------------------------------------
>
> Key: SCM-164
> URL: https://issues.apache.org/jira/browse/SCM-164
> 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-3
>
>
> This has been hidden by the but I reported in SCM-163. Once that bug is
> fixed, the perforce update command fails with an NPE if there are updated
> files. This is because the logger is not set on the ChangeLogCommand. Apply
> the following change to PerforceUpdateCommand.getChangeLogCommand():
> {noformat}
> PerforceChangeLogCommand command = new PerforceChangeLogCommand();
> command.setLogger(getLogger());
> return command;
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
