Reset user and password fields when credentialsprovider is reset

If authentication fails due to wrong credentials we need to ask the
user to correct the credentials. Clearing only the SecureStore entry
isn't sufficient. We have to clear also the user and password fields.

JGit-Dependency: I6fa726a14a84b06411e7010608c7a1e2bfb8bfe8
Bug: 430210
Change-Id: I5f029e38fcb3ab0a58baced5d95056b72d810f0a
Init credentials from secure store on first page of clone wizard

This way the user can recognize that there are credentials available in
the secure store for the URL he entered. Also this simplifies retry
handling in jgit if authentication failed either since credentials
changed or the user mistyped the credentials.

Change-Id: I9f61f8897d45b37ce4dae648878d835330879f79
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
Always configure credentials provider for remote operations

This ensures that credentials are requested from the user or loaded from
the secure store if the remote repository requires authentication for a
remote operation.

Bug: 338048
Bug: 339220
Bug: 342592
Bug: 427735
Change-Id: I8cbea42368d20657615b1b847e215eeb70290628
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
EGit v3.3.1.201403241930-r

Change-Id: Ie948cc2b677f84e5f7672a3c1074ad5fa8b7807b
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
Prepare 3.3.2-SNAPSHOT builds

Change-Id: I898b9923d1aa2f935c9d4401a778db379ce739fe
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
Merge branch 'stable-3.3'

* stable-3.3:
  Prepare 3.3.2-SNAPSHOT builds
  EGit v3.3.1.201403241930-r
  Always configure credentials provider for remote operations
  Init credentials from secure store on first page of clone wizard
  Reset user and password fields when credentialsprovider is reset

Change-Id: Ibf9d23e7c23f3d550d4f935c9e5bb2511b5613fb
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
[historyView] Prevent NPE for non-workspace comparisons

Using the actions "Compare with Version in Ancestor" and "Compare with
Workspace" in the history view for files resulted in a
NullPointerException, if the selected file was not in an imported
Eclipse project. In this case a null RepositoryMapping
was used to find the repo-relative path of the file to compare,
resulting in a NPE.

If no RepositoryMapping is available, use the repository we get as an
argument anyway, to get the repo-relative path.

Bug: 424585
Change-Id: I7b58b15f879b4f5d2b704faec87f05864a677199
Signed-off-by: Konrad Kügler <swamblumat-eclipsebugs@yahoo.de>
Include Java7 feature fragment when executing EGit tests

See [1] for details about adding fragment to Tycho test classpath.

[1] http://bit.ly/1lne3w9

Change-Id: I92a8fe5abb1eb111f0bd5ab4c9e0f1ec41ac97ca
Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
Merge Tool: Don't ask for merge mode per default

Display the initial state of the file on the left hand side of the merge 
tool per default. This simplifies user experience.

Bug: 431127
Change-Id: I38613c8a2bba0e1f248e7e8940d31ed77f0a09ac
Signed-off-by: Stefan Lay <stefan.lay@sap.com>
Add ability to edit a commit directly from the history view.

This adds a new menu item Modify > Edit to the context menu of the
history view. It can be used to edit a commit, then manually amending
the commit afterwards.

An error will be displayed if the selected commit cannot be reached
from the current HEAD commit. This is done so as to avoid the need
to checkout another commit automatically before executing the edit
procedure.

Change-Id: Idef404f2d712cccb862a7eb11571a7a4151badb8
Signed-off-by: Maik Schreiber <blizzy@blizzy.de>