You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/07/28 17:54:00 UTC

[jira] [Closed] (SCM-992) Support explicitly configured SSH private key for gitexe provider

     [ https://issues.apache.org/jira/browse/SCM-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed SCM-992.
------------------------------
    Resolution: Fixed

Fixed with [e77e0017971857158d1c4358f5ae66a22ef848f8|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=e77e0017971857158d1c4358f5ae66a22ef848f8].

> Support explicitly configured SSH private key for gitexe provider
> -----------------------------------------------------------------
>
>                 Key: SCM-992
>                 URL: https://issues.apache.org/jira/browse/SCM-992
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-provider-gitexe
>            Reporter: Konrad Windszus
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 2.0.0-M2
>
>
> Currently the {{privateKey}} parameter set on {{ScmProviderRepositoryWithHost}} is only evaluated in provider "jgit". It should also be used for provider "git". Same for {{passphrase}} parameter.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)