[
http://jira.codehaus.org/browse/SCM-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Janes updated SCM-415:
----------------------------
Attachment: scm-415.patch
Alternative patch that logs an info message when no password is set and
attempts to continue. This also allows for ticket-based login using Perforce's
cache.
> 1.1 requires setting a Perforce password breaking Perforce setup for external
> authentication
> --------------------------------------------------------------------------------------------
>
> Key: SCM-415
> URL: http://jira.codehaus.org/browse/SCM-415
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-perforce
> Affects Versions: 1.1
> Reporter: ajbanck
> Priority: Blocker
> Attachments: perforce_login.patch, scm-415.patch
>
>
> checkin r654744 for SCM-363 introduces a requirement to set a Perforce
> password.
> This will break the SCM provider when Perforce is configured to not accept a
> password. This will be the case when using the OS security instead of
> Perforce' own.
> The SCM pluging throws an exception when not providing a password, Perforce
> throws an error when trying to login with a (dummy) password.
> When no username and/or password is provided, the Perforce login step should
> be skipped.
> =========
> Perforce login output when running p4 from the command prompt:
> p4 login
> 'login' not necessary, no password set for this user.
> p4 login john
> You don't have permission for this operation.
> =========
> Offending code:
> PerforceLoginCommand.java
> if ( StringUtils.isEmpty( repo.getPassword() ) )
> {
> throw new ScmException( "password is required for the
> perforce scm plugin." );
> }
--
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
