Make the supported Transports extensible and discoverable

The new TransportProtocol type describes what a particular Transport
implementation wants in order to support a connection.  3rd parties
can now plug into the Transport.open() logic by implementing their
own TransportProtocol and Transport classes, and registering with
Transport.register().

GUI applications can help the user configure a connection by looking
at the supported fields of a particular TransportProtocol type, which
makes the GUI more dynamic and may better support new Transports.

Change-Id: Iafd8e3a6285261412aac6cba8e2c333f8b7b76a5
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>

1 files changed, 8 insertions, 0 deletions

diff --git a/org.eclipse.jgit/resources/org/eclipse/jgit/JGitText.properties b/org.eclipse.jgit/resources/org/eclipse/jgit/JGitText.properties
index f96d4261cc..9fe17fef00 100644
--- a/org.eclipse.jgit/resources/org/eclipse/jgit/JGitText.properties
+++ b/org.eclipse.jgit/resources/org/eclipse/jgit/JGitText.properties
@@ -419,6 +419,14 @@ transportExceptionEmptyRef=Empty ref: {0}
 transportExceptionInvalid=Invalid {0} {1}:{2}
 transportExceptionMissingAssumed=Missing assumed {0}
 transportExceptionReadRef=read {0}
+transportProtoAmazonS3=Amazon S3
+transportProtoBundleFile=Git Bundle File
+transportProtoGitAnon=Anonymous Git
+transportProtoFTP=FTP
+transportProtoHTTP=HTTP
+transportProtoLocal=Local Git Repository
+transportProtoSFTP=SFTP
+transportProtoSSH=SSH
 treeEntryAlreadyExists=Tree entry "{0}" already exists.
 treeIteratorDoesNotSupportRemove=TreeIterator does not support remove()
 truncatedHunkLinesMissingForAncestor=Truncated hunk, at least {0} lines missing for ancestor {1}