The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Thu, 22 Jul 2004 5:25 AM
Body:
> Before 1.0 jar:deploy used the deploy plugin, that in turn uses external ssh from
> the system.
> Now it uses artifact plugin that uses java implementation of ssh, so neither putty
> nor pageant affect.
Ok so it explains the change.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPARTIFACT-33?page=comments#action_22079
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPARTIFACT-33
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPARTIFACT-33
Summary: deploy need that the passphrase AND the privatekey defined
Type: Bug
Status: Unassigned
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-artifact-plugin
Versions:
1.4
Assignee:
Reporter: Arnaud HERITIER
Created: Wed, 21 Jul 2004 5:00 PM
Updated: Thu, 22 Jul 2004 5:25 AM
Description:
When I want to release a new plugin I need to define both properties :
maven.repo.apache.privatekey
maven.repo.apache.passphrase
If I define only one property, the plugin hang with a different error depending on
whether property is defined.
I'll attach the logs for the 2 cases.
I didn't have this problem (I defined only the private key) when I release the javadoc
plugin just before maven 1.0
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
