Description

<dependency>
    <groupId>jp.golia</groupId>
    <artifactId>kevy</artifactId>
    <version>6.2.2</version>
</dependency>

<?xml version="1.0" encoding="UTF-8"?>
<!--
  jp.golia:kevy — the native Java kevy client (a first-party port of the
  language-agnostic client contract in docs/client-contract.md).

  One artifact, both faces: a blocking KevyClient and an async
  KevyAsyncClient (java.util.concurrent.CompletableFuture), agreeing on
  results. connect(url): mem:// / file:// -> embedded (over the libkevy_jni
  desktop-JVM door), kevy:// / redis:// / tcp:// -> a native RESP2/3 TCP
  client. Zero runtime dependencies beyond the JDK; JUnit 5 is test-only.

  Maven/Gradle are not required to build or test in this repo — see
  run-tests.sh, which compiles with javac and runs JUnit 5 via the
  junit-platform-console-standalone jar (matching bench/jnigate.sh). This
  POM is the canonical artifact definition for a Maven-based consumer.
-->
<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>jp.golia</groupId>
    <artifactId>kevy</artifactId>
    <version>6.2.2</version>
    <packaging>jar</packaging>

    <name>kevy</name>
    <description>Native Java client for kevy — blocking + async faces, embedded (JNI) and remote (RESP2/3 TCP).</description>
    <url>https://kevy.golia.jp</url>

    <organization>
        <name>GOLIA K.K.</name>
        <url>https://kevy.golia.jp</url>
    </organization>

    <!-- Maven Central refuses a bundle without these three. They are not
         decoration: the licence tells a consumer what they may do, the
         SCM block tells a build where the sources came from, and the
         developer entry gives the artifact an accountable owner. -->
    <licenses>
        <license>
            <name>Apache-2.0</name>
            <url>https://www.apache.org/licenses/LICENSE-2.0.txt</url>
            <distribution>repo</distribution>
        </license>
        <license>
            <name>MIT</name>
            <url>https://opensource.org/licenses/MIT</url>
            <distribution>repo</distribution>
        </license>
    </licenses>

    <developers>
        <developer>
            <id>goliajp</id>
            <name>GOLIA K.K.</name>
            <organization>GOLIA K.K.</organization>
            <organizationUrl>https://kevy.golia.jp</organizationUrl>
        </developer>
    </developers>

    <scm>
        <connection>scm:git:https://github.com/goliajp/kevy.git</connection>
        <developerConnection>scm:git:ssh://git@github.com/goliajp/kevy.git</developerConnection>
        <url>https://github.com/goliajp/kevy</url>
        <tag>HEAD</tag>
    </scm>

    <properties>
        <maven.compiler.release>17</maven.compiler.release>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <junit.version>5.10.2</junit.version>
    </properties>

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

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>3.2.5</version>
                <configuration>
                    <!-- libkevy_jni lives under the cargo target dir. -->
                    <argLine>-Djava.library.path=${kevy.jni.dir}</argLine>
                </configuration>
            </plugin>
        </plugins>
    </build>

    <profiles>
        <!-- Everything Central demands beyond a plain jar, kept out of the
             everyday build: a sources jar, a javadoc jar, and a detached
             GPG signature for each artifact. Activate with `-Prelease`,
             which is what the publish path does; a developer running
             `mvn test` never pays for any of it and never needs a key. -->
        <profile>
            <id>release</id>
            <build>
                <plugins>
                    <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-source-plugin</artifactId>
                        <version>3.3.1</version>
                        <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>
                        <version>3.6.3</version>
                        <configuration>
                            <!-- Report broken syntax, not absent prose. An
                                 undocumented member is a gap; malformed
                                 markup is a defect that renders wrong on
                                 the published site, and only the second
                                 should stop a release. `&` unescaped in a
                                 doc comment is the defect this caught. -->
                            <doclint>all,-missing</doclint>
                        </configuration>
                        <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>3.2.4</version>
                        <executions>
                            <execution>
                                <id>sign-artifacts</id>
                                <phase>verify</phase>
                                <goals><goal>sign</goal></goals>
                                <configuration>
                                    <!-- The key arrives on stdin from the
                                         CI secret, so no interactive
                                         passphrase prompt can hang a
                                         headless publish. -->
                                    <gpgArguments>
                                        <arg>--pinentry-mode</arg>
                                        <arg>loopback</arg>
                                    </gpgArguments>
                                </configuration>
                            </execution>
                        </executions>
                    </plugin>
                </plugins>
            </build>
        </profile>
    </profiles>
</project>