Maven

Maven Central   

MockServer publishes the following artifacts to Maven Central under the org.mock-server groupId. Each comes in two forms:

• -no-dependencies form (RECOMMENDED) — the same code with every transitive dependency bundled into the jar and its packages relocated under shaded_package.*. This form declares zero transitive dependencies in its POM, so it cannot clash with versions of Netty, Jackson, Guava, Bouncy Castle, etc. that your project already uses, and it removes the noise from CVE scanners flagging unused transitive dependencies.
• Plain form — the unshaded jar with transitive dependencies declared in the POM. Use this only when you need to override a specific transitive version yourself.

Migrating from 5.15.x or earlier: the <classifier>shaded</classifier> form was removed in 6.0.0. Replace it with the corresponding -no-dependencies artifactId (e.g. mockserver-netty with <classifier>shaded</classifier> → mockserver-netty-no-dependencies). The -no-dependencies artifacts have always been the preferred form and produce the same bytes.

Artifact summary

mockserver-bom — Bill of Materials (version alignment)

Import mockserver-bom to keep the MockServer modules you use on one, mutually consistent version: declare any MockServer artifact without repeating its version. The BOM manages only MockServer's own org.mock-server modules — it does not pin the third-party libraries MockServer relies on internally (Jackson, Netty, Guava, Nimbus, …), so importing it never changes the versions or scopes your project resolves for those shared libraries. (If you use the -no-dependencies form there are no MockServer transitive dependencies to align, so the BOM is rarely needed.)

Strict version alignment. If your build enforces a single version of every dependency — for example the Maven Enforcer dependencyConvergence rule — importing mockserver-bom will not converge MockServer's third-party transitive versions for you (earlier releases did pin them, but that silently overrode consumers' own dependency versions and scopes, so it was removed). Manage those third-party versions yourself, or import each upstream project's own BOM.

Maven — import the BOM in dependencyManagement, then declare MockServer artifacts without a version:

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>org.mock-server</groupId>
            <artifactId>mockserver-bom</artifactId>
            <version>8.0.0</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

Gradle — use the platform dependency:

testImplementation(platform("org.mock-server:mockserver-bom:8.0.0"))

mockserver-netty — embedded server

The Netty-based HTTP(S) server for mocking and proxying. Use this when you want a MockServer instance running inside your test JVM or application.

Maven:

<dependency>
    <groupId>org.mock-server</groupId>
    <artifactId>mockserver-netty-no-dependencies</artifactId>
    <version>8.0.0</version>
    <scope>test</scope>
</dependency>

Gradle:

testImplementation("org.mock-server:mockserver-netty-no-dependencies:8.0.0")

Variants:

• org.mock-server:mockserver-netty-no-dependencies:8.0.0 — shaded, zero transitive dependencies (recommended)
• org.mock-server:mockserver-netty:8.0.0 — unshaded, transitive dependencies declared in the POM
• org.mock-server:mockserver-netty:8.0.0:jar-with-dependencies — single executable jar (for running MockServer from the command line via java -jar)

mockserver-client-java — Java client

The Java client that talks to a running MockServer instance (either a local ClientAndServer or a remote one).

<dependency>
    <groupId>org.mock-server</groupId>
    <artifactId>mockserver-client-java-no-dependencies</artifactId>
    <version>8.0.0</version>
    <scope>test</scope>
</dependency>

Variants:

• org.mock-server:mockserver-client-java-no-dependencies:8.0.0 — shaded, zero transitive dependencies (recommended)
• org.mock-server:mockserver-client-java:8.0.0 — unshaded

mockserver-junit-rule — JUnit 4 integration

A JUnit 4 @Rule that starts MockServer on a free port before each test and stops it after.

<dependency>
    <groupId>org.mock-server</groupId>
    <artifactId>mockserver-junit-rule-no-dependencies</artifactId>
    <version>8.0.0</version>
    <scope>test</scope>
</dependency>

Variants:

