Exception in deploy-file when uploading artifact with different owner for maven-metadata.xml --------------------------------------------------------------------------------------------
We have a case with several persons uploading to an internal repository (for our closed-source dependencies). Each person uses a his own user account for uploading, and a common group for all files. So we have a situation where artifact com.agroup:anartifact was first uploaded in version 2.0 by a user, and when another user tries to upload version 2.5 we get a LifecycleExecutionException with the message "Error while deploying metadata" (full stack trace provided below).
It seems this happens because the SSH provider tries to chown a file created by a different user. All the files are writable by group, so there should be no need for the chmod. The best work-around we have found so far is that a server administrator has to chown maven-metadata.xml* to the user that will do the upload.
-- 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
