[
http://jira.codehaus.org/browse/WAGON-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136570#action_136570
]
Benjamin Bentmann commented on WAGON-171:
-----------------------------------------
I assume a scenario where all developers of the project have the permissions
configured in their {{settings.xml}} (e.g. because people don't like updating
their umask which would affect their entire account and not just Maven
deployments). This in turn will make Wagon *always* try to set permissions, not
just on first deployment, wouldn't it? In this case, any deployment by somebody
other than the file owner will fail, because the {{SftpWagon}} is emitting a
chmod on the command channel in line 178. It doesn't matter if the permissions
were previously set to 777 or something else granting write permissions to the
group, only the file owner is allowed to issue chmod on the files. Hence I
would have expected {{SftpWagon.setFileMode()}} to guard against an exception
of the failed chmod and simply continue deployment. Do I miss something here?
> Cannot deploy files over existing files if someone else originally uploaded
> them.
> ---------------------------------------------------------------------------------
>
> Key: WAGON-171
> URL: http://jira.codehaus.org/browse/WAGON-171
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-ssh
> Environment: Desktop OS is Windows XP. Deploying to Solaris server
> using Tectia SSH2 Client.
> Reporter: Frank Russo
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.0-beta-3
>
> 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
