danipa-java-sdk
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>com.danipa</groupId>
<artifactId>danipa-java-sdk</artifactId>
<version>0.2.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>
<groupId>com.danipa</groupId>
<artifactId>danipa-java-sdk</artifactId>
<version>0.2.0</version>
<packaging>jar</packaging>
<name>Danipa Java SDK</name>
<description>Java client for the Danipa Fintech API.</description>
<url>https://github.com/Danipa/java-sdk</url>
<licenses>
<license>
<name>MIT</name>
<url>https://opensource.org/licenses/MIT</url>
</license>
</licenses>
<developers>
<developer>
<name>Danipa</name>
<email>developers@danipa.com</email>
<organization>Danipa Business Systems</organization>
<organizationUrl>https://danipa.com</organizationUrl>
</developer>
</developers>
<scm>
<connection>scm:git:git://github.com/Danipa/java-sdk.git</connection>
<developerConnection>scm:git:ssh://git@github.com/Danipa/java-sdk.git</developerConnection>
<url>https://github.com/Danipa/java-sdk</url>
</scm>
<issueManagement>
<system>GitHub</system>
<url>https://github.com/Danipa/java-sdk/issues</url>
</issueManagement>
<properties>
<maven.compiler.source>17</maven.compiler.source>
<maven.compiler.target>17</maven.compiler.target>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<jackson.version>2.18.2</jackson.version>
<junit.version>5.11.3</junit.version>
<!-- Overridden to "true" by the publish workflow on final java-v<X.Y.Z>
tags; pre-release tags and local runs leave the deployment in the
Sonatype Central Portal as a manual-publish bundle. -->
<central.autoPublish>false</central.autoPublish>
</properties>
<dependencies>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>${jackson.version}</version>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.datatype</groupId>
<artifactId>jackson-datatype-jsr310</artifactId>
<version>${jackson.version}</version>
</dependency>
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.13.0</version>
</plugin>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.5.2</version>
</plugin>
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
<version>0.8.13</version>
<executions>
<execution>
<id>jacoco-prepare</id>
<goals>
<goal>prepare-agent</goal>
</goals>
<configuration>
<!-- DefaultHttpTransport is a thin adapter over java.net.http.HttpClient;
it requires an integration test (real socket) to exercise. Excluded
from unit coverage the same way Stripe excludes HttpURLConnectionClient. -->
<excludes>
<exclude>com/danipa/sdk/DefaultHttpTransport.class</exclude>
</excludes>
</configuration>
</execution>
<execution>
<id>jacoco-report</id>
<phase>verify</phase>
<goals>
<goal>report</goal>
</goals>
</execution>
<execution>
<id>jacoco-check</id>
<phase>verify</phase>
<goals>
<goal>check</goal>
</goals>
<configuration>
<excludes>
<exclude>com/danipa/sdk/DefaultHttpTransport.class</exclude>
</excludes>
<rules>
<rule>
<element>BUNDLE</element>
<limits>
<limit>
<counter>INSTRUCTION</counter>
<value>COVEREDRATIO</value>
<minimum>0.80</minimum>
</limit>
<limit>
<counter>BRANCH</counter>
<value>COVEREDRATIO</value>
<minimum>0.80</minimum>
</limit>
</limits>
</rule>
</rules>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<profiles>
<!-- Release profile: produces sources + javadoc jars, GPG-signs every
artifact, and uploads the bundle to the Sonatype Central Portal.
Activated by the publish workflow with `mvn -P release deploy`. -->
<profile>
<id>release</id>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>3.3.1</version>
<executions>
<execution>
<id>attach-sources</id>
<goals>
<goal>jar-no-fork</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>3.11.2</version>
<executions>
<execution>
<id>attach-javadocs</id>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
<configuration>
<source>17</source>
<!-- Loose doclint so missing param/return tags on
hand-rolled DTOs don't fail the release; the
JAR is still required by Maven Central. -->
<doclint>none</doclint>
<quiet>true</quiet>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>3.2.7</version>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
<configuration>
<!-- loopback pinentry: required when the
passphrase is fed via env var in CI
and there's no interactive TTY. -->
<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>
<version>0.9.0</version>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<autoPublish>${central.autoPublish}</autoPublish>
<!-- Block the build until the portal has finished
server-side validation; if validation fails
we want CI red, not a silently-stuck bundle. -->
<waitUntil>validated</waitUntil>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>