FetchCommand: do not set a null credentials provider

FetchCommand now does not set a null credentials provider on
Transport because in this case the default provider is replaced with
null and the default mechanism for providing credentials is not
working.

Change-Id: I44096aa856f031545df39d4b09af198caa2c21f6
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>

diff --git a/org.eclipse.jgit/src/org/eclipse/jgit/api/FetchCommand.java b/org.eclipse.jgit/src/org/eclipse/jgit/api/FetchCommand.java
index 28c2d15ff63932a3ab944585220e6250409a252d..9594dfebe7def7be192f220f7f6dede2001b5d70 100644 (file)
--- a/org.eclipse.jgit/src/org/eclipse/jgit/api/FetchCommand.java
+++ b/org.eclipse.jgit/src/org/eclipse/jgit/api/FetchCommand.java
@@ -128,7 +128,8 @@ public class FetchCommand extends GitCommand<FetchResult> {
                        if (tagOption != null)
                                transport.setTagOpt(tagOption);
                        transport.setFetchThin(thin);
-                       transport.setCredentialsProvider(credentialsProvider);
+                       if (credentialsProvider != null)
+                               transport.setCredentialsProvider(credentialsProvider);
 
                        try {
                                FetchResult result = transport.fetch(monitor, refSpecs);