[
http://jira.codehaus.org/browse/WAGONSSH-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102132
]
Benjamin Bentmann commented on WAGONSSH-42:
-------------------------------------------
Thanks for your advice about using "umask", I will try this at the next
occasion.
As for the ScpWagon, I recently discovered the related discussion at
http://jira.codehaus.org/browse/WAGONSSH-44. If the world of SSH server
implementations is indeed so evil that there is no standard/reliable way of
setting the file permissions, I would appreciate a configuration setting for
the ScpWagon to enforce the (otherwise costly) usage of chmod. After all, a
long but successful deploy is still better than a quick but improper deploy.
> 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
