You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org> on 2010/01/19 14:38:55 UTC
[jira] Created: (MRELEASE-513) username part of scpexe URLs is
ignored
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
[jira] Moved: (WAGON-301) username part of scpexe URLs is ignored
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Moved: (MNG-4552) username part of scpexe URLs is ignored
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved WAGON-301 to MNG-4552:
-----------------------------------------
Complexity: Intermediate
Component/s: (was: wagon-ssh-external)
Artifacts and Repositories
Affects Version/s: (was: 1.0-beta-6)
2.2.1
Key: MNG-4552 (was: WAGON-301)
Project: Maven 2 & 3 (was: Maven Wagon)
> username part of scpexe URLs is ignored
> ---------------------------------------
>
> Key: MNG-4552
> URL: http://jira.codehaus.org/browse/MNG-4552
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208010#action_208010 ]
Christoph Lechleitner commented on MRELEASE-513:
------------------------------------------------
As expected that did'nt solve anything.
The previous pom.xml was already patched engough so avoid even a download anything of wagon-ssh-externel before 1.0-beta-3.
I'll try the most recent beta, 1.0-beta-6.
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208011#action_208011 ]
Christoph Lechleitner commented on MRELEASE-513:
------------------------------------------------
wagon-ssh-externel 1.0-beta-6 did'nt fix the problem neither.
Eventually WAGON-153 is'nt fixed after all!?
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208030#action_208030 ]
Christoph Lechleitner commented on MRELEASE-513:
------------------------------------------------
It'd be nice if error messages could contain the version of the code they belong to ;->>
But, as specified in the Issue's environment description ;->> I use maven 2.2.1 as packaged in Ubuntu 9.10.
I also just verified that this Ubuntu did not gamble too much, i.e. the source package absolutely uses wagon 1.0-beta-6.
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-4552) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208574#action_208574 ]
Christoph Lechleitner commented on MNG-4552:
--------------------------------------------
The issue moves are more than alright when it turns out that the initial place incorrect.
The workaround is not too convenient, but good enough, of course.
Thanks for tracking the problem down!
> username part of scpexe URLs is ignored
> ---------------------------------------
>
> Key: MNG-4552
> URL: http://jira.codehaus.org/browse/MNG-4552
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1
> Environment: Ubuntu 9.10 x64, Maven 2.2.1
> Reporter: Christoph Lechleitner
> Fix For: 2.2.2
>
> 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
[jira] Updated: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christoph Lechleitner updated MRELEASE-513:
-------------------------------------------
Attachment: mvn_release_perform.log
mvn_release_prepare.log
Outputs of mvn release:prepare -e -X and mvn release:perform -e -X
> 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_release_perform.log, mvn_release_prepare.log
>
>
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207481#action_207481 ]
Dennis Lundberg commented on MRELEASE-513:
------------------------------------------
The current version is 2.0-beta-9.
Do you have an example project that we use to test this issue?
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ 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://sandbox@maven.clazzes.org/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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207969#action_207969 ]
Christoph Lechleitner commented on MRELEASE-513:
------------------------------------------------
Yes, mvn deploy produces the same error.
Sorry if was blaming the wrong component.
I know that dividing in components and plugins, and usage of libraries give maven much of it's power, but sometimes we end users get lost ...
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MNG-4552) username part of scpexe URLs is ignored
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-4552:
------------------------------
Fix Version/s: 2.2.2
ok, sorry for all the issue moves. This is a Maven issue - the wagon correctly handles the username@ element, and the deployment works in Maven 3.0-alpha-5.
However, in Maven 2.2.x, it appears the authentication configuration is overriding it with the default username.
You can workaround this by adding a <server> element in settings.xml.
We can look if this is an easy fix for 2.2.2, otherwise it's likely to be closed since it already works in 3.0-alpha.
> username part of scpexe URLs is ignored
> ---------------------------------------
>
> Key: MNG-4552
> URL: http://jira.codehaus.org/browse/MNG-4552
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1
> Environment: Ubuntu 9.10 x64, Maven 2.2.1
> Reporter: Christoph Lechleitner
> Fix For: 2.2.2
>
> 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
[jira] Updated: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christoph Lechleitner updated MRELEASE-513:
-------------------------------------------
Attachment: pom.xml.releaseBackup
release.properties
pom.xml
pom.xml and release.properties right after the failed release:perfom run.
> 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_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
[jira] Updated: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christoph Lechleitner updated MRELEASE-513:
-------------------------------------------
Attachment: pom.xml
mvn_deploy.log
mvn_release_perform.log
Logs and pom.xml to previous comment.
> 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
[jira] Updated: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christoph Lechleitner updated MRELEASE-513:
-------------------------------------------
Attachment: mvn_deploy.log
Log of mvn deploy with essentially the same error.
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Christoph Lechleitner (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207488#action_207488 ]
Christoph Lechleitner commented on MRELEASE-513:
------------------------------------------------
I will set up a demo project and upgrade to beta-9 and report back in a few days.
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207970#action_207970 ]
Dennis Lundberg commented on MRELEASE-513:
------------------------------------------
Your build is using 1.0-beta-2 of Wagon.
Try adding this to your POM:
{noformat}
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
<version>1.0-beta-3</version>
</extension>
</extensions>
</build>
{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_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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208028#action_208028 ]
Brett Porter commented on MRELEASE-513:
---------------------------------------
what version of Maven is being used here? The external wagon is bundled in Maven so the version in your repository, or the POMs like Dennis suggested, generally won't be used. The right way to specify an alternative is with a build extension, but that only works in Maven 2.2.0+.
Maven 2.2.1 uses wagon 1.0-beta-6 with the built-in scpexe provider - does that work?
> 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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207965#action_207965 ]
Dennis Lundberg commented on MRELEASE-513:
------------------------------------------
Christoph,
Thanks for the files. After having a look at them, I don't think the root of you problem is in the Release Plugin.
Do you get the same error if you run the command 'mvn deploy'?
> 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_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
[jira] Commented: (MRELEASE-513) username part of scpexe URLs is
ignored
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208031#action_208031 ]
Brett Porter commented on MRELEASE-513:
---------------------------------------
Sorry, I missed that looking between the two issues.
I agree with Dennis that this is not a release plugin problem. I'll take a look and see if I can find the root cause.
> 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