Using fixed versions in examples

Maven release plug-in does not look maven project not included in
parent <module> element. However, we don’t want to include maven
project under examples as sub modules to be deployed to OSSRH staging.
I think there might be a way to skip specific module during deployment.
For now, I update these example pom.xml files to use “fixed” versions,
so we don’t need to worry about SNAPSHOT dependencies.

Author: Yoshito Umaoka

examples/custom-res-filter/csv-filter/pom.xml

@@ -3,7 +3,7 @@
 	<modelVersion>4.0.0</modelVersion>
 	<groupId>com.ibm.g11n.pipeline</groupId>
 	<artifactId>csv-filter</artifactId>
-	<version>1.2.0-SNAPSHOT</version>
+	<version>1.0.0</version>
 	<name>Custom resource filter example - CSV filter</name>
 
 	<properties>
@@ -21,7 +21,7 @@
 		<dependency>
 			<groupId>com.ibm.g11n.pipeline</groupId>
 			<artifactId>gp-res-filter</artifactId>
-			<version>1.2.0-SNAPSHOT</version>
+			<version>1.2.0</version>
 		</dependency>
 		<!-- JUnit -->
 		<dependency>

examples/custom-res-filter/maven/pom.xml

@@ -3,20 +3,20 @@
 	<modelVersion>4.0.0</modelVersion>
 	<groupId>com.ibm.g11n.pipeline</groupId>
 	<artifactId>custom-res-filter-maven</artifactId>
-	<version>1.2.0-SNAPSHOT</version>
+	<version>1.0.0</version>
 	<name>Custom resource filter usage example</name>
 
 	<build>
 		<plugins>
 			<plugin>
 				<groupId>com.ibm.g11n.pipeline</groupId>
 				<artifactId>gp-maven-plugin</artifactId>
-				<version>1.2.0-SNAPSHOT</version>
+				<version>1.2.0</version>
 				<dependencies>
 					<dependency>
 						<groupId>com.ibm.g11n.pipeline</groupId>
 						<artifactId>csv-filter</artifactId>
-						<version>1.2.0-SNAPSHOT</version>
+						<version>1.0.0</version>
 					</dependency>
 				</dependencies>
 				<configuration>