Community
Participate
Working Groups
Build ID: I20080617-2000 Steps To Reproduce: 1. Log in to a server with an account that does not have SSH access. 2. Attempt to copy a file from one location on the server to another. 3. Progress dialog is displayed, etc., but the file is not copied, and there are no error messages displayed/logged. More information: Newsgroup link: http://www.eclipse.org/newsportal/article.php?id=449&group=eclipse.dsdp.tm As explained by Martin, SFTP doesn't support remote file copying, and therefore falls back to an SSH 'cp' command. As suggested by Martin, if no SSH access is permitted, RSE could download the file and then upload it to the target directory (using SFTP). At a minimum, an error message should be displayed explaining what the problem is, or the 'Paste' context menu item on remote folders could be disabled if the clipboard held a reference to a remote file (though I prefer Martin's suggestion).
Updated summary, previous value was: SFTP remote copy falls back to SSH – SSH access not enabled on account
We should catch the exception and file a proper error message at the least. The error should tell users to manually download / upload the resources. A better solution would be to fall back to automatic download / upload like the EFS provider does.
Note that the FTPService also provides an implementation of recursive-copy and recursive-delete, which could be used here. We should consider putting this algorithm into the FileServiceSubSystem such that it can be re-used if needed - a simpler implementation could just copy the algorithm into SftpFileService. In the FileServiceSubSystem, we could catch something like UnsupportedOperationException in case of copying / deleting a non-empty folder, in order to trigger the algorithm. In either case, the service should cache the fact that remote ssh shell is not available, and directly trigger the alternative algorithms if needed. In some cases, it could also be a user preference (see also bug 155189). We'd appreciate if somebody in the Community would want to take a look at this.
Bulk update of target milestones to 3.2
Bulk moving 3.3 deferred items to 3.3.1
