api-log-spring-boot-starter
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>kr.devslab</groupId>
<artifactId>api-log-spring-boot-starter</artifactId>
<version>0.4.0</version>
</dependency><?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>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>3.5.6</version>
<relativePath/>
</parent>
<groupId>kr.devslab</groupId>
<artifactId>api-log-spring-boot-starter</artifactId>
<version>0.4.0</version>
<packaging>jar</packaging>
<name>API Log Spring Boot Starter</name>
<description>Event-driven API call logging for Spring Boot — async event pipeline with PostgreSQL JSONB storage.</description>
<url>https://github.com/devslab-kr/api-log</url>
<inceptionYear>2026</inceptionYear>
<licenses>
<license>
<name>The Apache License, Version 2.0</name>
<url>https://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
<organization>
<name>Devslab</name>
<url>https://devslab.kr</url>
</organization>
<developers>
<developer>
<id>devslab</id>
<name>Devslab</name>
<email>support@devslab.kr</email>
<url>https://devslab.kr</url>
<organization>Devslab</organization>
<organizationUrl>https://devslab.kr</organizationUrl>
</developer>
</developers>
<scm>
<connection>scm:git:https://github.com/devslab-kr/api-log.git</connection>
<developerConnection>scm:git:ssh://git@github.com/devslab-kr/api-log.git</developerConnection>
<url>https://github.com/devslab-kr/api-log</url>
<tag>HEAD</tag>
</scm>
<issueManagement>
<system>GitHub</system>
<url>https://github.com/devslab-kr/api-log/issues</url>
</issueManagement>
<properties>
<java.version>21</java.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<flyway.version>11.13.1</flyway.version>
<testcontainers.version>1.21.3</testcontainers.version>
</properties>
<dependencies>
<!-- Core: JPA repository + RestClient (Web) for the HTTP client utility -->
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-data-jpa</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
</dependency>
<!-- Retry: re-tries are reported back as RETRY_ERROR events -->
<dependency>
<groupId>org.springframework.retry</groupId>
<artifactId>spring-retry</artifactId>
</dependency>
<!-- Jackson Blackbird: high-throughput JSON for the JSONB payloads -->
<dependency>
<groupId>com.fasterxml.jackson.module</groupId>
<artifactId>jackson-module-blackbird</artifactId>
</dependency>
<!-- PostgreSQL JDBC driver — runtime only; this starter is PostgreSQL-specific (JSONB) -->
<dependency>
<groupId>org.postgresql</groupId>
<artifactId>postgresql</artifactId>
<scope>runtime</scope>
</dependency>
<!--
Flyway is OPTIONAL. The consumer must add it themselves if they want
api.log.schema.management=flyway. The starter compiles against the
FluentConfiguration class so its FlywayConfigurationCustomizer bean
can reference it, but with <optional>true</optional> we don't force
Flyway onto consumers' classpaths or transitive dependency graphs.
When the consumer uses Liquibase, manual DDL, or their own migration
flow, this starter stays out of their way.
-->
<dependency>
<groupId>org.flywaydb</groupId>
<artifactId>flyway-core</artifactId>
<version>${flyway.version}</version>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.flywaydb</groupId>
<artifactId>flyway-database-postgresql</artifactId>
<version>${flyway.version}</version>
<scope>runtime</scope>
<optional>true</optional>
</dependency>
<!-- Build-time only -->
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-configuration-processor</artifactId>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<optional>true</optional>
</dependency>
<!-- Test -->
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-testcontainers</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.testcontainers</groupId>
<artifactId>testcontainers</artifactId>
<version>${testcontainers.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.testcontainers</groupId>
<artifactId>junit-jupiter</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.testcontainers</groupId>
<artifactId>postgresql</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>com.h2database</groupId>
<artifactId>h2</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<annotationProcessorPaths>
<path>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-configuration-processor</artifactId>
</path>
<path>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
</path>
</annotationProcessorPaths>
</configuration>
</plugin>
</plugins>
</build>
<profiles>
<!--
Activated only during the Release workflow (./mvnw -P release deploy).
Adds the sources/javadoc jars, GPG signing, and the Central Portal
publishing plugin — all required for Maven Central but unnecessary
(and slow) for normal local builds.
-->
<profile>
<id>release</id>
<build>
<plugins>
<!-- Sources jar -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-sources</id>
<goals><goal>jar-no-fork</goal></goals>
</execution>
</executions>
</plugin>
<!-- Javadoc jar (Xdoclint:none → tolerate light doc gaps in release-time docs) -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<doclint>none</doclint>
<source>21</source>
</configuration>
<executions>
<execution>
<id>attach-javadocs</id>
<goals><goal>jar</goal></goals>
</execution>
</executions>
</plugin>
<!-- GPG signing — credentials come from the release.yml workflow env -->
<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>
<!-- Pinentry mode "loopback" lets the workflow pipe the passphrase via gpg-passphrase env -->
<gpgArguments>
<arg>--pinentry-mode</arg>
<arg>loopback</arg>
</gpgArguments>
</configuration>
</execution>
</executions>
</plugin>
<!-- Sonatype Central Portal publishing (replaces the legacy OSSRH/nexus-staging) -->
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<version>0.6.0</version>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<autoPublish>true</autoPublish>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>