[ 
http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208032#action_208032
 ] 

Christoph Lechleitner commented on MRELEASE-513:
------------------------------------------------

No problem and thanks.

What look suspicous to me is that, as the sshd log above shows, when trying to 
release:perform maven seems to use the correct user 2 times before finally 
using the wrong user once. I am not sure however if the ssh accesses using the 
correct user come from the scpexe: or the svn+ssh: URL, i.e. from the scm 
developerConnection or the distributionManagement.

> username part of scpexe URLs is ignored
> ---------------------------------------
>
>                 Key: MRELEASE-513
>                 URL: http://jira.codehaus.org/browse/MRELEASE-513
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: perform, scm
>    Affects Versions: 2.0-beta-8
>         Environment: Ubuntu 9.10 x64, Maven 2.2.1
>            Reporter: Christoph Lechleitner
>         Attachments: mvn_deploy.log, mvn_deploy.log, mvn_release_perform.log, 
> mvn_release_perform.log, mvn_release_prepare.log, pom.xml, pom.xml, 
> pom.xml.releaseBackup, release.properties
>
>
> Just like in WAGON-153 some 2 years ago, the current release plugin 
> (2.0-beta-8) ignores the user@ part of scpexe: URLs.
> Per-server settings in ~/.m2/settings.xml are respected.
> But with our (clazzes.org) setup using one unix user per project, granting 
> developer access through those users' ~/.ssh/authorized_keys file, this bug 
> forces us to create a unix account for every releasing developmer and to put 
> that in any project's unix group. This hack becomes impossible once there are 
> 2 different developers using equal user names (on their local development 
> machines).
> We'd appreciate if this bug could be fixed (again).

-- 
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

        

Reply via email to