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>

  <!-- Parent is cfc-core's root/BOM pom, resolved from a Maven repository (Central or the local
       .m2 cache), not from a filesystem checkout: this module is not part of cfc-core's reactor.
       The empty <relativePath/> is required; it disables Maven's default lookup of ../pom.xml,
       so the build does not depend on where this checkout sits. -->
  <parent>
    <groupId>com.cloudforgeci</groupId>
    <artifactId>cfc-core</artifactId>
    <!-- Tracks cfc-core's latest published SNAPSHOT — kept current by sync-versions.yml. -->
    <version>3.3.11-SNAPSHOT</version>
    <relativePath/>
  </parent>

  <artifactId>cloudforge-localstack</artifactId>
  <!-- Kept in lockstep with the parent's version (unlike e.g. cloudforge-manager-deployment,
       which has its own independent release cadence): this module was a reactor member of
       cfc-core until it moved to its own repository, and stays released alongside it on the same
       version number, just via a <parent> reference instead of reactor membership. -->
  <version>3.3.11-SNAPSHOT</version>
  <packaging>jar</packaging>
  <name>CloudForge LocalStack</name>
  <description>LocalStack local deployment adapter, deployer, and pipeline for CloudForge templates</description>

  <!-- Overrides the parent's <url>/<scm>, which point at CloudForgeCI/cfc-core. <licenses>/
       <developers> are shared across CloudForgeCI modules and stay inherited. -->
  <url>https://github.com/CloudForgeCI/cloudforge-localstack</url>

  <scm>
    <connection>scm:git:https://github.com/CloudForgeCI/cloudforge-localstack.git</connection>
    <developerConnection>scm:git:ssh://git@github.com/CloudForgeCI/cloudforge-localstack.git</developerConnection>
    <url>https://github.com/CloudForgeCI/cloudforge-localstack</url>
  </scm>

  <properties>
    <aws.sdk.version>2.57.3</aws.sdk.version>
    <testcontainers.version>1.21.0</testcontainers.version>
  </properties>

  <!-- Maven doesn't check the Central Portal's snapshots URL by default — needed to resolve the
       parent POM above while cfc-core is on a -SNAPSHOT version. Release (non-SNAPSHOT) builds
       never use this repository. -->
  <repositories>
    <repository>
      <id>central-snapshots</id>
      <url>https://central.sonatype.com/repository/maven-snapshots/</url>
      <releases><enabled>false</enabled></releases>
      <!-- updatePolicy=always: without it, Maven caches a "not found" or stale result for a
           whole day (the default), and that negative cache persists across CI runs along with
           the rest of ~/.m2. A build that runs before cfc-core's own matching SNAPSHOT finishes
           publishing can then fail every build for the rest of the day even once it exists. -->
      <snapshots><enabled>true</enabled><updatePolicy>always</updatePolicy></snapshots>
    </repository>
  </repositories>

  <dependencies>
    <dependency>
      <groupId>com.cloudforgeci</groupId>
      <artifactId>cloudforge-core</artifactId>
    </dependency>
    <dependency>
      <groupId>com.fasterxml.jackson.core</groupId>
      <artifactId>jackson-databind</artifactId>
    </dependency>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>cloudformation</artifactId>
      <version>${aws.sdk.version}</version>
    </dependency>

    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>s3</artifactId>
      <version>${aws.sdk.version}</version>
    </dependency>

    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>cognitoidentityprovider</artifactId>
      <version>${aws.sdk.version}</version>
    </dependency>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>secretsmanager</artifactId>
      <version>${aws.sdk.version}</version>
    </dependency>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>ecs</artifactId>
      <version>${aws.sdk.version}</version>
    </dependency>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>ssm</artifactId>
      <version>${aws.sdk.version}</version>
    </dependency>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>rds</artifactId>
      <version>${aws.sdk.version}</version>
    </dependency>

    <dependency>
      <groupId>org.junit.jupiter</groupId>
      <artifactId>junit-jupiter</artifactId>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>org.testcontainers</groupId>
      <artifactId>testcontainers</artifactId>
      <version>${testcontainers.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>ec2</artifactId>
      <version>${aws.sdk.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>elasticloadbalancingv2</artifactId>
      <version>${aws.sdk.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>route53</artifactId>
      <version>${aws.sdk.version}</version>
      <scope>test</scope>
    </dependency>
    <dependency>
      <groupId>software.amazon.awssdk</groupId>
      <artifactId>acm</artifactId>
      <version>${aws.sdk.version}</version>
      <scope>test</scope>
    </dependency>
  </dependencies>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-compiler-plugin</artifactId>
      </plugin>
      <plugin>
        <artifactId>maven-surefire-plugin</artifactId>
        <configuration>
          <excludedGroups>localstack</excludedGroups>
        </configuration>
      </plugin>
      <!-- Coverage check deferred until deployer/runtime tests expand -->
      <plugin>
        <groupId>org.jacoco</groupId>
        <artifactId>jacoco-maven-plugin</artifactId>
        <executions>
          <execution>
            <id>check</id>
            <phase>none</phase>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

  <profiles>
    <profile>
      <id>localstack</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <configuration combine.self="override">
              <!-- Run full module test suite (unit + @Tag("localstack") integration) -->
            </configuration>
          </plugin>
        </plugins>
      </build>
    </profile>
    <!-- Publishes to Maven Central via the Central Portal. Defined here rather than inherited:
         cfc-core's flatten-maven-plugin strips <profiles> from the POM it publishes, so the
         parent resolved from Central has no "release" profile. Same shape as
         cloudforge-ministack's own copy of this profile. -->
    <profile>
      <id>release</id>
      <build>
        <pluginManagement>
          <plugins>
            <plugin>
              <groupId>org.apache.maven.plugins</groupId>
              <artifactId>maven-javadoc-plugin</artifactId>
              <version>3.12.0</version>
              <configuration>
                <doclint>none</doclint>
                <failOnError>false</failOnError>
              </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>
              <!-- Matches cfc-core root pom's pin (see its comment for why 3.2.8); keep them in
                   sync. -->
              <version>3.2.8</version>
              <executions>
                <execution>
                  <id>sign-artifacts</id>
                  <phase>verify</phase>
                  <goals><goal>sign</goal></goals>
                </execution>
              </executions>
            </plugin>
          </plugins>
        </pluginManagement>
        <plugins>
          <!-- Flattens the parent-inherited license/developers and this module's own
               unversioned dependencies (e.g. cloudforge-core, left to the parent's
               dependencyManagement) into the published pom. Central's validator rejects a pom it
               would have to resolve a parent to make sense of, same as it rejects one missing
               those fields outright. Same shape as cfc-core's own copy of this plugin. -->
          <plugin>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>flatten-maven-plugin</artifactId>
            <version>1.8.0</version>
            <configuration>
              <updatePomFile>true</updatePomFile>
              <flattenMode>bom</flattenMode>
              <flattenedPomFilename>${project.build.directory}/${project.artifactId}-${project.version}.pom</flattenedPomFilename>
            </configuration>
            <executions>
              <execution>
                <id>flatten</id>
                <phase>process-resources</phase>
                <goals><goal>flatten</goal></goals>
              </execution>
              <execution>
                <id>flatten.clean</id>
                <phase>clean</phase>
                <goals><goal>clean</goal></goals>
              </execution>
            </executions>
          </plugin>

          <!-- Central Portal publisher (replaces old OSSRH/staging) -->
          <plugin>
            <groupId>org.sonatype.central</groupId>
            <artifactId>central-publishing-maven-plugin</artifactId>
            <version>0.12.0</version>
            <extensions>true</extensions>
            <configuration>
              <publishingServerId>central</publishingServerId>
              <autoPublish>true</autoPublish>
              <waitUntil>validated</waitUntil>
              <centralSnapshotsUrl>https://central.sonatype.com/repository/maven-snapshots/</centralSnapshotsUrl>
            </configuration>
          </plugin>

          <!-- Attach sources -->
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-source-plugin</artifactId>
            <executions>
              <execution>
                <id>attach-sources</id>
                <phase>verify</phase>
                <goals><goal>jar</goal></goals>
              </execution>
            </executions>
          </plugin>

          <!-- Attach javadocs -->
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-javadoc-plugin</artifactId>
            <executions>
              <execution><id>attach-javadocs</id><goals><goal>jar</goal></goals></execution>
            </executions>
            <configuration><failOnError>false</failOnError></configuration>
          </plugin>

          <!-- GPG signing (Central requires .asc) -->
          <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>
              </execution>
            </executions>
            <configuration>
              <gpgArguments>
                <arg>--pinentry-mode</arg><arg>loopback</arg>
              </gpgArguments>
              <homedir>${env.GPG_HOMEDIR}</homedir>
            </configuration>
          </plugin>

          <!-- Skip the default deploy plugin, which would otherwise fail with "repository element
               was not specified in the POM inside distributionManagement"; publishing is done by
               central-publishing-maven-plugin. -->
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-deploy-plugin</artifactId>
            <configuration><skip>true</skip></configuration>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>
</project>