getBranchesDiff() fixed, documentation updated

Author: gdy

README.md

@@ -1,74 +1,75 @@
-[![Release](https://jitpack.io/v/ProjectKaiser/pk-vcs-svn.svg)](https://jitpack.io/#ProjectKaiser/pk-vcs-svn)	
-
-# Overview
-Pk-vcs-svn is lightweight library for execute basic SVN VCS operations (merge, branch create etc). It uses [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) exposing IVCS implementation for SVN repositories and [SVNKit](https://svnkit.com/) as framework to work with SVN repositories.
-Features:
-- Branch create and remove
-- Branch merge returning result(success or list of conflicted files)
-- Commit messages list
-- Summarized diff between branches
-- Branches list
-- File content getting and setting
-- File create and remove
-
-# Terms
-- Workspace Home
-  - Home folder of all folders used by vcs-related operations. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
-- Repository Workspace
-  - Folder for LWC folders related to Repository of one type. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
-- Locked Working Copy, LWC
-  - Folder where vcs-related operations are executed. Provides thread- and process-safe repository of working folders. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
-- Test Repository
-  - A SVN repository used for functional testing
-  - Local file system is used, no dedicated server
-  - Creates new before and deletes after each test
-  - Named randomly (uuid is used) 
-
-# Using pk-vcs-svn
-- Add github-hosted pk-vcs-svn and pk-vcs-api projects as maven dependencies using [jitpack.io](https://jitpack.io/). As an example, add following to gradle.build file:
-	```gradle
-	allprojects {
-		repositories {
-			maven { url "https://jitpack.io" }
-		}
-	}
-	
-	dependencies {
-		compile 'com.github.ProjectKaiser:pk-vcs-svn:master-SNAPSHOT'
-		compile 'com.github.ProjectKaiser:pk-vcs-api:master-SNAPSHOT'
-	}
-	```
-- Create Workspace Home instance providing path to any folder as Workspace Home folder path. This folder will contain repositories folders (if different vcs or repositories are used)
-```java
-	public static final String WORKSPACE_DIR = System.getProperty("java.io.tmpdir") + "git-workspaces";
-	...
-	IVCSWorkspace workspace = new VCSWorkspace(WORKSPACE_DIR);
-	...
-```
-- Obtain Repository Workspace from Workspace Home providing a certain Repository's url. The obtained Repository Workspace will represent a folder within Workspace Home dir which will contain all Working Copies relating to the provided VCS Repository  
-```java
-	String repoUrl = "https://github.com/ProjectKaiser/pk-vcs-api";
-	IVCSRepositoryWorkspace repoWorkspace = workspace.getVCSRepositoryWorkspace(repoUrl);
-```
-- Create `SVNVCS` instance providing Repository Workspace, username and password for Repository
-```java
-	IVCS vcs = new SVNVCS(repoWorkspace, username, pass);
-```
-- Use methods of `IVCS` interface. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
-- Use `vcs.setProxy()` and `vcs.setCredentials()` if necessary
-
-# Implementation details
-- [SVNKit](https://svnkit.com/) is used for manage SVN repositories
-- LWC is obtained automatically when necessary
-
-# Functional testing
-- To execute tests just run SVNVCSTest class as JUnit test. Tests from VCSAbstractTest class will be executed. See  [pk-vcs-test](https://github.com/ProjectKaiser/pk-vcs-test) for details
-
-# Limitations
-- According to IVCS description `IVCS.getBranches()` should return list of user-created branches. But a branch and a dir are the same for SVN. So `SVNVCS.getBranches()` returns set of first level folders of "Branches/" branch and "Trunk" branch. I.e.:
-	- Assume we have following directory structure:
-		- Branches/Br1/Folder/file.txt
-		- Branches/Br2/Folder/file.txt
-		- Trunk/Folder/file.txt
-		- Tags/Tag1/
-	- Then `SVNVCS.getBranches()` method will return [Br1, Br2, Trunk]
+[![Release](https://jitpack.io/v/ProjectKaiser/pk-vcs-svn.svg)](https://jitpack.io/#ProjectKaiser/pk-vcs-svn)	
+
+# Overview
+Pk-vcs-svn is lightweight library for execute basic SVN VCS operations (merge, branch create etc). It uses [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) exposing IVCS implementation for SVN repositories and [SVNKit](https://svnkit.com/) as framework to work with SVN repositories.
+Features:
+- Branch create and remove
+- Branch merge returning result(success or list of conflicted files)
+- Commit messages list
+- Summarized diff between branches
+- Branches list
+- File content getting and setting
+- File create and remove
+
+# Terms
+- Workspace Home
+  - Home folder of all folders used by vcs-related operations. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
+- Repository Workspace
+  - Folder for LWC folders related to Repository of one type. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
+- Locked Working Copy, LWC
+  - Folder where vcs-related operations are executed. Provides thread- and process-safe repository of working folders. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
+- Test Repository
+  - A SVN repository used for functional testing
+  - Local file system is used, no dedicated server
+  - Creates new before and deletes after each test
+  - Named randomly (uuid is used) 
+
+# Using pk-vcs-svn
+- Add github-hosted pk-vcs-svn and pk-vcs-api projects as maven dependencies using [jitpack.io](https://jitpack.io/). As an example, add following to gradle.build file:
+	```gradle
+	allprojects {
+		repositories {
+			maven { url "https://jitpack.io" }
+		}
+	}
+	
+	dependencies {
+		compile 'com.github.ProjectKaiser:pk-vcs-svn:master-SNAPSHOT'
+		compile 'com.github.ProjectKaiser:pk-vcs-api:master-SNAPSHOT'
+	}
+	```
+- Create Workspace Home instance providing path to any folder as Workspace Home folder path. This folder will contain repositories folders (if different vcs or repositories are used)
+```java
+	public static final String WORKSPACE_DIR = System.getProperty("java.io.tmpdir") + "git-workspaces";
+	...
+	IVCSWorkspace workspace = new VCSWorkspace(WORKSPACE_DIR);
+	...
+```
+- Obtain Repository Workspace from Workspace Home providing a certain Repository's url. The obtained Repository Workspace will represent a folder within Workspace Home dir which will contain all Working Copies relating to the provided VCS Repository  
+```java
+	String repoUrl = "https://github.com/ProjectKaiser/pk-vcs-api";
+	IVCSRepositoryWorkspace repoWorkspace = workspace.getVCSRepositoryWorkspace(repoUrl);
+```
+- Create `SVNVCS` instance providing Repository Workspace, username and password for Repository
+```java
+	IVCS vcs = new SVNVCS(repoWorkspace, username, pass);
+```
+- Use methods of `IVCS` interface. See [pk-vcs-api](https://github.com/ProjectKaiser/pk-vcs-api) for details
+- Use `vcs.setProxy()` and `vcs.setCredentials()` if necessary
+
+# Implementation details
+- [SVNKit](https://svnkit.com/) is used for manage SVN repositories
+- LWC is obtained automatically when necessary
+
+# Functional testing
+- To execute tests just run SVNVCSTest class as JUnit test. Tests from VCSAbstractTest class will be executed. See  [pk-vcs-test](https://github.com/ProjectKaiser/pk-vcs-test) for details
+- Or run `gradle test`
+
+# Limitations
+- According to IVCS description `IVCS.getBranches()` should return list of user-created branches. But a branch and a dir are the same for SVN. So `SVNVCS.getBranches()` returns set of first level folders of "Branches/" branch and "Trunk" branch. I.e.:
+	- Assume we have following directory structure:
+		- Branches/Br1/Folder/file.txt
+		- Branches/Br2/Folder/file.txt
+		- Trunk/Folder/file.txt
+		- Tags/Tag1/
+	- Then `SVNVCS.getBranches()` method will return [Br1, Br2, Trunk]

src/main/java/com/projectkaiser/scm/vcs/svn/SVNVCS.java

@@ -406,6 +406,7 @@ private VCSChangeType SVNChangeTypeToVCSChangeType(SVNStatusType modificationTyp
 				}
 			}
         });
+		summarizeDiff.run();
 
 		return res;
 	}