pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>io.github.achird-labs</groupId>
  <artifactId>rift-java-parent</artifactId>
  <version>0.3.8-SNAPSHOT</version>
  <packaging>pom</packaging>

  <name>rift-java (parent)</name>
  <description>Official Java SDK for Rift — a Mountebank-compatible HTTP/HTTPS mock server.</description>
  <url>https://github.com/achird-labs/rift-java</url>
  <inceptionYear>2026</inceptionYear>

  <licenses>
    <license>
      <name>Apache License, Version 2.0</name>
      <url>https://www.apache.org/licenses/LICENSE-2.0.txt</url>
      <distribution>repo</distribution>
    </license>
  </licenses>

  <developers>
    <developer>
      <id>EtaCassiopeia</id>
      <name>Mohsen Zainalpour</name>
      <url>https://github.com/EtaCassiopeia</url>
    </developer>
  </developers>

  <scm>
    <connection>scm:git:https://github.com/achird-labs/rift-java.git</connection>
    <developerConnection>scm:git:git@github.com:achird-labs/rift-java.git</developerConnection>
    <url>https://github.com/achird-labs/rift-java</url>
    <tag>HEAD</tag>
  </scm>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
    <!-- Base language level for the zero-dep modules. Embedded modules override this. -->
    <maven.compiler.release>17</maven.compiler.release>

    <!-- Pinned Rift engine release the natives + version preflight track (no leading 'v'). -->
    <rift.engine.version>0.24.0</rift.engine.version>

    <!-- rift-java-bom's resolve-through-bom invoker IT is self-validation, not a prerequisite for
         the BOM artifact. It runs at integration-test (before install) and needs network to resolve
         the managed modules' transitive deps, so a failure (e.g. a locked-down mirror) would block a
         plain `mvn install` from ever landing the BOM pom. Skipped by default so a source build works
         with no flags; the release profile flips it on, so it still runs on every push/PR via
         release-smoke and at deploy. Run it locally with `-Dinvoker.skip=false`. (Only rift-java-bom
         uses the invoker plugin, so this property is inert for every other module.) -->
    <invoker.skip>true</invoker.skip>

    <!-- Dependency versions -->
    <junit.version>5.11.4</junit.version>
    <jackson.version>2.18.2</jackson.version>

    <!-- Plugin versions -->
    <maven-compiler-plugin.version>3.13.0</maven-compiler-plugin.version>
    <maven-surefire-plugin.version>3.5.2</maven-surefire-plugin.version>
    <maven-jar-plugin.version>3.4.1</maven-jar-plugin.version>
    <maven-source-plugin.version>3.3.1</maven-source-plugin.version>
    <maven-javadoc-plugin.version>3.11.2</maven-javadoc-plugin.version>
    <maven-gpg-plugin.version>3.2.7</maven-gpg-plugin.version>
    <central-publishing-plugin.version>0.8.0</central-publishing-plugin.version>
    <exec-maven-plugin.version>3.5.0</exec-maven-plugin.version>
    <flatten-maven-plugin.version>1.6.0</flatten-maven-plugin.version>
    <maven-invoker-plugin.version>3.8.0</maven-invoker-plugin.version>
    <maven-help-plugin.version>3.5.2</maven-help-plugin.version>
    <build-helper-maven-plugin.version>3.6.0</build-helper-maven-plugin.version>
  </properties>

  <modules>
    <module>rift-java-core</module>
    <module>rift-java-jackson</module>
    <module>rift-java-junit5</module>
    <module>rift-java-natives</module>
    <module>rift-java-spring</module>
    <module>rift-java-testcontainers</module>
    <module>rift-java-conformance</module>
    <module>rift-java-bom</module>
  </modules>

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.junit</groupId>
        <artifactId>junit-bom</artifactId>
        <version>${junit.version}</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
      <dependency>
        <groupId>com.fasterxml.jackson</groupId>
        <artifactId>jackson-bom</artifactId>
        <version>${jackson.version}</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
      <!-- Intra-project modules -->
      <dependency>
        <groupId>io.github.achird-labs</groupId>
        <artifactId>rift-java-core</artifactId>
        <version>${project.version}</version>
      </dependency>
    </dependencies>
  </dependencyManagement>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-compiler-plugin</artifactId>
          <version>${maven-compiler-plugin.version}</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>${maven-surefire-plugin.version}</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-jar-plugin</artifactId>
          <version>${maven-jar-plugin.version}</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-source-plugin</artifactId>
          <version>${maven-source-plugin.version}</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-javadoc-plugin</artifactId>
          <version>${maven-javadoc-plugin.version}</version>
          <!-- Pinned, not merely left to the strict defaults: these three parameters bind to the
               user properties maven.javadoc.failOnError / maven.javadoc.skip / doclint, so without
               an explicit value here a `-Dmaven.javadoc.failOnError=false` on any mvn command line
               silences javadoc errors for that invocation (#205). A <configuration> value takes
               precedence over the property, which makes that override impossible rather than merely
               detectable. scripts/check-javadoc-strictness.py requires this block to stay. -->
          <configuration>
            <failOnError>true</failOnError>
            <skip>false</skip>
            <doclint>all</doclint>
          </configuration>
        </plugin>
        <!-- Not bound to any phase: CI's javadoc-strictness sweep invokes help:effective-pom by
             goal prefix (#203). Prefix-invoked goals otherwise resolve whatever is newest on Central
             at run time, so pinning keeps the sweep reproducible. -->
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-help-plugin</artifactId>
          <version>${maven-help-plugin.version}</version>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

  <profiles>
    <!-- Embedded (stable FFM) builds only on JDK 22+. FFM binding lands in #8. -->
    <profile>
      <id>embedded</id>
      <activation>
        <jdk>[22,)</jdk>
      </activation>
      <modules>
        <module>rift-java-embedded</module>
        <!-- The parity samples use the embedded engine + intercept, so they need JDK 22+ same as
             rift-java-embedded itself; must not build on the JDK 17 lane. -->
        <module>examples</module>
      </modules>
    </profile>

    <!-- The JDK 21 preview variant builds only on JDK 21. Preview FFM flags arrive with #11. -->
    <profile>
      <id>embedded-jdk21</id>
      <activation>
        <jdk>21</jdk>
      </activation>
      <modules>
        <module>rift-java-embedded-jdk21</module>
      </modules>
    </profile>

    <!-- Release path only: pull the stable-FFM rift-java-embedded (JDK 22+) into the JDK 21 deploy
         reactor so BOTH embedded variants publish from one run. On JDK 21 the `embedded` profile
         above is inactive, so this is the module's only way into the reactor; it compiles via a
         JDK 22 toolchain (see rift-java-embedded's own `dual-embedded` profile) that must be present
         in ~/.m2/toolchains.xml. Activated by -DdualEmbedded, which the publish workflow passes on
         the JDK 21 deploy. Do NOT combine -DdualEmbedded with a JDK 22+ reactor: the `embedded`
         profile would then also add the module and the reactor would reject the duplicate. -->
    <profile>
      <id>dual-embedded</id>
      <activation>
        <property>
          <name>dualEmbedded</name>
        </property>
      </activation>
      <modules>
        <module>rift-java-embedded</module>
      </modules>
    </profile>

    <!-- Signing + sources + javadoc + Central publishing. Enabled explicitly on deploy. -->
    <profile>
      <id>release</id>
      <properties>
        <!-- Re-enable the BOM's resolve-through-bom self-validation IT in the release lane
             (release-smoke on every push/PR, and deploy), where it is skipped by default so a plain
             source install is never blocked by it. See rift-java-bom/pom.xml. -->
        <invoker.skip>false</invoker.skip>
      </properties>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-source-plugin</artifactId>
            <executions>
              <execution>
                <id>attach-sources</id>
                <goals>
                  <goal>jar-no-fork</goal>
                </goals>
              </execution>
            </executions>
          </plugin>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-javadoc-plugin</artifactId>
            <executions>
              <execution>
                <id>attach-javadocs</id>
                <goals>
                  <goal>jar</goal>
                </goals>
              </execution>
            </executions>
          </plugin>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-gpg-plugin</artifactId>
            <version>${maven-gpg-plugin.version}</version>
            <executions>
              <execution>
                <id>sign-artifacts</id>
                <phase>verify</phase>
                <goals>
                  <goal>sign</goal>
                </goals>
              </execution>
            </executions>
            <configuration>
              <gpgArguments>
                <arg>--pinentry-mode</arg>
                <arg>loopback</arg>
              </gpgArguments>
            </configuration>
          </plugin>
          <plugin>
            <groupId>org.sonatype.central</groupId>
            <artifactId>central-publishing-maven-plugin</artifactId>
            <version>${central-publishing-plugin.version}</version>
            <extensions>true</extensions>
            <configuration>
              <publishingServerId>central</publishingServerId>
              <!-- Name the Portal deployment after the artifact + version instead of the plugin's
                   generic "Deployment", so releases are identifiable in the Central UI. -->
              <deploymentName>rift-java ${project.version}</deploymentName>
              <!-- Snapshots deploy immediately; releases are auto-published once validated. -->
              <autoPublish>true</autoPublish>
              <waitUntil>validated</waitUntil>
            </configuration>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>
</project>