You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2022/07/12 08:33:00 UTC
[jira] [Comment Edited] (SCM-992) Support explicitly configured private key & passphrase for gitexe
[ https://issues.apache.org/jira/browse/SCM-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17565358#comment-17565358 ]
Konrad Windszus edited comment on SCM-992 at 7/12/22 8:32 AM:
--------------------------------------------------------------
Yes, the {{GIT_SSH_COMMAND}} approach is already leveraged in https://github.com/apache/maven-scm/pull/153 for testing SSH authentication. It is supported since git 2.3.0.
was (Author: kwin):
Yes, this approach is already leveraged in https://github.com/apache/maven-scm/pull/153 for testing SSH authentication.
> Support explicitly configured private key & passphrase for gitexe
> -----------------------------------------------------------------
>
> 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
> Priority: Major
>
> 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)