[
http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207878#action_207878
]
Christoph Lechleitner commented on MRELEASE-513:
------------------------------------------------
I just set up a sandbox project at
http://svn.clazzes.org/svn/sandbox/trunk/sandbox (read only access, see below
for write access) that definitively uses 2.0-beta-9 of the release plugin, and
the problem still exists.
While pom.xml contains ...
<distributionManagement>
<repository>
<id>org.clazzes</id>
<url>scpexe://[email protected]/var/www/htdocs/maven.clazzes.org</url>
</repository>
</distributionManagement>
... mvn:release still fails because it tries to scp as lech (my local user) as
the server's auth.log shows:
Jan 22 15:09:02 svn sshd[9785]: Accepted publickey for lech from 83.175.125.189
port 39012 ssh2
If anyone wants to do tests:
I actually have created a test user with a password free ssh key that is
included correctly in sandbox' .ssh/authorized_keys (tested with ssh -i), but
I'd prefer if you just mail me your public key so I can introduce it there.
In both cases, just send it to lech at ibcl.at.
Logfiles and so on will follow in a few seconds.
> 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
>
> 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
