You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2007/12/20 06:11:57 UTC
[jira] Created: (MRELEASE-307) Plugin hangs when scp credentials
are incorrect
Plugin hangs when scp credentials are incorrect
-----------------------------------------------
Key: MRELEASE-307
URL: http://jira.codehaus.org/browse/MRELEASE-307
Project: Maven 2.x Release Plugin
Issue Type: Bug
Reporter: Dan Fabulich
I was trying to follow the New Release Process (which requires staging to an alternate repository). On account of this, I accidentally used an scp url with incorrect credentials; the forked Maven process hung waiting for me to enter credentials on the command line. Unfortunately, there's no visible sign of this on the console of the forking process, and no way to type the answer to any questions; all you can do at that point is Ctrl-C.
The forked Maven should automatically halt if it doesn't have credentials it needs. (For example, are we correctly passing in -B to prevent keyboard authorization?)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MRELEASE-307) Plugin hangs when scp credentials
are incorrect
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-307:
-------------------------------------
Component/s: stage
> Plugin hangs when scp credentials are incorrect
> -----------------------------------------------
>
> Key: MRELEASE-307
> URL: http://jira.codehaus.org/browse/MRELEASE-307
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: stage
> Reporter: Dan Fabulich
>
> I was trying to follow the New Release Process (which requires staging to an alternate repository). On account of this, I accidentally used an scp url with incorrect credentials; the forked Maven process hung waiting for me to enter credentials on the command line. Unfortunately, there's no visible sign of this on the console of the forking process, and no way to type the answer to any questions; all you can do at that point is Ctrl-C.
> The forked Maven should automatically halt if it doesn't have credentials it needs. (For example, are we correctly passing in -B to prevent keyboard authorization?)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-307) Plugin hangs when scp credentials
are incorrect
Posted by "Brian Jackson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118785 ]
Brian Jackson commented on MRELEASE-307:
----------------------------------------
I experience a similar issue where the plugin hangs waiting for the user to accept the ssh fingerprint. So I was required to make it part of our group's training that everyone has to manually do a small site-deploy on any new workstations before attempting a release otherwise they'll experience this hang.
> Plugin hangs when scp credentials are incorrect
> -----------------------------------------------
>
> Key: MRELEASE-307
> URL: http://jira.codehaus.org/browse/MRELEASE-307
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Reporter: Dan Fabulich
>
> I was trying to follow the New Release Process (which requires staging to an alternate repository). On account of this, I accidentally used an scp url with incorrect credentials; the forked Maven process hung waiting for me to enter credentials on the command line. Unfortunately, there's no visible sign of this on the console of the forking process, and no way to type the answer to any questions; all you can do at that point is Ctrl-C.
> The forked Maven should automatically halt if it doesn't have credentials it needs. (For example, are we correctly passing in -B to prevent keyboard authorization?)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira