<?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 https://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <parent>
        <groupId>ai.ravenroot</groupId>
        <artifactId>ravenroot-parent</artifactId>
        <version>0.1.0-alpha.1</version>
    </parent>

    <artifactId>ravenroot-persistence-sqlite</artifactId>
    <name>Ravenroot SQLite Execution Store</name>
    <description>Durable single-host SQLite/WAL adapter for the ADR 0010 execution-store port. Not included in the standalone server or the default distribution; an adopter must add this module and wire it explicitly to use it.</description>

    <dependencies>
        <dependency>
            <groupId>ai.ravenroot</groupId>
            <artifactId>ravenroot-application-api</artifactId>
        </dependency>
        <dependency>
            <groupId>org.xerial</groupId>
            <artifactId>sqlite-jdbc</artifactId>
            <version>${sqlite-jdbc.version}</version>
        </dependency>
        <dependency>
            <groupId>org.junit.jupiter</groupId>
            <artifactId>junit-jupiter</artifactId>
            <scope>test</scope>
        </dependency>
        <dependency>
            <groupId>ai.ravenroot</groupId>
            <artifactId>ravenroot-persistence-testkit</artifactId>
            <scope>test</scope>
        </dependency>
        <!-- Fuzzing the journal's digest-tamper detection.
             Version is managed by the parent, which already declares jqwik for ravenroot-core. -->
        <dependency>
            <groupId>net.jqwik</groupId>
            <artifactId>jqwik</artifactId>
            <scope>test</scope>
        </dependency>
    </dependencies>

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <configuration>
                    <!--
                        The kill test and the cross-process lease test launch a real second JVM and
                        hand it this JVM's classpath. Surefire's default manifest-only booter JAR
                        reduces java.class.path to a single synthetic JAR, which a forked child can
                        only resolve through that JAR's manifest Class-Path; making the real
                        classpath explicit removes a layer of indirection from tests whose entire
                        point is that a SIGKILL, not a classloading accident, is what ended the child.
                    -->
                    <useManifestOnlyJar>false</useManifestOnlyJar>
                </configuration>
            </plugin>
        </plugins>
    </build>
</project>
