You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scm-dev@maven.apache.org by "John Didion (JIRA)" <ji...@codehaus.org> on 2006/02/23 04:22:37 UTC
[jira] Created: (SCM-164) PerforceUpdateCommand fails with NPE
PerforceUpdateCommand fails with NPE
------------------------------------
Key: SCM-164
URL: http://jira.codehaus.org/browse/SCM-164
Project: Maven SCM
Type: Bug
Components: maven-scm-provider-perforce
Versions: 1.0-beta-3
Reporter: John Didion
Priority: Critical
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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (SCM-164) PerforceUpdateCommand fails with NPE
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-164?page=all ]
Mike Perham reassigned SCM-164:
-------------------------------
Assign To: Mike Perham
> PerforceUpdateCommand fails with NPE
> ------------------------------------
>
> Key: SCM-164
> URL: http://jira.codehaus.org/browse/SCM-164
> Project: Maven SCM
> Type: Bug
> Components: maven-scm-provider-perforce
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (SCM-164) PerforceUpdateCommand fails with NPE
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/SCM-164?page=all ]
Mike Perham resolved SCM-164:
-----------------------------
Resolution: Fixed
Fix Version: 1.0-beta-3
> PerforceUpdateCommand fails with NPE
> ------------------------------------
>
> Key: SCM-164
> URL: http://jira.codehaus.org/browse/SCM-164
> Project: Maven SCM
> Type: Bug
> Components: maven-scm-provider-perforce
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira