[
http://jira.codehaus.org/browse/WAGON-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter moved MRELEASE-513 to WAGON-301:
---------------------------------------------
Component/s: (was: perform)
(was: scm)
wagon-ssh-external
Affects Version/s: (was: 2.0-beta-8)
1.0-beta-6
Key: WAGON-301 (was: MRELEASE-513)
Project: Maven Wagon (was: Maven 2.x Release Plugin)
> username part of scpexe URLs is ignored
> ---------------------------------------
>
> Key: WAGON-301
> URL: http://jira.codehaus.org/browse/WAGON-301
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh-external
> Affects Versions: 1.0-beta-6
> 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
