[
http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207974#action_207974
]
Christoph Lechleitner commented on MRELEASE-513:
------------------------------------------------
I apologize for not having realized that the fix for WAGON-153 just has not
"reached" maven's deploy and release components, and for eventually creating
what might be a duplicate.
If it was only that we'd easily wait for it, but there still might be more to
it:
After adding the wagon-ssh-external 1.0-beta-3 mvn downloaded it, but did'nt
seem to use it.
So I deleted any wagon-ssh-external stuff from my ~/.m2/repository and added
wagon-ssh-external 1.0-beta-3 as dependency to all plugins in the pom.xml's
<build> section, and finally mvn downloaded and used 1.0-beta-3.
Unfortunately mvn release ...
Jan 23 13:57:52 svn sshd[7375]: Accepted publickey for sandbox from
212.186.17.126 port 48999 ssh2
Jan 23 13:57:52 svn sshd[7381]: Accepted publickey for sandbox from
212.186.17.126 port 49000 ssh2
Jan 23 13:57:58 svn sshd[7391]: Accepted publickey for lech from 212.186.17.126
port 49001 ssh2
... and mvn deploy ...
Jan 23 13:59:48 svn sshd[7455]: Accepted publickey for lech from 212.186.17.126
port 58547 ssh2
Jan 23 13:59:49 svn sshd[7460]: Accepted publickey for lech from 212.186.17.126
port 58548 ssh2
... still ignore the sandbox@ part of the scpexe URL.
Current pom.xml and logs follow.
> 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_release_perform.log,
> mvn_release_prepare.log, 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