• org.mock-server:mockserver-junit-rule-no-dependencies:8.0.0 (recommended)
• org.mock-server:mockserver-junit-rule:8.0.0

mockserver-junit-jupiter — JUnit 5 integration

A JUnit 5 test extension that starts MockServer for tests annotated with @MockServerSettings and @ExtendWith(MockServerExtension.class).

<dependency>
    <groupId>org.mock-server</groupId>
    <artifactId>mockserver-junit-jupiter-no-dependencies</artifactId>
    <version>8.0.0</version>
    <scope>test</scope>
</dependency>

Variants:

• org.mock-server:mockserver-junit-jupiter-no-dependencies:8.0.0 (recommended)
• org.mock-server:mockserver-junit-jupiter:8.0.0

mockserver-spring-test-listener — Spring integration

A Spring TestExecutionListener that starts MockServer for tests in Spring projects.

<dependency>
    <groupId>org.mock-server</groupId>
    <artifactId>mockserver-spring-test-listener-no-dependencies</artifactId>
    <version>8.0.0</version>
    <scope>test</scope>
</dependency>

Variants:

• org.mock-server:mockserver-spring-test-listener-no-dependencies:8.0.0 (recommended)
• org.mock-server:mockserver-spring-test-listener:8.0.0

mockserver-integration-testing — shared test helpers

A library of integration-test helpers (assertion utilities, fixtures, shared base classes) used to test MockServer itself and that can be reused in downstream test suites.

<dependency>
    <groupId>org.mock-server</groupId>
    <artifactId>mockserver-integration-testing-no-dependencies</artifactId>
    <version>8.0.0</version>
    <scope>test</scope>
</dependency>

Variants:

• org.mock-server:mockserver-integration-testing-no-dependencies:8.0.0 (recommended)
• org.mock-server:mockserver-integration-testing:8.0.0

mockserver-maven-plugin — Maven plugin

A Maven plugin to start, stop, and fork MockServer as part of the build lifecycle — useful for binding MockServer to pre-integration-test / post-integration-test phases.

<plugin>
    <groupId>org.mock-server</groupId>
    <artifactId>mockserver-maven-plugin</artifactId>
    <version>8.0.0</version>
    <configuration>
        <serverPort>1080</serverPort>
        <pipeLogToConsole>true</pipeLogToConsole>
    </configuration>
</plugin>

mockserver-war / mockserver-proxy-war — servlet WARs

Deployable WAR archives for hosting MockServer (in mock mode or proxy mode) on any servlet container.

• mockserver-war — download .war
• mockserver-proxy-war — download .war

Sonatype SNAPSHOT

Pre-release SNAPSHOT builds are published to the Sonatype Central Portal snapshot repository at https://central.sonatype.com/repository/maven-snapshots/org/mock-server/.

Maven

Add the snapshot repository to your ~/.m2/settings.xml (preferred) or to the project pom.xml:

<profile>
    <id>sonatype</id>
    <activation>
        <activeByDefault>true</activeByDefault>
    </activation>
    <repositories>
        <repository>
            <id>central-portal-snapshots</id>
            <name>Sonatype Central Portal snapshots</name>
            <url>https://central.sonatype.com/repository/maven-snapshots/</url>
            <releases>
                <enabled>false</enabled>
            </releases>
            <snapshots>
                <enabled>true</enabled>
            </snapshots>
        </repository>
    </repositories>
</profile>

Then reference the SNAPSHOT version directly. The -no-dependencies artifacts are recommended here too:

<dependency>
    <groupId>org.mock-server</groupId>
    <artifactId>mockserver-netty-no-dependencies</artifactId>
    <version>8.0.1-SNAPSHOT</version>
</dependency>

Gradle

repositories {
    maven { url "https://central.sonatype.com/repository/maven-snapshots/" }
}

dependencies {
    testImplementation("org.mock-server:mockserver-netty-no-dependencies:8.0.1-SNAPSHOT")
}