Firstly, I'd strongly suggest that you consider either starting WireMock programmatically, or running the standalone JAR e.g.
java -jar wiremock-1.32-standalone.jar --port <your port number>
At the start of your test code you'll need to tell the client where the server is:
WireMock.configureFor("<wiremock server host>", <your port number>);
There are a couple of options for programmatic startup: 1) If you're using JUnit, you can just add the @Rule as described here: http://wiremock.org/getting-started.html#junit-4-x 2) For any other test framework, you can new up the server: http://wiremock.org/getting-started.html#non-junit-and-general-java-usage
It's worth noting that there are some features of WireMock that aren't available when deployed into a container (mostly fault injection related).
If you have no choice than to run inside a container, then a few things worth noting: The host and port of the server are set in the container settings, so from within the Maven plugin settings you'd want something like this:
<connectors>
<connector implementation="org.mortbay.jetty.nio.SelectChannelConnector">
<port>9090</port>
</connector>
</connectors>
If you've deployed the WAR under a non-root URL, you also need to tell the client about this e.g.
WireMock.configureFor("my.jetty.host", 9090, "/wiremock");