datalogic
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>io.github.goplasmatic</groupId>
<artifactId>datalogic</artifactId>
<version>5.1.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>io.github.goplasmatic</groupId>
<artifactId>datalogic</artifactId>
<version>5.1.0</version>
<packaging>jar</packaging>
<name>datalogic</name>
<description>Java/JVM bindings for datalogic-rs — a JSONLogic (json-logic) rules engine with a native Rust core via the Java FFM API (java.lang.foreign). Compile once, evaluate in nanoseconds; identical semantics across Java, Kotlin, Scala, .NET, Python, Go, Node.js, WASM, PHP, and Rust.</description>
<url>https://github.com/GoPlasmatic/datalogic-rs</url>
<licenses>
<license>
<name>Apache License, Version 2.0</name>
<url>https://www.apache.org/licenses/LICENSE-2.0.txt</url>
</license>
</licenses>
<developers>
<developer>
<name>Plasmatic</name>
<organization>Plasmatic</organization>
<organizationUrl>https://github.com/GoPlasmatic</organizationUrl>
</developer>
</developers>
<scm>
<connection>scm:git:https://github.com/GoPlasmatic/datalogic-rs.git</connection>
<developerConnection>scm:git:ssh://git@github.com/GoPlasmatic/datalogic-rs.git</developerConnection>
<url>https://github.com/GoPlasmatic/datalogic-rs</url>
</scm>
<properties>
<!-- JDK 22 is the floor: the binding speaks to libdatalogic_c
through the java.lang.foreign (FFM) API, final since 22.
No JNA, no JNI glue — the JDK is the FFI runtime. -->
<maven.compiler.release>22</maven.compiler.release>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<jackson.version>2.22.1</jackson.version>
<junit.version>5.14.4</junit.version>
</properties>
<dependencies>
<!-- Jackson for JSON-string marshalling at the boundary. Most
Java users have Jackson already; if not, the Maven Central
footprint is well-understood. -->
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</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>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.13.0</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.5.2</version>
<configuration>
<!-- In-tree dev: surface the C ABI's cargo target
dir so the FFM loader can resolve
libdatalogic_c.* without the classpath-root
<os-arch>/ JAR layout (the release workflow
stages those at packaging time; locally they're
absent on a fresh clone). -->
<systemPropertyVariables>
<datalogic.library.path>${project.basedir}/../c/target/release</datalogic.library.path>
</systemPropertyVariables>
<!-- FFM downcalls/upcalls are "restricted methods":
JDK 24+ warns (and will eventually deny) unless
native access is granted explicitly. -->
<argLine>--enable-native-access=ALL-UNNAMED</argLine>
</configuration>
</plugin>
<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>
<configuration>
<doclint>none</doclint>
</configuration>
<executions>
<execution>
<id>attach-javadocs</id>
<goals><goal>jar</goal></goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
<profiles>
<!-- Activated by `mvn -P release deploy` in publish-jvm. Adds
GPG signing + Sonatype Central Portal upload. Kept profile-
gated so local `mvn package` doesn't try to sign / publish. -->
<profile>
<id>release</id>
<build>
<plugins>
<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>
<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>
<!-- 0.8.0+ tolerates the Central Portal API's added
`warnings` response field; 0.7.0 crashed
deserializing it *after* a successful publish,
reporting a false failure. -->
<version>0.11.0</version>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<autoPublish>true</autoPublish>
<waitUntil>published</waitUntil>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>