upgraded version in *.md files to 0.17.0

siom79 · Nov 16, 2022 · dd0a642 · dd0a642
1 parent 4e799a6
commit dd0a642
Show file tree

Hide file tree

Showing 4 changed files with 15 additions and 15 deletions.
diff --git a/README.md b/README.md
@@ -3,7 +3,7 @@ The website is located at [https://siom79.github.io/japicmp](https://siom79.gith
 # japicmp
 japicmp is a tool to compare two versions of a jar archive:
 ``` bash
-java -jar japicmp-0.16.0-jar-with-dependencies.jar -n new-version.jar -o old-version.jar
+java -jar japicmp-0.17.0-jar-with-dependencies.jar -n new-version.jar -o old-version.jar
 ```
 It can also be used as a library:
 ```java
@@ -17,7 +17,7 @@ japicmp is available in the Maven Central Repository:
 <dependency>
 	<groupId>com.github.siom79.japicmp</groupId>
 	<artifactId>japicmp</artifactId>
-	<version>0.16.0</version>
+	<version>0.17.0</version>
 </dependency>
 ```
 A maven plugin allows you to integrate the checks into your build:
@@ -26,7 +26,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.16.0</version>
+	<version>0.17.0</version>
 	<configuration>
 		<oldVersion>
 			<dependency>

diff --git a/src/site/markdown/CliTool.md b/src/site/markdown/CliTool.md
@@ -137,13 +137,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.16.0-jar-with-dependencies.jar -n new-version.jar -o old-version.jar --new-classpath other-library-v2.jar
+    java -jar japicmp-0.17.0-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.16.0-jar-with-dependencies.jar;otherLibrary.jar japicmp.JApiCmp -n new-version.jar -o old-version.jar
+	java -cp japicmp-0.17.0-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.16.0-jar-with-dependencies.jar -o lib1-old.jar;lib2-old.jar -n lib1-new.jar;lib2-new.jar
+	java -jar japicmp-0.17.0-jar-with-dependencies.jar -o lib1-old.jar;lib2-old.jar -n lib1-new.jar;lib2-new.jar
diff --git a/src/site/markdown/MavenPlugin.md b/src/site/markdown/MavenPlugin.md
@@ -10,7 +10,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.16.0</version>
+	<version>0.17.0</version>
 	<configuration>
 		<oldVersion>
 			<dependency>
@@ -46,7 +46,7 @@ You can also leave out the &lt;oldVersion&gt; and &lt;newVersion&gt; elements:
 <plugin>
 	<groupId>com.github.siom79.japicmp</groupId>
 	<artifactId>japicmp-maven-plugin</artifactId>
-	<version>0.16.0</version>
+	<version>0.17.0</version>
 	<configuration>
 		<parameter>
 			<!-- see documentation -->
@@ -70,7 +70,7 @@ to configure the latest version more precisely (e.g. only GA versions), then you
 <plugin>
 	<groupId>com.github.siom79.japicmp</groupId>
 	<artifactId>japicmp-maven-plugin</artifactId>
-	<version>0.16.0</version>
+	<version>0.17.0</version>
 	<configuration>
 		<parameter>
         	<oldVersionPattern>\d+\.\d+\.\d+\.GA</oldVersionPattern>
@@ -115,13 +115,13 @@ An advanced configuration can utilize the following parameters:
 		<plugin>
 			<groupId>com.github.siom79.japicmp</groupId>
 			<artifactId>japicmp-maven-plugin</artifactId>
-			<version>0.16.0</version>
+			<version>0.17.0</version>
 			<configuration>
 				<oldVersion>
 					<dependency>
 						<groupId>japicmp</groupId>
 						<artifactId>japicmp-test-v1</artifactId>
-						<version>0.16.0</version>
+						<version>0.17.0</version>
 						<type>jar</type>
 					</dependency>
 				</oldVersion>
@@ -365,7 +365,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.16.0</version>
+			<version>0.17.0</version>
 			<reportSets>
 				<reportSet>
 					<reports>

diff --git a/src/site/markdown/index.md b/src/site/markdown/index.md
@@ -3,7 +3,7 @@ japicmp
 
 japicmp is a tool to compare two versions of a jar archive:
 
-	java -jar japicmp-0.16.0-jar-with-dependencies.jar -n new-version.jar -o old-version.jar
+	java -jar japicmp-0.17.0-jar-with-dependencies.jar -n new-version.jar -o old-version.jar
 
 It can also be used as a library:
 
@@ -16,7 +16,7 @@ japicmp is available in the Maven Central Repository:
 	<dependency>
 		<groupId>com.github.siom79.japicmp</groupId>
 		<artifactId>japicmp</artifactId>
-		<version>0.16.0</version>
+		<version>0.17.0</version>
 	</dependency>
 
 A maven plugin allows you to integrate the checks into your build:
@@ -25,7 +25,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.16.0</version>
+	<version>0.17.0</version>
 	<configuration>
 		<oldVersion>
 			<dependency>