Update READMEs to reflect semantic versioning in JAR file paths

README.md

@@ -98,28 +98,28 @@ This will create the `target` folder under each module. From here, create a new
 ```
 .
 ├── cv-data-controller
-│   ├── cv-data-controller-x.x.x.jar
+│   ├── cv-data-controller-x.y.z.jar
 │   ├── Dockerfile
 ├── cv-data-tasks
-│   ├── cv-data-tasks-x.x.x.jar
+│   ├── cv-data-tasks-x.y.z.jar
 │   ├── Dockerfile
 ├── docker-compose.yml
 ├── ode-data-logger
 │   ├── Dockerfile
-│   ├── ode-data-logger-x.x.x.jar
+│   ├── ode-data-logger-x.y.z.jar
 ├── ode-mongo-logger
 │   ├── Dockerfile
-│   ├── ode-mongo-logger-x.x.x.jar
+│   ├── ode-mongo-logger-x.y.z.jar
 ├── ode-wrapper
 │   ├── Dockerfile
-│   ├── ode-wrapper-x.x.x.jar
+│   ├── ode-wrapper-x.y.z.jar
 ├── ode-wrapper-docs
 │   └── swagger-ui-master
 │       ├── Dockerfile
 │       ├── (swagger folder structure)
 └── tim-refresh
     ├── Dockerfile   
-    ├── tim-refresh-x.x.x.jar
+    ├── tim-refresh-x.y.z.jar
 
 ```
 

cert-expiration/README.md

@@ -27,14 +27,14 @@ The following instructions are intended to be executed from the root directory o
 
     Linux:
     ```bash
-    mv ./cert-expiration/target/cert-expiration-x.x.x-SNAPSHOT.jar ./cert-expiration/
+    mv ./cert-expiration/target/cert-expiration-x.y.z-SNAPSHOT.jar ./cert-expiration/
     ``` 
     Windows:
     ```windows
-    move .\cert-expiration\target\cert-expiration-x.x.x-SNAPSHOT.jar .\cert-expiration\
+    move .\cert-expiration\target\cert-expiration-x.y.z-SNAPSHOT.jar .\cert-expiration\
     ```
 
-    Replace `x.x.x` with the version number of the JAR file. If a JAR file already exists in the `cert-expiration` directory, you may need to delete it first.
+    Replace `x.y.z` with the version number of the JAR file. If a JAR file already exists in the `cert-expiration` directory, you may need to delete it first.
 
 1. Copy the sample.env to .env:
 

cv-data-controller/README.md

@@ -27,14 +27,14 @@ The following instructions are intended to be executed from the root directory o
 
     Linux:
     ```bash
-    mv ./cv-data-controller/target/cv-data-controller-x.x.x-SNAPSHOT.jar ./cv-data-controller/
+    mv ./cv-data-controller/target/cv-data-controller-x.y.z-SNAPSHOT.jar ./cv-data-controller/
     ``` 
     Windows:
     ```windows
-    move .\cv-data-controller\target\cv-data-controller-x.x.x-SNAPSHOT.jar .\cv-data-controller\
+    move .\cv-data-controller\target\cv-data-controller-x.y.z-SNAPSHOT.jar .\cv-data-controller\
     ```
 
-    Replace `x.x.x` with the version number of the JAR file. If a JAR file already exists in the `cv-data-controller` directory, you may need to delete it first.
+    Replace `x.y.z` with the version number of the JAR file. If a JAR file already exists in the `cv-data-controller` directory, you may need to delete it first.
 
 1. Copy the sample.env to .env:
 

ode-data-logger/README.md

@@ -37,14 +37,14 @@ The following instructions are intended to be executed from the root directory o
 
     Linux:
     ```bash
-    mv ./ode-data-logger/target/ode-data-logger-x.x.x-SNAPSHOT.jar ./ode-data-logger/
+    mv ./ode-data-logger/target/ode-data-logger-x.y.z-SNAPSHOT.jar ./ode-data-logger/
     ```
     Windows:
     ```windows
-    move .\ode-data-logger\target\ode-data-logger-x.x.x-SNAPSHOT.jar .\ode-data-logger\
+    move .\ode-data-logger\target\ode-data-logger-x.y.z-SNAPSHOT.jar .\ode-data-logger\
     ```
 
-    Replace `x.x.x` with the version number of the JAR file. If a JAR file already exists in the `ode-data-logger` directory, you may need to delete it first.
+    Replace `x.y.z` with the version number of the JAR file. If a JAR file already exists in the `ode-data-logger` directory, you may need to delete it first.
 
 1. Copy the sample.env to .env:
 

