build: use mise instead of Maven Wrapper to set up Maven locally

Generated with:
$ MISE_DISABLE_BACKENDS=asdf mise use maven@3.6.3

See also: jdx/mise#4177

Part of #1748

Author: php-coder

.gitignore

@@ -53,9 +53,6 @@ coder_rsa
 mystamps_rsa
 prod_vars.yml
 
-# maven-wrapper
-.mvn/wrapper/maven-wrapper.jar
-
 # @asm0dey uses molecule for role testing which generates .pyc files
 # and also creates molecule directory
 *.pyc

.mvn/wrapper/MavenWrapperDownloader.java

@@ -25,9 +25,10 @@ You can look at it and try on https://my-stamps.ru
 If you are programmer/sysadmin or you just feeling that you are able to run a local version of the site then follow the following instructions:
 If you want to run it locally, follow the instructions:
 
-* install JDK (at least 8th version is required)
+* install JDK (8th version is required) and Maven
+  * the preferred way to set up tools is to use [`mise`](https://mise.jdx.dev/getting-started.html). After its activation, the required tools will be installed automatically
 * clone this project
-* from the console inside the directory with source code, execute the command `./mvnw spring-boot:run`
+* from the console inside the directory with source code, execute the command `mvn spring-boot:run`
 * open up `http://127.0.0.1:8080` in a browser
 * browse the site or log in as one of the pre-created users: `admin`, `paid`, or `coder` with password `test`
 * press `Ctrl-C` to stop the server

.mvn/wrapper/maven-wrapper.properties

@@ -2,7 +2,7 @@
 
 ## Faster Iterations
 
-As we already know, `./mvnw verify` runs all the integration tests. But let's
+As we already know, `mvn verify` runs all the integration tests. But let's
 suppose that we are working on a single test and we need to run it many times
 until it will work as desired. In this case, we would like to iterate faster
 and at least don't run all the tests, but the only one that we are working on.
@@ -11,11 +11,11 @@ In this case we can (temporary) mark the test with a unique tag, let’s say
 `testme`, and ask `robotframework-maven-plugin` to execute only tests with such
 a tag:
 ```console
-./mvnw verify -Dincludes=testme
+mvn verify -Dincludes=testme
 ```
 
 Now we run much less tests but could we make the execution even faster? Sure,
-we can! Let's look on what exactly `./mvnw verify` does:
+we can! Let's look on what exactly `mvn verify` does:
 1) it runs the application (this in turn includes many steps, like code
    compilation, preparation of the resources, running unit tests and so on)
 2) it runs [Wiremock server](wiremock.md) that is required by some tests
@@ -28,14 +28,14 @@ execute all the steps that we need:
 
 1) run the application:
    ```console
-   ./mvnw spring-boot:run
+   mvn spring-boot:run
    ```
 2) in another terminal, run Wiremock server, only if your test need it:
    ```console
-   ./mvnw wiremock:run -Dwiremock.keepRunning=true
+   mvn wiremock:run -Dwiremock.keepRunning=true
    ```
 3) in another terminal, run integration tests as many times as you need:
    ```console
-   ./mvnw robotframework:run -Dincludes=testme
+   mvn robotframework:run -Dincludes=testme
    ```
 

README.md

@@ -5,12 +5,12 @@ WireMock is a simulator for HTTP-based APIs. We use this tool in the integration
 external services. For example, for testing import of the stamps series from sites.
 
 ## Running on CI
-WireMock is automatically running/stopping during integration tests execution (`./mvnw verify`).
+WireMock is automatically running/stopping during integration tests execution (`mvn verify`).
 
 ## Running manually
 In order to run the server as a standalone process:
 ```console
-$ ./mvnw wiremock:run -Dwiremock.keepRunning=true
+$ mvn wiremock:run -Dwiremock.keepRunning=true
 ```
 
 After that the mock server will be available on 8888 port.

docs/robotframework.md

@@ -5,11 +5,11 @@ possible configurations, we support only those that are typically used:
 
 * **a single container** where the application is running with `test` profile.
   In this mode, it also runs in-memory database H2. This is roughly the same as
-  executing `./mvnw spring-boot:run` command but inside a Docker container.
+  executing `mvn spring-boot:run` command but inside a Docker container.
 
   * Create a WAR file and build the image `phpcoder/mystamps:latest`:
     ```console
-    $ ./mvnw package dockerfile:build
+    $ mvn package dockerfile:build
     ```
   * Run a container with `docker compose`:
     ```console

docs/wiremock.md

@@ -0,0 +1,2 @@
+[tools]
+maven = "3.6.3"