pom.xml

<!--
SPDX-FileCopyrightText: 2026 Bernard Ladenthin <bernard.ladenthin@gmail.com>

SPDX-License-Identifier: Apache-2.0
-->

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

    <groupId>net.ladenthin</groupId>
    <artifactId>srcmorph-parent</artifactId>
    <version>1.2.0-SNAPSHOT</version>
    <packaging>pom</packaging>

    <name>${project.groupId}:${project.artifactId}</name>
    <description>Reactor parent for srcmorph: a prompt-driven source-tree transformer using local llama.cpp models, and its Maven plugin.</description>
    <url>https://github.com/bernardladenthin/srcmorph</url>

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

    <developers>
        <developer>
            <name>Bernard Ladenthin</name>
            <organization>ladenthin.net</organization>
        </developer>
    </developers>

    <scm>
        <connection>scm:git:https://github.com/bernardladenthin/srcmorph.git</connection>
        <developerConnection>scm:git:https://github.com/bernardladenthin/srcmorph.git</developerConnection>
        <url>https://github.com/bernardladenthin/srcmorph</url>
    </scm>

    <issueManagement>
        <system>GitHub Issues</system>
        <url>https://github.com/bernardladenthin/srcmorph/issues</url>
    </issueManagement>

    <distributionManagement>
        <snapshotRepository>
            <id>central</id>
            <url>https://central.sonatype.com/repository/maven-snapshots/</url>
        </snapshotRepository>
    </distributionManagement>

    <properties>
        <!--
            SonarCloud requires sonar.organization on the project the scanner actually analyzes.
            The SonarCloud scan runs at THIS reactor root (.github/workflows/sonarqube.yml calls
            `mvn ... sonar:sonar` with no -f, so the analyzed project is this parent POM), and a
            parent POM never sees its children's <properties>. Declaring it only in the child
            modules therefore left the root scan without it, failing with
            "You must define the following mandatory properties for '<projectKey>': sonar.organization".
            Kept in the child modules too (harmless) so a per-module scan would also carry it.
        -->
        <sonar.organization>bernardladenthin</sonar.organization>
        <!--
            Defined here (not only in srcmorph-cli/pom.xml) because this parent's own
            <dependencyManagement> below references it: child properties are never visible to a
            parent POM, so the version used by both jackson dependencyManagement entries must live
            at this level. srcmorph-cli/pom.xml does not redeclare it.
        -->
        <jackson.version>2.22.1</jackson.version>
        <!--
            SonarCloud requires sonar.organization on the project the scanner executes, which is
            this reactor root (srcmorph-parent) — child-module properties are not visible to the
            parent POM. The child modules also declare it for standalone/module-scoped runs; the
            projectKey stays a workflow -D argument (see .github/workflows/sonarqube.yml).
        -->
        <sonar.organization>bernardladenthin</sonar.organization>
    </properties>

    <!--
        Reactor modules. `srcmorph` is the extracted core library (config/document/indexer/prompt/
        provider/support — framework-free, no Maven plugin API); `srcmorph-cli` is the standalone
        JSON/YAML-driven CLI (fat jar deliverable) built on top of it; `srcmorph-maven-plugin`
        depends on the core library too and supplies only the Mojo entry points (renamed from
        `llamacpp-ai-index-maven-plugin` in the migration — goal prefix `srcmorph`, package
        `net.ladenthin.maven.srcmorph.mojo`, properties `srcmorph.*`).

        A fourth module, a minimal relocation-stub POM for the retired
        `net.ladenthin:llamacpp-ai-index-maven-plugin` coordinates (no <parent>, version-pinned at
        1.0.4, only a <distributionManagement><relocation> pointing at srcmorph-maven-plugin:1.1.1),
        was published to Maven Central and then removed from this reactor — the published artifact
        is permanent on Central regardless of what this repo's module list contains, and the
        relocation was verified working end-to-end (a clean-repo Maven resolution of the old
        coordinates correctly redirects to the new ones) before removal. There is nothing left for
        that module to do: it will never be re-released, so keeping it in the active reactor (and
        the `versions:set -Dexcludes=...` footgun that came with it) served no further purpose.
    -->
    <modules>
        <module>srcmorph</module>
        <module>srcmorph-cli</module>
        <module>srcmorph-maven-plugin</module>
    </modules>

    <dependencyManagement>
        <dependencies>
            <!--
                Converge slf4j-api: the llama dependency brings slf4j-api directly AND
                transitively (via logback-classic, which requests an older patch). Pin the
                higher version so maven-enforcer DependencyConvergence is satisfied.
            -->
            <dependency>
                <groupId>org.slf4j</groupId>
                <artifactId>slf4j-api</artifactId>
                <version>2.0.18</version>
            </dependency>
            <!--
                Pin logback-classic (runtime scope) so the runtime binding and the explicit
                test-scope declaration (used to attach a ListAppender in
                AiFieldGenerationSupportTest) stay converged. The managed version here wins over
                whatever the llama dependency brings in transitively, satisfying maven-enforcer's
                DependencyConvergence.
            -->
            <dependency>
                <groupId>ch.qos.logback</groupId>
                <artifactId>logback-classic</artifactId>
                <version>1.6.1</version>
            </dependency>
            <!--
                JSON/YAML binding for srcmorph-cli's CConfiguration. Both artifacts are pinned to the
                SAME jackson.version (declared in srcmorph-cli/pom.xml) because they ship from the same
                jackson release train and each transitively pulls jackson-core/jackson-annotations at a
                matching version — pinning them together here keeps maven-enforcer's
                dependencyConvergence rule satisfied without needing a separate jackson-core/
                jackson-annotations/snakeyaml pin (nothing else in the reactor depends on jackson or
                snakeyaml, so there is no other version to converge against).
            -->
            <dependency>
                <groupId>com.fasterxml.jackson.core</groupId>
                <artifactId>jackson-databind</artifactId>
                <version>${jackson.version}</version>
            </dependency>
            <dependency>
                <groupId>com.fasterxml.jackson.dataformat</groupId>
                <artifactId>jackson-dataformat-yaml</artifactId>
                <version>${jackson.version}</version>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <profiles>
        <!--
            Signs and publishes every reactor module in one `mvn -P release deploy` (the
            java-llama.cpp reactor pattern). GPG signing at verify + Central Portal publishing;
            autoPublish completes the deployment once portal validation passes.
        -->
        <profile>
            <id>release</id>
            <build>
                <plugins>
                    <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-gpg-plugin</artifactId>
                        <!-- No parent pluginManagement above this pom to inherit a default version
                             from; must match the pin in the plugin module's own pluginManagement. -->
                        <version>3.2.8</version>
                        <executions>
                            <execution>
                                <id>sign-artifacts</id>
                                <phase>verify</phase>
                                <goals><goal>sign</goal></goals>
                                <configuration>
                                    <keyname>${gpg.keyname}</keyname>
                                    <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>
                        <!-- No parent pluginManagement above this pom to inherit a default version
                             from; must match the pin in the plugin module's own pluginManagement. -->
                        <version>0.11.0</version>
                        <extensions>true</extensions>
                        <configuration>
                            <publishingServerId>central</publishingServerId>
                            <autoPublish>true</autoPublish>
                            <!-- validated: wait only for portal validation (where real errors surface), not the slow server-side publish; autoPublish completes it -->
                            <waitUntil>validated</waitUntil>
                            <!-- seconds; generous headroom for the validation poll (default 1800) -->
                            <waitMaxTime>21600</waitMaxTime>
                        </configuration>
                    </plugin>
                </plugins>
            </build>
        </profile>
    </profiles>
</project>