Description

<dependency>
    <groupId>com.fortemate</groupId>
    <artifactId>dicechess-bot-runtime</artifactId>
    <version>2.0.0</version>
</dependency>

<?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>com.fortemate</groupId>
    <artifactId>dicechess-bot-runtime</artifactId>
    <version>2.0.0</version>
    <packaging>jar</packaging>

    <name>Fortemate Dice Chess Bot Runtime</name>
    <description>Transport runtime for Dice Chess webhook bots: HMAC-SHA256 verification, the ownership handshake,
        typed turn and draw decisions, and framework-free HTTP wiring for Java, Kotlin, and Scala.
    </description>
    <url>https://fortemate.com</url>
    <inceptionYear>2026</inceptionYear>

    <organization>
        <name>Fortemate</name>
        <url>https://fortemate.com</url>
    </organization>

    <licenses>
        <license>
            <name>MIT License</name>
            <url>https://opensource.org/licenses/MIT</url>
        </license>
    </licenses>

    <developers>
        <developer>
            <id>fortemate</id>
            <name>Fortemate</name>
            <email>contact@fortemate.com</email>
            <url>https://fortemate.com</url>
            <roles>
                <role>developer</role>
            </roles>
            <timezone>Europe/Riga</timezone>
        </developer>
    </developers>

    <scm>
        <url>https://github.com/fortemate/dicechess-bot-runtime</url>
        <connection>scm:git:https://github.com/fortemate/dicechess-bot-runtime.git</connection>
        <developerConnection>scm:git:ssh://git@github.com/fortemate/dicechess-bot-runtime.git</developerConnection>
        <tag>HEAD</tag>
    </scm>

    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
        <maven.compiler.release>25</maven.compiler.release>

        <gson.version>2.14.0</gson.version>
        <junit.version>6.1.3</junit.version>
        <assertj.version>3.27.7</assertj.version>

        <maven-compiler-plugin.version>3.15.0</maven-compiler-plugin.version>
        <maven-surefire-plugin.version>3.5.6</maven-surefire-plugin.version>
        <maven-javadoc-plugin.version>3.12.0</maven-javadoc-plugin.version>
        <maven-jar-plugin.version>3.5.1</maven-jar-plugin.version>
        <maven-source-plugin.version>3.4.0</maven-source-plugin.version>
        <maven-gpg-plugin.version>3.2.8</maven-gpg-plugin.version>
        <central-publishing-maven-plugin.version>0.11.0</central-publishing-maven-plugin.version>

        <!-- Release workflows wait for Maven Central's terminal published state. -->
        <centralPublishing.autoPublish>true</centralPublishing.autoPublish>
    </properties>

    <dependencies>
        <!-- Envelope parsing only; never appears in the public API (String / java.util.* at every boundary). -->
        <dependency>
            <groupId>com.google.code.gson</groupId>
            <artifactId>gson</artifactId>
            <version>${gson.version}</version>
        </dependency>

        <dependency>
            <groupId>org.junit.jupiter</groupId>
            <artifactId>junit-jupiter</artifactId>
            <version>${junit.version}</version>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>org.assertj</groupId>
            <artifactId>assertj-core</artifactId>
            <version>${assertj.version}</version>
            <scope>test</scope>
        </dependency>
    </dependencies>

    <build>
        <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>

            <!-- Automatic-Module-Name pins the JPMS module name to the public package. -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-jar-plugin</artifactId>
                <version>${maven-jar-plugin.version}</version>
                <configuration>
                    <archive>
                        <manifestEntries>
                            <Automatic-Module-Name>com.fortemate.dicechess.runtime</Automatic-Module-Name>
                        </manifestEntries>
                    </archive>
                </configuration>
            </plugin>

            <!-- doclint is a hard gate: undocumented or malformed public API fails the build. -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-javadoc-plugin</artifactId>
                <version>${maven-javadoc-plugin.version}</version>
                <configuration>
                    <doclint>all</doclint>
                    <additionalOptions>
                        <additionalOption>-Xwerror</additionalOption>
                    </additionalOptions>
                    <quiet>true</quiet>
                </configuration>
                <executions>
                    <execution>
                        <id>attach-javadocs</id>
                        <phase>package</phase>
                        <goals>
                            <goal>jar</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

            <!-- Central rejects a bundle with no sources jar. Attached unconditionally, the same way
                 the javadoc jar above already is, so `mvn package` alone always produces the complete,
                 publishable artifact set — nothing release-specific to remember on a normal build. -->
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-source-plugin</artifactId>
                <version>${maven-source-plugin.version}</version>
                <executions>
                    <execution>
                        <id>attach-sources</id>
                        <phase>package</phase>
                        <goals>
                            <goal>jar-no-fork</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>

    <!-- Signing and the Central Portal upload activate only under `-P release` (the release/publish
         workflows): a laptop `mvn test`/`mvn package` needs neither a GPG passphrase nor Central
         credentials, and stays exactly as fast as it is today. -->
    <profiles>
        <profile>
            <id>release</id>
            <build>
                <plugins>
                    <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-gpg-plugin</artifactId>
                        <version>${maven-gpg-plugin.version}</version>
                        <configuration>
                            <bestPractices>true</bestPractices>
                            <gpgArguments>
                                <arg>--pinentry-mode</arg>
                                <arg>loopback</arg>
                            </gpgArguments>
                        </configuration>
                        <executions>
                            <execution>
                                <id>sign-artifacts</id>
                                <phase>verify</phase>
                                <goals>
                                    <goal>sign</goal>
                                </goals>
                            </execution>
                        </executions>
                    </plugin>

                    <plugin>
                        <groupId>org.sonatype.central</groupId>
                        <artifactId>central-publishing-maven-plugin</artifactId>
                        <version>${central-publishing-maven-plugin.version}</version>
                        <extensions>true</extensions>
                        <configuration>
                            <publishingServerId>central</publishingServerId>
                            <!-- Use the canonical <groupId>:<artifactId>:<version> deployment name so
                                 releases in the Central Portal match organization-wide convention rather
                                 than displaying the default "Deployment" label. -->
                            <deploymentName>${project.groupId}:${project.artifactId}:${project.version}</deploymentName>
                            <autoPublish>${centralPublishing.autoPublish}</autoPublish>
                            <!-- With autoPublish on, "published" is a state the deployment actually
                                 reaches on its own — waiting for it (rather than the default
                                 `validated`) means a post-validation failure fails the release step
                                 instead of silently leaving an unpublished deployment behind. -->
                            <waitUntil>published</waitUntil>
                        </configuration>
                    </plugin>
                </plugins>
            </build>
        </profile>
    </profiles>

    <!-- No distributionManagement: the Central publishing extension owns release deploys. A plain
         mvn deploy outside the release profile intentionally has nowhere to publish. -->
</project>