ode-mongo-logger/README.md

@@ -36,14 +36,14 @@ The following instructions are intended to be executed from the root directory o
 
     Linux:
     ```bash
-    mv ./ode-mongo-logger/target/ode-mongo-logger-x.x.x-SNAPSHOT.jar ./ode-mongo-logger/
+    mv ./ode-mongo-logger/target/ode-mongo-logger-x.y.z-SNAPSHOT.jar ./ode-mongo-logger/
     ```
     Windows:
     ```windows
-    move .\ode-mongo-logger\target\ode-mongo-logger-x.x.x-SNAPSHOT.jar .\ode-mongo-logger\
+    move .\ode-mongo-logger\target\ode-mongo-logger-x.y.z-SNAPSHOT.jar .\ode-mongo-logger\
     ```
 
-    Replace `x.x.x` with the version number of the JAR file. If a JAR file already exists in the `ode-mongo-logger` directory, you may need to delete it first.
+    Replace `x.y.z` with the version number of the JAR file. If a JAR file already exists in the `ode-mongo-logger` directory, you may need to delete it first.
 
 1. Copy the sample.env to .env:
 

ode-wrapper/README.md

@@ -38,14 +38,14 @@ The following instructions are intended to be executed from the root directory o
 
     Linux:
     ```bash
-    mv ./ode-wrapper/target/ode-wrapper-x.x.x-SNAPSHOT.jar ./ode-wrapper/
+    mv ./ode-wrapper/target/ode-wrapper-x.y.z-SNAPSHOT.jar ./ode-wrapper/
     ```
     Windows:
     ```windows
-    move .\ode-wrapper\target\ode-wrapper-x.x.x-SNAPSHOT.jar .\ode-wrapper\
+    move .\ode-wrapper\target\ode-wrapper-x.y.z-SNAPSHOT.jar .\ode-wrapper\
     ```
 
-    Replace `x.x.x` with the version number of the JAR file. If a JAR file already exists in the `ode-wrapper` directory, you may need to delete it first.
+    Replace `x.y.z` with the version number of the JAR file. If a JAR file already exists in the `ode-wrapper` directory, you may need to delete it first.
 
 1. Copy the sample.env to .env:
 

rsu-data-controller/README.md

@@ -35,14 +35,14 @@ The following instructions are intended to be executed from the root directory o
 
     Linux:
     ```bash
-    mv ./rsu-data-controller/target/rsu-data-controller-x.x.x-SNAPSHOT.jar ./rsu-data-controller/
+    mv ./rsu-data-controller/target/rsu-data-controller-x.y.z-SNAPSHOT.jar ./rsu-data-controller/
     ```
     Windows:
     ```windows
-    move .\rsu-data-controller\target\rsu-data-controller-x.x.x-SNAPSHOT.jar .\rsu-data-controller\
+    move .\rsu-data-controller\target\rsu-data-controller-x.y.z-SNAPSHOT.jar .\rsu-data-controller\
     ```
 
-    Replace `x.x.x` with the version number of the JAR file. If a JAR file already exists in the `rsu-data-controller` directory, you may need to delete it first.
+    Replace `x.y.z` with the version number of the JAR file. If a JAR file already exists in the `rsu-data-controller` directory, you may need to delete it first.
 
 1. Copy the sample.env to .env:
 

tim-refresh/README.md

@@ -34,14 +34,14 @@ The following instructions are intended to be executed from the root directory o
 
     Linux:
     ```bash
-    mv ./tim-refresh/target/tim-refresh-x.x.x-SNAPSHOT.jar ./tim-refresh/
+    mv ./tim-refresh/target/tim-refresh-x.y.z-SNAPSHOT.jar ./tim-refresh/
     ``` 
     Windows:
     ```windows
-    move .\tim-refresh\target\tim-refresh-x.x.x-SNAPSHOT.jar .\tim-refresh\
+    move .\tim-refresh\target\tim-refresh-x.y.z-SNAPSHOT.jar .\tim-refresh\
     ```
 
-    Replace `x.x.x` with the version number of the JAR file. If a JAR file already exists in the `tim-refresh` directory, you may need to delete it first.
+    Replace `x.y.z` with the version number of the JAR file. If a JAR file already exists in the `tim-refresh` directory, you may need to delete it first.
 
 1. Copy the sample.env to .env: