WireMock

Hi. Which version of WireMock do you use?

Asking, because <https://github.com/wiremock/wiremock/pull/2238> changed the implementation of the templating engine, and some behavior might have changed. So triage is needed. FYI <@U03N1E342B0>

P.S: it's not often to see the Maven Docker Plugin in the wild. Is it the fabric8 one? If you triage, one of the first steps would be to ensure that the parameter is actually propagated

Thanks oleg for kind response, I'm using wiremock `2.35.0` I will go through the given links. Thanks.

Screen Shot 2023-07-25 at 11.12.13 AM.png

Screen Shot 2023-07-25 at 11.09.05 AM.png

Hi <@U04NTGJ6Z1D>, I also found that my wiremock always run at port `8080` inside docker. And I see that my command arguments are present in wiremock tab in docker app. (Please see attached image). But still none of those arguments are honored. For eg: `--verbose` doesnt enable verbose logging. It still says verbose as `false` in output.

Never mind, I just changed `WIREMOCK_COMMANDLINE_OPTIONS` to `cmd` and it worked :slightly_smiling_face:. Thanks.

```&lt;cmd&gt;--port 8181 --verbose --global-response-templating&lt;/cmd&gt;```

Did you find this environment variable somewhere in the docs?

If you would be interested to write a short article about running WireMock from the Maven Docker plugin (use-cases and how-to's), it would be awesome too!