diff --git a/integration-tests/it-exporter/it-exporter-test/pom.xml b/integration-tests/it-exporter/it-exporter-test/pom.xml
index 40ee58412..9620db370 100644
--- a/integration-tests/it-exporter/it-exporter-test/pom.xml
+++ b/integration-tests/it-exporter/it-exporter-test/pom.xml
@@ -29,5 +29,36 @@
       <version>${guava.version}</version>
       <scope>test</scope>
     </dependency>
+    <!-- Each integration test runs its sample application from the shaded jar
+    that the corresponding module leaves in `target`, a dependency Maven cannot
+    infer: it derives the reactor build order only from directly declared
+    dependencies. These declarations give it that order; without them serial
+    builds work only by accident of the module ordering in `../pom.xml`, while
+    `mvn -T` races against the sample modules and `mvn -am` skips them
+    entirely. -->
+    <dependency>
+      <groupId>io.prometheus</groupId>
+      <artifactId>it-exporter-servlet-tomcat-sample</artifactId>
+      <version>${project.version}</version>
+      <scope>test</scope>
+    </dependency>
+    <dependency>
+      <groupId>io.prometheus</groupId>
+      <artifactId>it-exporter-servlet-jetty-sample</artifactId>
+      <version>${project.version}</version>
+      <scope>test</scope>
+    </dependency>
+    <dependency>
+      <groupId>io.prometheus</groupId>
+      <artifactId>it-exporter-httpserver-sample</artifactId>
+      <version>${project.version}</version>
+      <scope>test</scope>
+    </dependency>
+    <dependency>
+      <groupId>io.prometheus</groupId>
+      <artifactId>it-exporter-duplicate-metrics-sample</artifactId>
+      <version>${project.version}</version>
+      <scope>test</scope>
+    </dependency>
   </dependencies>
 </project>
diff --git a/integration-tests/it-exporter/it-no-protobuf-test/pom.xml b/integration-tests/it-exporter/it-no-protobuf-test/pom.xml
index 389867de5..313cefe7b 100644
--- a/integration-tests/it-exporter/it-no-protobuf-test/pom.xml
+++ b/integration-tests/it-exporter/it-no-protobuf-test/pom.xml
@@ -23,5 +23,18 @@
       <version>${project.version}</version>
       <scope>test</scope>
     </dependency>
+    <!-- `NoProtobufIT` runs its sample application from the shaded jar that
+    `it-exporter-no-protobuf` leaves in `target`, a dependency Maven cannot
+    infer: it derives the reactor build order only from directly declared
+    dependencies. This declaration gives it that order; without it serial
+    builds work only by accident of the module ordering in `../pom.xml`, while
+    `mvn -T` races against the sample module and `mvn -am` skips it
+    entirely. -->
+    <dependency>
+      <groupId>io.prometheus</groupId>
+      <artifactId>it-exporter-no-protobuf</artifactId>
+      <version>${project.version}</version>
+      <scope>test</scope>
+    </dependency>
   </dependencies>
 </project>
diff --git a/integration-tests/it-spring-boot-smoke-test/pom.xml b/integration-tests/it-spring-boot-smoke-test/pom.xml
index 6c0f92357..11afc50b6 100644
--- a/integration-tests/it-spring-boot-smoke-test/pom.xml
+++ b/integration-tests/it-spring-boot-smoke-test/pom.xml
@@ -56,6 +56,22 @@
       <artifactId>micrometer-registry-prometheus</artifactId>
       <scope>runtime</scope>
     </dependency>
+    <!-- Already pulled in transitively by `micrometer-registry-prometheus`,
+    but declared explicitly (with the exclusion that
+    `micrometer-registry-prometheus` applies, so that the resolved set of
+    artifacts, their versions and their scopes is unchanged) because Maven
+    derives the reactor build order only from directly declared dependencies. -->
+    <dependency>
+      <groupId>io.prometheus</groupId>
+      <artifactId>prometheus-metrics-core</artifactId>
+      <scope>runtime</scope>
+      <exclusions>
+        <exclusion>
+          <groupId>io.prometheus</groupId>
+          <artifactId>prometheus-metrics-tracer-initializer</artifactId>
+        </exclusion>
+      </exclusions>
+    </dependency>
     <dependency>
       <groupId>org.springframework.boot</groupId>
       <artifactId>spring-boot-starter-test</artifactId>
diff --git a/prometheus-metrics-exporter-opentelemetry/src/test/java/io/prometheus/metrics/exporter/opentelemetry/ExemplarTest.java b/prometheus-metrics-exporter-opentelemetry/src/test/java/io/prometheus/metrics/exporter/opentelemetry/ExemplarTest.java
index c21f1ead4..c764f3e83 100644
--- a/prometheus-metrics-exporter-opentelemetry/src/test/java/io/prometheus/metrics/exporter/opentelemetry/ExemplarTest.java
+++ b/prometheus-metrics-exporter-opentelemetry/src/test/java/io/prometheus/metrics/exporter/opentelemetry/ExemplarTest.java
@@ -13,6 +13,7 @@
 import static org.awaitility.Awaitility.await;
 
 import com.github.tomakehurst.wiremock.http.Request;
+import com.github.tomakehurst.wiremock.junit5.WireMockRuntimeInfo;
 import com.github.tomakehurst.wiremock.junit5.WireMockTest;
 import com.github.tomakehurst.wiremock.matching.MatchResult;
 import com.github.tomakehurst.wiremock.matching.ValueMatcher;
@@ -34,7 +35,7 @@
 import org.junit.jupiter.api.BeforeEach;
 import org.junit.jupiter.api.Test;
 
-@WireMockTest(httpPort = 4317)
+@WireMockTest
 class ExemplarTest {
   private static final String ENDPOINT_PATH = "/v1/metrics";
   private static final int TIMEOUT = 3;
@@ -45,10 +46,10 @@ class ExemplarTest {
   private OpenTelemetryExporter openTelemetryExporter;
 
   @BeforeEach
-  void setUp() {
+  void setUp(WireMockRuntimeInfo wireMockRuntimeInfo) {
     openTelemetryExporter =
         OpenTelemetryExporter.builder()
-            .endpoint("http://localhost:4317")
+            .endpoint(wireMockRuntimeInfo.getHttpBaseUrl())
             .protocol("http/protobuf")
             .intervalSeconds(1)
             .buildAndStart();