Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342860 - Provide a programmatic way to enforce use of an external ssh executable
Summary: Provide a programmatic way to enforce use of an external ssh executable
Status: NEW
Alias: None
Product: JGit
Classification: Technology
Component: JGit (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-14 11:43 EDT by Benjamin Bentmann CLA
Modified: 2011-04-19 07:40 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Bentmann CLA 2011-04-14 11:43:31 EDT 
Regarding this code snippet from TransportGitSsh

  private static boolean useExtConnection() {
    return SystemReader.getInstance().getenv("GIT_SSH") != null;
  }

It would be nice if there was a way to enforce use of some ssh executable from within the already running JVM. Right now, this requires to install a new SystemReader which overlays the desired GIT_SSH value and otherwise delegates to the original SystemReader.