[
https://issues.apache.org/jira/browse/SCM-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SCM-477.
------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Public key passphrases when using ext connection method
> -------------------------------------------------------
>
> Key: SCM-477
> URL: https://issues.apache.org/jira/browse/SCM-477
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-cvs
> Affects Versions: 1.3
> Environment: Windows
> Reporter: mattb
>
> When using the ext connection method, and a public key is found by the
> cvsjava implementation, it checks a System property named
> "maven.scm.cvs.java.ssh.passphrase". If this property is not defined, then
> the empty string is used as the passphrase.
> The exception given when attempting to use the public key with an empty
> passphrase (when in reality the passphrase is not empty) is misleading and
> does not really tell the user that the cvsjava library could not determine
> what passphrase to use. In addition, the site documentation does not make any
> mention of the need to set the property "maven.scm.cvs.java.ssh.passphrase".
> In my opinion, a mention in the site provider documentation about this
> property (along with several others used by ExtConnection, such as the
> location of the public key file, which are all undocumented) would go a long
> way towards helping make this plugin/provider easier to use. In addition, the
> exception printed in this scenario could be clearer as well.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
