Description

<dependency>
    <groupId>net.ladenthin</groupId>
    <artifactId>llamacpp-ai-index-maven-plugin</artifactId>
    <version>1.0.4</version>
</dependency>

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

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

<!--
    Relocation stub for the retired net.ladenthin:llamacpp-ai-index-maven-plugin coordinates.

    This module is DELIBERATELY minimal: no <dependencies>, no source, no tests — only the
    coordinates plus the Maven Central <distributionManagement><relocation> block. A stray
    dependency here could confuse a build that resolves the old artifact, so keep this file
    exactly as small as it looks.

    IT DOES declare <parent> (unlike earlier drafts of this file), for one specific reason:
    without it, this module inherits neither the release profile's <maven-gpg-plugin> signing
    execution nor its <central-publishing-maven-plugin> binding, so `mvn -P release deploy` had
    nothing to sign or publish this pom-only artifact WITH — it would fall through to the plain
    Super-POM `maven-deploy-plugin:deploy` binding for `pom` packaging, which needs an explicit
    <distributionManagement><repository> that this file (correctly) does not declare, and would
    fail the whole reactor deploy the moment it reached this module. Inheriting <parent> fixes
    that: it pulls in the release profile (gpg-sign + central-publishing-maven-plugin), exactly
    like every other reactor module, so this artifact is signed and bundled into the same
    Central Publisher upload as srcmorph/srcmorph-cli/srcmorph-maven-plugin.

    Declaring <parent> does NOT tie this module's own <version> to the parent's: a child project
    may freely override <version> (and <artifactId>) — only omitting it inherits the parent's
    value. This module's <version> below stays pinned independently at 1.0.4, unaffected by the
    reactor's own version (currently 1.1.1 in ../pom.xml).

    That independence is NOT automatic against tooling, though: `mvn versions:set -DnewVersion=X`
    run from the repo root walks every module reachable via the root <modules> list — parent
    relationship or not — and rewrites each one's own <version> to X. This module must still be
    excluded explicitly on every such run:

        mvn versions:set -DnewVersion=X -DgenerateBackupPoms=false \
            -Dexcludes=net.ladenthin:llamacpp-ai-index-maven-plugin

    This artifact was published under net.ladenthin:llamacpp-ai-index-maven-plugin through
    1.0.4; the plugin now ships as net.ladenthin:srcmorph-maven-plugin (see
    ../srcmorph-maven-plugin/pom.xml). This stub exists only so a consumer still declaring the
    old coordinates is redirected by Maven to the new ones.
-->
<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>net.ladenthin</groupId>
        <artifactId>srcmorph-parent</artifactId>
        <version>1.1.1</version>
        <relativePath>../pom.xml</relativePath>
    </parent>

    <artifactId>llamacpp-ai-index-maven-plugin</artifactId>
    <!-- Deliberate override of the inherited parent version — see the comment above. -->
    <version>1.0.4</version>
    <packaging>pom</packaging>

    <name>llamacpp-ai-index-maven-plugin (relocated)</name>
    <description>Relocated. This artifact moved to net.ladenthin:srcmorph-maven-plugin; see the distributionManagement/relocation below.</description>

    <distributionManagement>
        <relocation>
            <groupId>net.ladenthin</groupId>
            <artifactId>srcmorph-maven-plugin</artifactId>
            <version>1.1.1</version>
        </relocation>
    </distributionManagement>
</project>