| Summary: |
[scp] When creating an "SSH Only" connection, scp should not be selected by default |
| Product: |
[Tools] Target Management
|
Reporter: |
Martin Oberhuber <mober.at+eclipse> |
| Component: |
RSE | Assignee: |
Anna Dushistova <anna.dushistova> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
Martin Oberhuber <mober.at+eclipse> |
| Severity: |
enhancement
|
|
|
| Priority: |
P3
|
CC: |
anna.dushistova, apitigoi, dan, krapfenbauer, lothar, nikita_shulga
|
| Version: |
3.3 | Keywords: |
helpwanted |
| Target Milestone: |
3.3 M4 | |
|
| Hardware: |
All | |
|
| OS: |
All | |
|
| Whiteboard: |
|
| Bug Depends on: |
213438
|
|
|
| Bug Blocks: |
|
|
|
With the new SCP plugin installed, when I create an "SSH Only" connection the scp file subsystem is selected by default. This might be a problem when scp gets mature and integrated into RSE-runtime. Since many existing users of RSE will be used to creating "SSH Only" connections, but for a fact (and because of the conceptual transfer method), the SFTP connection is more reliable than SCP. We need to find a way of integrating scp with the standard RSE-runtime while making sure that we don't break existing adopters. Following ideas might work: (a) just change order of subsystems in the wizard, giving scp lower priority (b) invent a fallback where sftp is tried first, with a fallback to scp when it fails (c) Don't register scp into the "SSH Only" system type by default, but provide a separate and different system type