[
http://jira.codehaus.org/browse/WAGONSSH-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102123
]
Trustin Lee commented on WAGONSSH-42:
-------------------------------------
ScpWagon correctly specified the file permission but most OpenSSH servers
doesn't seem to respect it. I'm not sure if it's an OpenSSH bug or ScpWagon is
using some non-standard way to set permissions.
This issue can be fixed by modifying ScpWagon to run chmod command explicitly,
but it will make the deployment time much longer.
Instead, this issue can be worked around by changing the default umask of the
user. Please try to add 'umask 002' to your .shrc or .bashrc file.
> 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
