docs: Updated two more places, where we didn't output a concrete vers…

…ion in the docs.
apache · Feb 14, 2024 · fd53a59 · fd53a59
1 parent e34fa65
commit fd53a59
Show file tree

Hide file tree

Showing 2 changed files with 19 additions and 16 deletions.
diff --git a/src/site/asciidoc/users/tools/scraper.adoc b/src/site/asciidoc/users/tools/scraper.adoc
@@ -30,14 +30,16 @@ As we have encountered exactly the same problem for about every integration modu
 This tool automatically handles all of the tasks mentioned above.
 
 === Getting started with the `Scraper`
-The Scraper can be found in the Maven module
-```
-<dependency>
-  <groupId>org.apache.plc4x</groupId>
-  <artifactId>plc4j-scraper</artifactId>
-  <version>${current.version}</version>
-</dependency>
-```
+The Scraper can be found in the Maven module:
+
+[subs=attributes+]
+----
+    <dependency>
+      <groupId>org.apache.plc4x</groupId>
+      <artifactId>plc4j-scraper</artifactId>
+      <version>{current-last-released-version}</version>
+    </dependency>
+----
 
 In general, you need 3 parts to work with the `Scraper`:
 

diff --git a/src/site/asciidoc/users/tools/testing.adoc b/src/site/asciidoc/users/tools/testing.adoc
@@ -23,14 +23,15 @@ PLC4X has a _Mock Driver_ which was initially implemented to be used for Unit Te
 But this driver is also very suitable to play around a bit with the PLC4X API if no _Hardware_ PLC is available.
 The driver can be found in the Maven module
 
-```
-<dependency>
-  <groupId>org.apache.plc4x</groupId>
-  <artifactId>plc4j-transport-test</artifactId>
-  <version>${current.version}</version>
-  <scope>test</scope>
-</dependency>
-```
+[subs=attributes+]
+----
+    <dependency>
+      <groupId>org.apache.plc4x</groupId>
+      <artifactId>plc4j-transport-test</artifactId>
+      <version>{current-last-released-version}</version>
+      <scope>test</scope>
+   </dependency>
+----
 
 The connection string Syntax for the mock driver is `mock:{name-of-the-connection}`. So you can use multiple Mock Devices at the same time.