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>com.clickhouse.chdb</groupId>
  <artifactId>chdb-java-parent</artifactId>
  <version>1.0.0-SNAPSHOT</version>
  <packaging>pom</packaging>

  <name>chDB Java Binding (parent)</name>
  <description>JDBC driver and native platform packages for the embedded chDB engine.</description>
  <url>https://github.com/chdb-io/chdb-java</url>

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

  <organization>
    <name>chDB</name>
    <url>https://chdb.io</url>
  </organization>

  <!--
    Central rejects a release without <scm>, <developers> and <licenses>. They are here rather
    than in the release profile because they describe the project whether or not it is being
    published, and a consumer reading the POM from a snapshot should see the same thing.
  -->
  <scm>
    <connection>scm:git:https://github.com/chdb-io/chdb-java.git</connection>
    <developerConnection>scm:git:git@github.com:chdb-io/chdb-java.git</developerConnection>
    <url>https://github.com/chdb-io/chdb-java</url>
    <tag>HEAD</tag>
  </scm>

  <developers>
    <developer>
      <id>chdb-io</id>
      <name>The chDB maintainers</name>
      <url>https://github.com/chdb-io</url>
      <organization>chDB</organization>
      <organizationUrl>https://chdb.io</organizationUrl>
    </developer>
  </developers>

  <issueManagement>
    <system>GitHub Issues</system>
    <url>https://github.com/chdb-io/chdb-java/issues</url>
  </issueManagement>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>

    <!-- Java 11 is the V1 floor (work plan section 2.1). Never raise without a plan change. -->
    <maven.compiler.release>11</maven.compiler.release>

    <!--
      Engine baseline. These three coordinates are the single source of truth for
      which chDB Core release this binding is built and tested against; scripts/engine.properties
      mirrors them for the shell/CMake side. Changing engine.version requires a new
      Maven version (work plan section 4.3) and a full platform re-test.
    -->
    <chdb.engine.version>26.7.3</chdb.engine.version>
    <chdb.binding.revision>1</chdb.binding.revision>
    <!-- Bumped only on an incompatible change to the Java <-> JNI shim contract. -->
    <chdb.jni.abi.version>2</chdb.jni.abi.version>
    <!-- Bumped only on an incompatible change to the public Java API. -->
    <chdb.java.api.version>1</chdb.java.api.version>

    <junit.version>5.10.2</junit.version>
    <surefire.version>3.2.5</surefire.version>
    <failsafe.version>3.2.5</failsafe.version>
  </properties>

  <modules>
    <module>chdb-bom</module>
    <module>chdb-jdbc</module>
    <module>chdb-native-macos-aarch64</module>
    <module>chdb-native-macos-x86_64</module>
    <module>chdb-native-linux-x86_64-gnu</module>
    <module>chdb-native-linux-aarch64-gnu</module>
    <module>chdb-integration-tests</module>
    <module>chdb-examples</module>
  </modules>

  <dependencyManagement>
    <dependencies>
      <dependency>
        <groupId>org.junit</groupId>
        <artifactId>junit-bom</artifactId>
        <version>${junit.version}</version>
        <type>pom</type>
        <scope>import</scope>
      </dependency>
    </dependencies>
  </dependencyManagement>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-compiler-plugin</artifactId>
          <version>3.13.0</version>
          <configuration>
            <compilerArgs>
              <arg>-Xlint:all</arg>
              <!-- The JDBC interfaces we implement are stable; serial/this-escape noise is not useful. -->
              <arg>-Xlint:-serial</arg>
            </compilerArgs>
          </configuration>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>${surefire.version}</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-failsafe-plugin</artifactId>
          <version>${failsafe.version}</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-jar-plugin</artifactId>
          <version>3.4.1</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-source-plugin</artifactId>
          <version>3.3.1</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-javadoc-plugin</artifactId>
          <version>3.6.3</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-antrun-plugin</artifactId>
          <version>3.1.0</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-resources-plugin</artifactId>
          <version>3.3.1</version>
        </plugin>
        <plugin>
          <groupId>org.codehaus.mojo</groupId>
          <artifactId>exec-maven-plugin</artifactId>
          <version>3.2.0</version>
        </plugin>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-gpg-plugin</artifactId>
          <version>3.2.8</version>
        </plugin>
        <plugin>
          <groupId>org.sonatype.central</groupId>
          <artifactId>central-publishing-maven-plugin</artifactId>
          <version>0.11.0</version>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

  <profiles>
    <!--
      Everything a Maven Central release needs and an ordinary build must not pay for: signing
      (which prompts for a passphrase), and the publishing plugin (which talks to Sonatype).
      The source and javadoc jars Central also requires are attached per module, because what
      "sources" means differs between the driver and a package whose content is two shared
      libraries — see the release profile in each module.

          mvn -Prelease deploy

      Requires a `central` server entry in settings.xml holding the portal token, and a GPG
      key whose public half is on a keyserver. docs/publishing.md is the runbook.
    -->
    <profile>
      <id>release</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-gpg-plugin</artifactId>
            <executions>
              <execution>
                <id>sign-artifacts</id>
                <phase>verify</phase>
                <goals>
                  <goal>sign</goal>
                </goals>
                <configuration>
                  <!--
                    Loopback pinentry so the passphrase can come from a CI secret rather than a
                    terminal. Harmless interactively: gpg-agent still caches as usual.
                  -->
                  <gpgArguments>
                    <arg>--pinentry-mode</arg>
                    <arg>loopback</arg>
                  </gpgArguments>
                </configuration>
              </execution>
            </executions>
          </plugin>
          <plugin>
            <groupId>org.sonatype.central</groupId>
            <artifactId>central-publishing-maven-plugin</artifactId>
            <extensions>true</extensions>
            <configuration>
              <publishingServerId>central</publishingServerId>
              <!--
                Deliberately not automatic. A release here is ~550 MB across six artifacts and
                cannot be unpublished; a human confirming the bundle in the portal is worth the
                extra step, at least until several releases have gone out uneventfully.
              -->
              <autoPublish>false</autoPublish>
              <!--
                Wait for Sonatype's validation and report the result, rather than uploading and
                returning. VALIDATED is also the plugin's default; it is written out because
                the release workflow's success is taken to mean "the bundle is valid and
                waiting", and that should not depend on a default.

                This replaces a waitUntilValidated element, which is not a parameter of
                central-publishing-maven-plugin 0.11.0 — the mojo declares waitUntil,
                waitMaxTime, waitPollingInterval and waitForPublishCompletion, and nothing
                named waitUntilValidated. Maven drops configuration elements a mojo does not
                declare rather than failing on them, so it had been doing nothing at all.
              -->
              <waitUntil>VALIDATED</waitUntil>
            </configuration>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>
</project>