[
http://jira.codehaus.org/browse/WAGONSSH-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102133
]
Benjamin Bentmann edited comment on WAGONSSH-42 at 7/13/07 2:30 AM:
--------------------------------------------------------------------
"umask 002" really works fine. Great thanks!
One final note about the explicit chmod for the ScpWagon: If this gets
implemented, chmod must not fail the deployment if the currently executing user
is not the file owner. Either chmod is only issued for an initial deployment of
the file or it silently fails if executed on behalf of a foreign user.
Otherwise, we will run into the problem this issue for SftpWagon is already
about.
was:
"umask 002" really works fine. Great thanks!
One final note about the explicit chmod for the ScpWagon: If this gets
implemented, chmod must not fail the deployment if the currently executing user
is not the file owner. Either chmod is only issued for an initial deployment of
the file or it silently fails if executed on behave of a foreign user.
Otherwise, we will run into the problem this issue for SftpWagon is already
about.
> 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
