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 2016/05/18 21:27:13 UTC
[jira] [Closed] (MANTTASKS-34) It should be possible to specify the
public key for a repository as well as the private key
[ https://issues.apache.org/jira/browse/MANTTASKS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MANTTASKS-34.
-----------------------------------
Resolution: Won't Fix
This component has been retired.
> It should be possible to specify the public key for a repository as well as the private key
> -------------------------------------------------------------------------------------------
>
> Key: MANTTASKS-34
> URL: https://issues.apache.org/jira/browse/MANTTASKS-34
> Project: Maven Ant Tasks
> Issue Type: Improvement
> Reporter: Dan Fabulich
>
> This bug is related to WAGONSSH-19. Right now settings.xml and the repository ant tasks allow you to specify a path to a private key, but not a path to a public key. WAGONSSH-19 suggests a way in which this could be configured using arbitrary <configuration> properties, but that's not as clean as allowing the user to explicitly specify a <publickey> element on the <server> element in settings.xml or as a "publickey" attribute on the <authentication> element in an Ant task.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)