[
http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208008#action_208008
]
Dennis Lundberg commented on MRELEASE-513:
------------------------------------------
Right, you are on the right track here. However there is one plugin missing
from your POM, and it's that plugin that needs to have its wagon dependency
updated - the Deploy Plugin.
Add this to your original pom.xml. You shouldn't need to add the wagon
dependency to any of the other plugins.
{noformat}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<dependencies>
<dependency>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
<version>1.0-beta-3</version>
</dependency>
</dependencies>
</plugin>
{noformat}
> 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
