[
http://jira.codehaus.org/browse/SCM-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Venisse closed SCM-277.
--------------------------------
Assignee: Emmanuel Venisse
Resolution: Fixed
Fix Version/s: 1.0
> CVS Provider should support SSPI transport
> ------------------------------------------
>
> Key: SCM-277
> URL: http://jira.codehaus.org/browse/SCM-277
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-cvs
> Environment: Windows XP Pro, CVSNT 2.0.51d, Maven 2.0.4
> Reporter: Daniel Siegmann
> Assigned To: Emmanuel Venisse
> Fix For: 1.0
>
> Attachments: AbstractCvsScmProvider.java.patch
>
>
> The CVS provider should support connections via the SSPI protocol (for
> Windows domain authentication). Though this is not supported by CVS, it is
> supported by CVSNT (which is a superset of CVS, and is open source).
> The SCM connection should should be specified as:
> {{scm:cvs:sspi:host:path:module}}
> I have implemented this functionality. The only changes are in
> AbstractCvsScmProvider.java, for which I have attached a patch. The changes
> are hopefully easy to understand. The only limitation I have noticed in my
> implementation is that CvsScmProviderRepository cannot be created with a null
> user. So I have passed in "" for the user. This results in an additional '@'
> symbol prefixing the host which should not be present, but this has not
> caused any errors in my tests.
> I have not provided any unit tests, since there are no unit tests for the
> other transports. I have simply done some testing on my local system. I was
> able to successfully use both scm:update and scm:checkin.
> I did have one error when using scm:checkin. This command failed due to the
> property connectionUrl not being defined. This property should retrieve its
> value from the SCM connection defined in the POM. When I explicitly defined
> this property on the command line, scm:checkin completed successfully. I do
> not know whether this is related to the work I have done, but I assume this
> is handled elsewhere. Please let me know if I should file a separate bug
> report.
> Note that this functionality will require that the CVS executable (cvs.exe)
> which is present on the path be provided by CVSNT.
--
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
