version increment to 0.7.1

README.md

@@ -2,7 +2,7 @@
 
 japicmp is a tool to compare two versions of a jar archive:
 
-	java -jar japicmp-0.7.0-jar-with-dependencies.jar -n new-version.jar -o old-version.jar
+	java -jar japicmp-0.7.1-jar-with-dependencies.jar -n new-version.jar -o old-version.jar
 
 It can also be used as a library:
 
@@ -15,7 +15,7 @@ japicmp is available in the Maven Central Repository:
 	<dependency>
 		<groupId>com.github.siom79.japicmp</groupId>
 		<artifactId>japicmp</artifactId>
-		<version>0.7.0</version>
+		<version>0.7.1</version>
 	</dependency>
 
 A maven plugin allows you to integrate the checks into your build:
@@ -24,7 +24,7 @@ A maven plugin allows you to integrate the checks into your build:
 <plugin>
 	<groupId>com.github.siom79.japicmp</groupId>
 	<artifactId>japicmp-maven-plugin</artifactId>
-	<version>0.7.0</version>
+	<version>0.7.1</version>
 	<configuration>
 		<oldVersion>
 			<dependency>

src/site/markdown/CliTool.md

@@ -84,13 +84,13 @@ OPTIONS
 When your library implements interfaces or extends classes from other libraries than the JDK and you want to evaluate binary
 compatibility you must specify the classpath for the two different versions:
 
-    java -jar japicmp-0.7.0-jar-with-dependencies.jar -n new-version.jar -o old-version.jar --new-classpath other-library-v2.jar
+    java -jar japicmp-0.7.1-jar-with-dependencies.jar -n new-version.jar -o old-version.jar --new-classpath other-library-v2.jar
         --old-classpath other-library-v1.jar
 
 In case the classpath for both versions did not change, you can add the library using the standard way:
 
-	java -cp japicmp-0.7.0-jar-with-dependencies.jar;otherLibrary.jar japicmp.JApiCmp -n new-version.jar -o old-version.jar
+	java -cp japicmp-0.7.1-jar-with-dependencies.jar;otherLibrary.jar japicmp.JApiCmp -n new-version.jar -o old-version.jar
 
 For reporting purposes you can also provide more than one jar as old or new version(s):
 
-	java -jar japicmp-0.7.0-jar-with-dependencies.jar -o lib1-old.jar;lib2-old.jar -n lib1-new.jar;lib2-new.jar
+	java -jar japicmp-0.7.1-jar-with-dependencies.jar -o lib1-old.jar;lib2-old.jar -n lib1-new.jar;lib2-new.jar

src/site/markdown/MavenPlugin.md

@@ -8,7 +8,7 @@ The maven plugin can be included in the pom.xml file of your artifact in the fol
 <plugin>
 	<groupId>com.github.siom79.japicmp</groupId>
 	<artifactId>japicmp-maven-plugin</artifactId>
-	<version>0.7.0</version>
+	<version>0.7.1</version>
 	<configuration>
 		<oldVersion>
 			<dependency>
@@ -48,13 +48,13 @@ An advanced configuration can utilize the following parameters:
 		<plugin>
 			<groupId>com.github.siom79.japicmp</groupId>
 			<artifactId>japicmp-maven-plugin</artifactId>
-			<version>0.7.0</version>
+			<version>0.7.1</version>
 			<configuration>
 				<oldVersion>
 					<dependency>
 						<groupId>japicmp</groupId>
 						<artifactId>japicmp-test-v1</artifactId>
-						<version>0.7.0</version>
+						<version>0.7.1</version>
 						<type>jar</type>
 					</dependency>
 				</oldVersion>
@@ -193,7 +193,7 @@ Alternatively it can be used inside the `<reporting/>` tag in order to be invoke
 		<plugin>
 			<groupId>com.github.siom79.japicmp</groupId>
 			<artifactId>japicmp-maven-plugin</artifactId>
-			<version>0.7.0</version>
+			<version>0.7.1</version>
 			<reportSets>
 				<reportSet>
 					<reports>

src/site/markdown/ReleaseNotes.md

@@ -6,10 +6,11 @@ The following versions of japicmp are available:
 
 * Exceptions declared in method signatures are now tracked and evaluated regarding source incompatibility. [#110](https://github.com/siom79/japicmp/issues/110)
 * HTML report now names all incompatible changes additional to the markers * and !. [#115](https://github.com/siom79/japicmp/issues/115)
+* Maven plugin has new parameter postAnalysisScript that allows execution of Groovy script after comparison phase. [#120](https://github.com/siom79/japicmp/issues/120)
 * Method added to new interface is no longer detected as source incompatible. [#112](https://github.com/siom79/japicmp/issues/112)
 * Method that overrides in subinterface method from superinterface is no longer detected as source incompatible. [#113](https://github.com/siom79/japicmp/issues/113)
 * Excluded xerces vom maven-reporting dependency in order to prevent warnings from SAXParserImpl. [#109](https://github.com/siom79/japicmp/issues/109)
-* Indirectly implemented interfaces should not be reported as removed. [#119](https://github.com/siom79/japicmp/issues/119)
+* Indirectly implemented interfaces are no longer reported as removed. [#119](https://github.com/siom79/japicmp/issues/119)
 
 Available at [Maven Central](http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22com.github.siom79.japicmp%22%20AND%20v%3A%220.7.1%22).
 

src/site/markdown/index.md

@@ -2,7 +2,7 @@
 
 japicmp is a tool to compare two versions of a jar archive:
 
-	java -jar japicmp-0.7.0-jar-with-dependencies.jar -n new-version.jar -o old-version.jar
+	java -jar japicmp-0.7.1-jar-with-dependencies.jar -n new-version.jar -o old-version.jar
 
 It can also be used as a library:
 
@@ -15,7 +15,7 @@ japicmp is available in the Maven Central Repository:
 	<dependency>
 		<groupId>com.github.siom79.japicmp</groupId>
 		<artifactId>japicmp</artifactId>
-		<version>0.7.0</version>
+		<version>0.7.1</version>
 	</dependency>
 
 A maven plugin allows you to integrate the checks into your build:
@@ -24,7 +24,7 @@ A maven plugin allows you to integrate the checks into your build:
 <plugin>
 	<groupId>com.github.siom79.japicmp</groupId>
 	<artifactId>japicmp-maven-plugin</artifactId>
-	<version>0.7.0</version>
+	<version>0.7.1</version>
 	<configuration>
 		<oldVersion>
 			<dependency>