You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2007/07/12 21:58:13 UTC
[jira] Commented: (WAGONSSH-42) Cannot deploy files over existing
files if someone else originally uploaded them.
[ http://jira.codehaus.org/browse/WAGONSSH-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102098 ]
Benjamin Bentmann commented on WAGONSSH-42:
-------------------------------------------
I ran into this problem today and would like to clarify the cause for it. Maven's SftpWagon tries to set the file permissions after file upload, i.e. it issues a chmod on the file (see your stack trace). However, changing file permissions is only allowed to the file owner. Users having full file access (777) may change the file contents but only the owner may change its permissions.
For the moment, we simple use "scp" as the protocol rather than "sftp". The ScpWagen seems to successfully deploy regardless which user currently owns the file in the repo. Unfortunately, the ScpWagen seems to struggle with file permissions. It does not grant write permission to the group. I'm still invastigating why it does not honor the <filePermissions>664</filePermission> element in the settings.xml. For now, we manully grant write permissions after an initial deploy. Later on, the ScpWagen seems not to change the permissions.
> Cannot deploy files over existing files if someone else originally uploaded them.
> ---------------------------------------------------------------------------------
>
> Key: WAGONSSH-42
> URL: http://jira.codehaus.org/browse/WAGONSSH-42
> Project: wagon-ssh
> Issue Type: Bug
> Affects Versions: 1.0-alpha-6
> Environment: Desktop OS is Windows XP. Deploying to Solaris server using Tectia SSH2 Client.
> Reporter: Frank Russo
> Priority: Critical
> Attachments: File sharing issue with maven-deploy using wagon.txt
>
>
> On first deploy, everything works fine. On next deploy, if a different developer runs the command, the attached error occurs(see attached the original email posted to the Maven Users Mailing List.)
> The file is owned by the first developer, but has full rwx access (777). If developer 2 directly connects to the machine, they can do anything to the file, so it's not a Unix permissions issue...
--
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