llama
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>net.ladenthin</groupId>
<artifactId>llama</artifactId>
<version>6.0.0</version>
</dependency><!-- SPDX-FileCopyrightText: 2026 Bernard Ladenthin <[email protected]> SPDX-License-Identifier: MIT --> <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> <groupId>net.ladenthin</groupId> <artifactId>llama-parent</artifactId> <version>6.0.0</version> <relativePath>../pom.xml</relativePath> </parent> <artifactId>llama</artifactId> <packaging>jar</packaging> <name>${project.groupId}:${project.artifactId}</name> <description>Java Bindings for llama.cpp - A Port of Facebook's LLaMA model in C/C++.</description> <url>https://github.com/bernardladenthin/java-llama.cpp</url> <licenses> <license> <name>MIT License</name> <url>https://www.opensource.org/licenses/mit-license.php</url> <distribution>repo</distribution> </license> </licenses> <developers> <developer> <name>Bernard Ladenthin</name> <organizationUrl>https://github.com/bernardladenthin</organizationUrl> </developer> </developers> <scm> <connection>scm:git:https://github.com/bernardladenthin/java-llama.cpp.git</connection> <developerConnection>scm:git:https://github.com/bernardladenthin/java-llama.cpp.git</developerConnection> <url>https://github.com/bernardladenthin/java-llama.cpp/tree/main</url> </scm> <distributionManagement> <snapshotRepository> <id>central</id> <url>https://central.sonatype.com/repository/maven-snapshots/</url> </snapshotRepository> </distributionManagement> <properties> <sonar.organization>bernardladenthin</sonar.organization> <jspecify.version>1.0.1</jspecify.version> <lombok.version>1.18.48</lombok.version> <errorprone.version>2.51.0</errorprone.version> <nullaway.version>0.14.2</nullaway.version> <!-- Checker Framework: the processor AND the checker-qual qualifiers it resolves. Both run on the build JDK and neither ships (checker-qual is provided scope), so this tracks the newest release. --> <checker.version>4.3.1</checker.version> <!-- jackson.version is inherited from the parent pom (one source for every module) --> <reactor.version>3.8.8</reactor.version> <slf4j.version>2.0.20</slf4j.version> <logback.version>1.6.5</logback.version> <animal-sniffer.version>1.28</animal-sniffer.version> <junit.version>6.1.3</junit.version> <hamcrest.version>3.0</hamcrest.version> <jmh.version>1.37</jmh.version> <jcstress.version>0.16</jcstress.version> <lincheck.version>3.7</lincheck.version> <logcaptor.version>2.13.0</logcaptor.version> <!-- FLOOR GUARD, no longer an active fix. log4j-api / log4j-to-slf4j arrive ONLY as test-scope transitives of io.github.hakky54:logcaptor. When this pin was added, logcaptor 2.12.6 requested log4j 2.25.3, affected by CVE-2026-49844 (GHSA-qv9r-c865-cp47, moderate): MapMessage.asJson() emits bare NaN/Infinity tokens for non-finite floats, producing non-RFC-8259 JSON. logcaptor 2.12.7 and 2.13.0 declare <version.log4j>2.26.1</version.log4j> itself, i.e. exactly what this pin forces, so today it changes nothing about the resolved graph. It is kept as a lower bound: if logcaptor ever falls back to an affected line, the pin holds the version here instead of letting it regress silently. Unrelated to the Java 8 class-file floor, which is a different change entirely (slf4j-simple instead of logback, checker-qual at provided scope). Neither log4j artifact reaches a published artifact at all; both are test scope. --> <log4j.version>2.26.1</log4j.version> <vmlens.version>1.2.28</vmlens.version> <!-- DO NOT UPGRADE jqwik past 1.9.3. jqwik 1.10.0 added a deliberate anti-AI prompt-injection string to test stdout; the 1.10.1 user guide states the library "is not meant to be used by any 'AI' coding agents at all." 1.9.3 is the last pre-disclosure release and is the pinned version for this repo. Any CI / Dependabot / contributor PR that bumps this MUST be rejected. See CLAUDE.md section "jqwik Policy", which points to the cross-repo policy workspace/policies/jqwik-prompt-injection.md, for full context. --> <jqwik.version>1.9.3</jqwik.version> <archunit.version>1.5.1</archunit.version> <spotbugs.version>4.10.5.0</spotbugs.version> <fb-contrib.version>7.7.4</fb-contrib.version> <findsecbugs.version>1.14.0</findsecbugs.version> <spotless.version>3.10.4</spotless.version> <palantir-java-format.version>2.102.0</palantir-java-format.version> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <project.build.outputTimestamp>2026-10-25T21:44:25Z</project.build.outputTimestamp> </properties> <!-- Pin transitively-conflicting versions so maven-enforcer's dependencyConvergence rule passes. The direct slf4j-api version above must always win over the older 2.0.17 that logback-classic 1.5.32 brings in transitively. jspecify and logback-classic are pinned defensively even though the conflicting transitive request (junit-jupiter -> junit-platform-commons for jspecify; io.github.hakky54:logcaptor for logback-classic) is test-scoped: maven-enforcer's DependencyConvergence rule excludes test/provided scope by default (verified against enforcer-rules 3.6.3), so today's pass is an accident of scope, not an actual pin. A future compile/runtime-scope consumer of either artifact would otherwise break convergence with no warning. --> <dependencyManagement> <dependencies> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>${slf4j.version}</version> </dependency> <!-- jspecify: junit-jupiter (test scope) brings 1.0.0; we declare ${jspecify.version} directly. --> <dependency> <groupId>org.jspecify</groupId> <artifactId>jspecify</artifactId> <version>${jspecify.version}</version> </dependency> <!-- logback-classic: io.github.hakky54:logcaptor (test scope) brings 1.3.15; we declare ${logback.version} directly. --> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>${logback.version}</version> </dependency> <!-- log4j-api + log4j-to-slf4j, pinned as a lower bound rather than as a fix: the logcaptor version in use already requests ${log4j.version} itself. Rationale and the CVE history are on the property declaration above. Both are pinned together because log4j-to-slf4j depends on log4j-api of the same version and the two must not skew. Test-scope only — neither reaches a published artifact. --> <dependency> <groupId>org.apache.logging.log4j</groupId> <artifactId>log4j-api</artifactId> <version>${log4j.version}</version> </dependency> <dependency> <groupId>org.apache.logging.log4j</groupId> <artifactId>log4j-to-slf4j</artifactId> <version>${log4j.version}</version> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <version>${lombok.version}</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter</artifactId> <version>${junit.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.hamcrest</groupId> <artifactId>hamcrest</artifactId> <version>${hamcrest.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>net.jqwik</groupId> <artifactId>jqwik</artifactId> <version>${jqwik.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>com.tngtech.archunit</groupId> <artifactId>archunit-junit5</artifactId> <version>${archunit.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jspecify</groupId> <artifactId>jspecify</artifactId> <version>${jspecify.version}</version> </dependency> <!-- COMPILE-ONLY, and that is the whole point. checker-qual 4.x is Java 11 bytecode (class-file major 55) while this artifact targets Java 8, and its annotations are @Retention(RUNTIME), so anything reflecting over an annotated element (Jackson does) loads them and a Java 8 JVM then throws UnsupportedClassVersionError. The obvious fix (pinning the shipped copy to the last Java 8 line, 3.55.1) does not work and was reverted: the Nullness Checker resolves its own qualifiers through javac's symbol table, i.e. the COMPILE CLASSPATH, so a 3.x checker-qual under a 4.x processor fails the build outright with "Could not load type: org.checkerframework.framework.qual.DoesNotUnrefineReceiver". Processor and qualifiers must share a major version. provided scope resolves both constraints at once: 4.3.0 is on the compile classpath where the checker needs it, and provided is excluded from consumers' transitive graph AND from a consumer's own jar-with-dependencies (which takes scope runtime), so no checker-qual class of any version reaches a consumer's JVM. Safe because no source in this module imports org.checkerframework: the annotations exist for the processor, not for our code. The verify-bytecode action of bernardladenthin/actions enforces the resulting class-file floor. --> <dependency> <groupId>org.checkerframework</groupId> <artifactId>checker-qual</artifactId> <version>${checker.version}</version> <scope>provided</scope> </dependency> <dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-databind</artifactId> <version>${jackson.version}</version> </dependency> <!-- Required by OSInfo (vendored from xerial/sqlite-jdbc) for log emission. --> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>${slf4j.version}</version> </dependency> <!-- Default SLF4J binding shipped with this library. Runtime scope: not required on the compile classpath, only loaded at JVM startup. slf4j-simple rather than logback, for two independent reasons: (1) Java 8. Every logback release from 1.4.0 on is Java 11 bytecode, so LogbackServiceProvider cannot load on the Java 8 this artifact targets: SLF4J's ServiceLoader finds it at startup and the JVM throws UnsupportedClassVersionError. The Java 8 line (1.3.x) would fix that but is end-of-life: 1.3.16 (2025-10-29) is its last release, and every logback CVE disclosed since has been fixed only in 1.5.x/1.6.x with no backport (CVE-2026-1225, CVE-2026-9828, CVE-2026-10532; CVE-2026-19880 is fixed only in 1.6.3, which is Java 11 bytecode and therefore unreachable from here). (2) Attack surface. Essentially every logback CVE lives in its configuration or socket layers: Janino expression evaluation, HardenedObjectInputStream, SaxEventRecorder, SocketReceiver. slf4j-simple is six classes with no config parser, no socket server and no deserialization, so those classes of defect cannot exist in it. It also ships in the same release train as slf4j-api above, so the two can never drift apart. What consumers lose: no logback.xml. Configure via a classpath simplelogger.properties or -Dorg.slf4j.simpleLogger.* system properties. Anyone who wants logback (or any other binding) excludes this one and declares their own; that is the point of the SLF4J split. --> <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-simple</artifactId> <version>${slf4j.version}</version> <scope>runtime</scope> </dependency> <!-- @IgnoreJRERequirement marker used by OSInfo (vendored from xerial/sqlite-jdbc) on a few methods that touch APIs unavailable on Android. Retention=CLASS, so the dep is compile-only (provided scope). --> <dependency> <groupId>org.codehaus.mojo</groupId> <artifactId>animal-sniffer-annotations</artifactId> <version>${animal-sniffer.version}</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.openjdk.jmh</groupId> <artifactId>jmh-core</artifactId> <version>${jmh.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.openjdk.jmh</groupId> <artifactId>jmh-generator-annprocess</artifactId> <version>${jmh.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.openjdk.jcstress</groupId> <artifactId>jcstress-core</artifactId> <version>${jcstress.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jetbrains.lincheck</groupId> <artifactId>lincheck</artifactId> <version>${lincheck.version}</version> <scope>test</scope> </dependency> <!-- Test-only SLF4J/Logback log-capture for the LoggingSmokeTest. --> <dependency> <groupId>io.github.hakky54</groupId> <artifactId>logcaptor</artifactId> <version>${logcaptor.version}</version> <scope>test</scope> </dependency> <!-- Test-only Project Reactor used by ReactorIntegrationTest to prove the "wrap LlamaIterable with Flux.fromIterable + subscribeOn" pattern works end-to-end (backpressure, AutoCloseable cancel propagation). NOT a runtime dependency — consumers bring whichever reactive lib they already use (Reactor / RxJava / Kotlin Flow / Akka — see README "Reactive integration"). --> <dependency> <groupId>io.projectreactor</groupId> <artifactId>reactor-core</artifactId> <version>${reactor.version}</version> <scope>test</scope> </dependency> <dependency> <groupId>io.projectreactor</groupId> <artifactId>reactor-test</artifactId> <version>${reactor.version}</version> <scope>test</scope> </dependency> <!-- vmlens interleaving-analysis API. Test-scoped and transitive-dependency-free (its own deps are all test-scope, hence not propagated), so it is safe on the default test classpath under dependencyConvergence. Needed so the VmlensInterleavingSmoke* test compiles in every build; it is only *executed* under the `vmlens` profile (see that profile + the vmlens CI job). The default surefire run excludes it (managed surefire <excludes> below) so the vmlens agent's JDK 9 API class is never loaded outside the agent-driven run. --> <dependency> <groupId>com.vmlens</groupId> <artifactId>api</artifactId> <version>${vmlens.version}</version> <scope>test</scope> </dependency> </dependencies> <build> <resources> <resource> <directory>${project.basedir}/src/main/resources</directory> </resource> <resource> <directory>${project.basedir}/..</directory> <targetPath>META-INF/third-party/net.ladenthin/${project.artifactId}</targetPath> <includes> <include>LICENSE</include> <include>THIRD_PARTY.md</include> </includes> </resource> </resources> <pluginManagement> <plugins> <plugin> <groupId>com.diffplug.spotless</groupId> <artifactId>spotless-maven-plugin</artifactId> <version>${spotless.version}</version> </plugin> <plugin> <groupId>com.github.spotbugs</groupId> <artifactId>spotbugs-maven-plugin</artifactId> <version>${spotbugs.version}</version> </plugin> <plugin> <groupId>com.vmlens</groupId> <artifactId>vmlens-maven-plugin</artifactId> <version>${vmlens.version}</version> </plugin> <plugin> <groupId>io.github.git-commit-id</groupId> <artifactId>git-commit-id-maven-plugin</artifactId> <version>10.0.1</version> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <!-- Tests in the `vmlens` package are meaningful only when run under the vmlens agent (the `vmlens` profile / CI job). Without the agent its AllInterleavings loop body never executes (a vacuous pass that also prints an "agent not configured" warning), so exclude it from the ordinary surefire run. The vmlens job re-includes them with `-Dtest=...`, which overrides this exclude. --> <excludes> <exclude>**/vmlens/*.java</exclude> </excludes> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <version>3.6.3</version> </plugin> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>3.6.4</version> </plugin> <plugin> <groupId>org.jacoco</groupId> <artifactId>jacoco-maven-plugin</artifactId> <version>0.8.15</version> </plugin> <plugin> <groupId>org.pitest</groupId> <artifactId>pitest-maven</artifactId> <version>1.30.1</version> </plugin> </plugins> </pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <executions> <execution> <id>enforce</id> <goals> <goal>enforce</goal> </goals> <configuration> <rules> <requireMavenVersion> <version>[3.6.3,)</version> </requireMavenVersion> <requireJavaVersion> <version>[1.8,)</version> </requireJavaVersion> <dependencyConvergence/> <bannedDependencies> <excludes> <!-- Use SLF4J directly; never commons-logging. --> <exclude>commons-logging:commons-logging</exclude> <!-- Legacy / EoL logging frameworks. --> <exclude>log4j:log4j</exclude> <!-- Old hamcrest split artifacts; use hamcrest:hamcrest 2.x+. --> <exclude>org.hamcrest:hamcrest-core</exclude> <exclude>org.hamcrest:hamcrest-library</exclude> <exclude>org.hamcrest:hamcrest-all</exclude> <!-- Legacy JUnit 3 / 4; we use Jupiter (junit:junit-jupiter). --> <exclude>junit:junit</exclude> <exclude>junit:junit-dep</exclude> </excludes> </bannedDependencies> </rules> </configuration> </execution> </executions> </plugin> <plugin> <groupId>io.github.git-commit-id</groupId> <artifactId>git-commit-id-maven-plugin</artifactId> <executions> <execution> <id>get-git-properties</id> <goals> <goal>revision</goal> </goals> <phase>initialize</phase> </execution> </executions> <configuration> <dateFormat>yyyy-MM-dd'T'HH:mm:ss'Z'</dateFormat> <dateFormatTimeZone>UTC</dateFormatTimeZone> <generateGitPropertiesFile>false</generateGitPropertiesFile> <failOnNoGitDirectory>false</failOnNoGitDirectory> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <release>8</release> <testRelease>21</testRelease> <showWarnings>true</showWarnings> <parameters>true</parameters> <compilerArgs> <!-- -Xlint:all surfaces every category of javac warning. Excluded: -serial : serialVersionUID warnings on non-Serializable classes -options : bootclasspath / target-mismatch chatter under release=8 -classfile : noise when javac reads our own .class output mid-build -processing: "No processor claimed any of these annotations" — the animal-sniffer @IgnoreJRERequirement is consumed by the maven-plugin (not a JSR-269 processor), so javac flags it every build -Werror is on: the ElementType.MODULE blocker is gone now that @NullMarked lives only in module-info.java (compiled at release 9 in a separate execution); see module-info.java's javadoc. --> <arg>-Xlint:all,-serial,-options,-classfile,-processing</arg> <arg>-Werror</arg> <!-- Checker Framework Nullness Checker runs as a second nullness pass alongside NullAway. CF is generics-aware and stricter than NullAway, so it acts as a second-opinion verifier on the same JSpecify annotations. --> <!-- Explicit processor list: Lombok (two SPI classes) + Checker Framework's Nullness Checker as a 2nd nullness pass alongside NullAway. The explicit -processor argument overrides SPI discovery, so every processor we want to run must be listed here. --> <arg>-processor</arg> <arg>lombok.launch.AnnotationProcessorHider$AnnotationProcessor,lombok.launch.AnnotationProcessorHider$ClaimingProcessor,org.checkerframework.checker.nullness.NullnessChecker</arg> <arg>-XDaddTypeAnnotationsToSymbol=true</arg> <arg>-XDcompilePolicy=simple</arg> <arg>--should-stop=ifError=FLOW</arg> <arg>-Xplugin:ErrorProne -Xep:NullAway:ERROR -XepOpt:NullAway:OnlyNullMarked=true -XepOpt:NullAway:JSpecifyMode=true -XepOpt:NullAway:CheckOptionalEmptiness=true -XepOpt:NullAway:AcknowledgeRestrictiveAnnotations=true -XepOpt:NullAway:AcknowledgeAndroidRecent=true -XepOpt:NullAway:AssertsEnabled=true -Xep:BoxedPrimitiveEquality:ERROR -Xep:EqualsHashCode:ERROR -Xep:EqualsIncompatibleType:ERROR -Xep:IdentityBinaryExpression:ERROR -Xep:SelfAssignment:ERROR -Xep:SelfComparison:ERROR -Xep:SelfEquals:ERROR -Xep:DeadException:ERROR -Xep:FormatString:ERROR -Xep:InvalidPatternSyntax:ERROR -Xep:OptionalEquality:ERROR -Xep:ImpossibleNullComparison:ERROR</arg> </compilerArgs> <annotationProcessorPaths> <path> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <version>${lombok.version}</version> </path> <path> <groupId>com.google.errorprone</groupId> <artifactId>error_prone_core</artifactId> <version>${errorprone.version}</version> </path> <path> <groupId>com.uber.nullaway</groupId> <artifactId>nullaway</artifactId> <version>${nullaway.version}</version> </path> <path> <groupId>org.checkerframework</groupId> <artifactId>checker</artifactId> <version>${checker.version}</version> </path> </annotationProcessorPaths> </configuration> <executions> <execution> <id>default-compile</id> <configuration> <!-- The default compile pass targets Java 8 bytecode for the library sources. module-info.java cannot be compiled at release 8 (it is a Java 9+ construct) and is handled by the separate execution below. --> <excludes> <exclude>module-info.java</exclude> </excludes> </configuration> </execution> <execution> <id>module-info-compile</id> <phase>compile</phase> <goals> <goal>compile</goal> </goals> <configuration> <!-- module-info.java is the only Java 9+ source in this project; compile it at release 9 (the minimum version that understands modules) without the Error Prone / NullAway / Checker Framework processors that target ordinary source files only. Java 8 runtimes silently ignore the resulting module-info.class at the JAR root, so existing classpath consumers continue to work unchanged. LlamaLoader finds the native libs (separate natives jars) through its ClassLoader, which needs no opens directives. --> <release>9</release> <includes> <include>module-info.java</include> </includes> <compilerArgs combine.self="override"/> <annotationProcessorPaths combine.self="override"/> </configuration> </execution> <execution> <id>default-testCompile</id> <configuration> <!-- Drop -parameters for test compile so jcstress reflection doesn't pick up parameter names from MethodParameters. --> <parameters>false</parameters> <compilerArgs combine.self="override"> <arg>-XDaddTypeAnnotationsToSymbol=true</arg> <arg>-XDcompilePolicy=simple</arg> <arg>--should-stop=ifError=FLOW</arg> <arg>-Xplugin:ErrorProne -Xep:NullAway:OFF -Xep:GuardedBy:OFF</arg> </compilerArgs> <annotationProcessorPaths combine.children="append"> <path> <groupId>org.openjdk.jcstress</groupId> <artifactId>jcstress-core</artifactId> <version>${jcstress.version}</version> </path> <path> <groupId>org.openjdk.jmh</groupId> <artifactId>jmh-generator-annprocess</artifactId> <version>${jmh.version}</version> </path> </annotationProcessorPaths> </configuration> </execution> </executions> </plugin> <plugin> <artifactId>maven-resources-plugin</artifactId> </plugin> <plugin> <!-- The classes jar names ServerLauncher as its Main-Class, so `java -jar llama-<v>.jar` and a JBang line that resolves it from Central next to a natives jar start the embedded server (NativeServer by default, OpenAiCompatServer with the jllama-openai-compat flag), as the README says. Only the default execution: the natives jars of the `natives` profile keep their own manifest (an Automatic-Module-Name, no entry point). smoke-natives-jars.sh holds the manifest to this in the package job; the entry was lost with the fat-jar assembly. --> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <executions> <execution> <id>default-jar</id> <configuration> <archive> <manifest> <mainClass>net.ladenthin.llama.server.ServerLauncher</mainClass> </manifest> </archive> </configuration> </execution> </executions> </plugin> <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> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-javadoc-plugin</artifactId> <configuration> <source>1.8</source> <failOnError>true</failOnError> <failOnWarnings>true</failOnWarnings> <!-- doclint is "all,-missing" (not plain "all") because Javadoc runs on the RAW source, before Lombok's annotation processor runs, so it cannot see the constructor Lombok's class-level @Builder generates. For a Lombok value class like TrainingParameters it therefore reports a spurious "use of default constructor, which does not provide a comment" (the `missing` group) even though no public default constructor exists at compile time. Dropping only the `missing` group avoids hand-writing the redundant all-args constructor that @Builder already generates, while keeping the reference / html / syntax / accessibility checks fatal (a broken {@link} or malformed HTML still fails the build). failOnWarnings stays true so those categories remain enforced. --> <doclint>all,-missing</doclint> </configuration> <executions> <execution> <id>attach-javadocs</id> <goals> <goal>jar</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.jacoco</groupId> <artifactId>jacoco-maven-plugin</artifactId> <executions> <execution> <id>prepare-agent</id> <goals> <goal>prepare-agent</goal> </goals> </execution> <execution> <id>report</id> <phase>test</phase> <goals> <goal>report</goal> </goals> </execution> </executions> </plugin> <plugin> <!-- Surefire is configured here only to control native-crash diagnostics: - argLine inherits jacoco's @{argLine} (so the jacoco runtime agent stays attached) and appends -XX:ErrorFile so the JVM crash log (hs_err_pid<pid>.log) always lands in the project basedir, which is the same directory the CI upload-artifact globs (${{ github.workspace }}/hs_err_pid*.log). - HeapDumpOnOutOfMemoryError + HeapDumpPath catch OOMs that would otherwise just print a stack and exit. - The version is pinned to the same release Maven would otherwise auto-select (visible in CI error logs as 3.5.4), so we don't drift independently of Maven's plugin-defaults bump. --> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <!-- -XX:+EnableDynamicAgentLoading: silences the JDK 21 byte-buddy self-attach agent warning that intermittently corrupts Surefire's fork channel ("Corrupted channel ..." / bogus "timeout in the fork"). See workspace policy ci-test-diagnostics.md section 2.1: https://github.com/bernardladenthin/workspace/blob/main/policies/ci-test-diagnostics.md - root cause: https://github.com/raphw/byte-buddy/issues/1639 --> <argLine>@{argLine} -Xmx2g -XX:ErrorFile=hs_err_pid%p.log -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=. -XX:+EnableDynamicAgentLoading</argLine> <!-- Keep the shipped SLF4J binding OFF the test classpath. slf4j-simple is a runtime-scope dependency, and runtime scope is part of the test classpath too. LogCaptor (io.github.hakky54, test scope) brings logback, so both providers would be present, SLF4J would pick one arbitrarily, and LogCaptor fails outright when it does not get logback: "SLF4J Logger implementation should be of the type [ch.qos.logback.classic.Logger] but found [org.slf4j.simple.SimpleLogger]" (7 tests across LoggingSmokeTest, TimingsLoggerTest, ChatResponseParserTest and CompletionResponseParserTest). Excluding it here leaves logback as the sole provider during tests and does not touch the artifact: the shipped jar's pom still names slf4j-simple at runtime scope. The tests assert what our code logs, which is binding-agnostic; which binding renders it is not what they are about. --> <classpathDependencyExcludes> <classpathDependencyExclude>org.slf4j:slf4j-simple</classpathDependencyExclude> </classpathDependencyExcludes> <!-- The native libraries a local CMake build (or a CI job) put into src/main/natives/ are not part of the main jar, so the tests read them from there directly. A checkout without a native build has no such directory, and the native-backed tests skip themselves. --> <additionalClasspathElements> <additionalClasspathElement>${project.basedir}/src/main/natives</additionalClasspathElement> </additionalClasspathElements> <!-- Tests run on the classpath, not the module path. target/classes holds a module-info.class, and Surefire then defaults to module mode: the main and test classes become the named module net.ladenthin.llama, and every module it requires (Jackson, SLF4J) moves to the module path. Jackson is then a named module of its own that may not reflect into an unexported test package (ExamplesTest: "module net.ladenthin.llama does not export examples to module com.fasterxml.jackson.databind"), and java.class.path no longer holds Jackson, so the worker JVM RouterModeIntegrationTest starts from it dies with NoClassDefFoundError. Both broke when module-info.java started to require Jackson and SLF4J. Classpath mode is how nearly every consumer runs this Java 8 library; the module path is covered by .github/smoke-natives-jars.sh against the real jars. --> <useModulePath>false</useModulePath> <!-- Capture each test class's stdout/stderr into target/surefire-reports/<class>-output.txt. When a native crash takes down the forked JVM, this file is the ONLY record of which @Test method was last running (without it the surefire *.txt summary just says "VM terminated", which we already saw in CI without telling us which test was on fire). --> <redirectTestOutputToFile>true</redirectTestOutputToFile> </configuration> </plugin> <plugin> <groupId>com.diffplug.spotless</groupId> <artifactId>spotless-maven-plugin</artifactId> <configuration> <java> <includes> <include>src/main/java/**/*.java</include> <include>src/test/java/**/*.java</include> </includes> <palantirJavaFormat> <version>${palantir-java-format.version}</version> </palantirJavaFormat> <removeUnusedImports/> <trimTrailingWhitespace/> <endWithNewline/> </java> </configuration> <executions> <execution> <id>spotless-check</id> <phase>verify</phase> <goals> <goal>check</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>com.github.spotbugs</groupId> <artifactId>spotbugs-maven-plugin</artifactId> <configuration> <effort>Max</effort> <threshold>Low</threshold> <failOnError>true</failOnError> <includeTests>false</includeTests> <excludeFilterFile>spotbugs-exclude.xml</excludeFilterFile> <plugins> <plugin> <groupId>com.mebigfatguy.fb-contrib</groupId> <artifactId>fb-contrib</artifactId> <version>${fb-contrib.version}</version> </plugin> <plugin> <groupId>com.h3xstream.findsecbugs</groupId> <artifactId>findsecbugs-plugin</artifactId> <version>${findsecbugs.version}</version> </plugin> </plugins> </configuration> <executions> <execution> <id>spotbugs-check</id> <phase>verify</phase> <goals> <goal>check</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <configuration> <mainClass>org.openjdk.jmh.Main</mainClass> <classpathScope>test</classpathScope> </configuration> </plugin> <plugin> <!-- Generic PIT policy (version, 100% gate, invocation, expansion rule): see ../workspace/policies/pit-mutation-testing.md. Repo-specific: the gated value/exception/args/json classes are pure-Java (no native libjllama or model file needed); targetClasses/targetTests are kept in lock-step. The gate is hermetic: ContentPartTest's @TempDir tests cover value.ContentPart.audioFile(Path), so no fixture is required. --> <groupId>org.pitest</groupId> <artifactId>pitest-maven</artifactId> <dependencies> <dependency> <groupId>org.pitest</groupId> <artifactId>pitest-junit5-plugin</artifactId> <version>1.2.3</version> </dependency> </dependencies> <configuration> <targetClasses> <param>net.ladenthin.llama.value.*</param> <param>net.ladenthin.llama.exception.*</param> <param>net.ladenthin.llama.args.*</param> <param>net.ladenthin.llama.json.TimingsLogger</param> <param>net.ladenthin.llama.json.RerankResponseParser</param> <param>net.ladenthin.llama.json.ChatResponseParser</param> <param>net.ladenthin.llama.json.CompletionResponseParser</param> <!-- JsonParameters carries the one-JSON-value invariant that stops a caller-supplied fragment from injecting sibling fields into a request body, so it is gated rather than merely tested. The rest of the parameters package is deliberately NOT on the gate: those classes are ~200 one-line builder setters whose mutants add cost without adding signal. --> <param>net.ladenthin.llama.parameters.JsonParameters</param> </targetClasses> <targetTests> <param>net.ladenthin.llama.value.*</param> <param>net.ladenthin.llama.exception.*</param> <param>net.ladenthin.llama.args.*</param> <param>net.ladenthin.llama.json.*</param> <param>net.ladenthin.llama.parameters.*</param> <!-- Not a mutation test: it fails when PIT's own classpath lacks the native library or puts the tests in a named module. --> <param>net.ladenthin.llama.TestClasspathTest</param> </targetTests> <mutationThreshold>100</mutationThreshold> <timeoutConstant>30000</timeoutConstant> <!-- The same exclusion Surefire carries above, and it has to be repeated here because PIT builds its OWN classpath and does not read Surefire's configuration. Two SLF4J providers are on the test classpath: slf4j-simple arrives at runtime scope (the binding the pom ships with the jar) and logback-classic at test scope (LogCaptor requires logback specifically). SLF4J's ServiceLoader then picks one arbitrarily; when it picks slf4j-simple, every LogCaptor assertion fails and PIT aborts the whole run with "N tests did not pass without mutation ... requires a green suite" — a red gate on a suite Surefire had just run green, which is a genuinely confusing failure to land on. The parameter is pitest-maven's own, modelled on Surefire's and taking the same "groupId:artifactId" form. It changes nothing about the artifact: the jar's pom still ships slf4j-simple. --> <classpathDependencyExcludes> <classpathDependencyExclude>org.slf4j:slf4j-simple</classpathDependencyExclude> </classpathDependencyExcludes> <!-- The native library, for the same reason: Surefire reads it from src/main/natives (additionalClasspathElements above), and PIT does not see that setting. Since the natives left target/classes (natives jars, #472), a model-backed test in a target-test package found its model in CI but no library, and PIT aborted with "JsonEndpointParametersTest did not pass without mutation". Without a native build the directory is missing and those tests skip themselves, as under Surefire. --> <additionalClasspathElements> <additionalClasspathElement>${project.basedir}/src/main/natives</additionalClasspathElement> </additionalClasspathElements> </configuration> </plugin> </plugins> </build> <profiles> <!-- The `release` profile (GPG signing + Central Publishing) now lives in the parent pom (../pom.xml) and is inherited, so a single reactor `mvn -P release deploy` signs and publishes every module. The natives profile below stays here — it is core-specific. --> <!-- The natives jars. The main jar carries classes only; every native build ships as its own jar holding exactly one directory, net/ladenthin/llama/<OS>/<ARCH>/<backend>/, so any combination of them can share one classpath: LlamaLoader loads the library jar of the running platform (LlamaLoader.LIBRARY_BACKENDS) and puts every GPU module jar of the platform next to it (LlamaLoader.MODULE_BACKENDS), see CLAUDE.md "Natives jars". The executions below are generated from .github/natives.csv, the single list of natives jars: `python3 .github/check-natives.py pom` prints them, and the same script (run in CI) fails when they drift from the list. Each jar needs its own Automatic-Module-Name: without one every natives jar derives the module name "llama" from its file name, and the module path silently keeps only the first of them. The libraries come from src/main/natives/, where CMake writes them and CI merges every build's artifact (.github/merge-native-artifacts.sh, which fails on a missing one). Activated only in CI (-P natives): a local build has one of these directories at most. --> <profile> <id>natives</id> <build> <plugins> <!-- The license texts of the third-party code compiled into the natives (llama.cpp/ggml, its vendored libraries, BoringSSL, the GPU vendors' header libraries), committed under llama/legal/natives/ and copied next to the natives tree before packaging, so every natives jar below carries them under META-INF/third-party/natives/ (the include check-natives.py generates). src/main/natives is generated anyway: CMake writes the libraries there and CI merges every build's artifact into it. --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-resources-plugin</artifactId> <executions> <execution> <id>natives-legal</id> <phase>prepare-package</phase> <goals> <goal>copy-resources</goal> </goals> <configuration> <outputDirectory>${project.basedir}/src/main/natives/META-INF/third-party/natives</outputDirectory> <resources> <resource> <directory>${project.basedir}/legal/natives</directory> </resource> </resources> </configuration> </execution> </executions> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <executions> <execution> <id>natives-cpu-linux-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>cpu-linux-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux/x86_64/cpu/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.cpu_linux_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-cpu-linux-aarch64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>cpu-linux-aarch64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux/aarch64/cpu/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.cpu_linux_aarch64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-cpu-linux-s390x</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>cpu-linux-s390x</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux/s390x/cpu/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.cpu_linux_s390x</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-cpu-android-aarch64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>cpu-android-aarch64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux-Android/aarch64/cpu/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.cpu_android_aarch64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-cpu-android-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>cpu-android-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux-Android/x86_64/cpu/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.cpu_android_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-cpu-windows-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>cpu-windows-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/x86_64/cpu/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.cpu_windows_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-cpu-windows-aarch64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>cpu-windows-aarch64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/aarch64/cpu/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.cpu_windows_aarch64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-metal-macos-aarch64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>metal-macos-aarch64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Mac/aarch64/metal/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.metal_macos_aarch64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-cuda13-linux-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>cuda13-linux-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux/x86_64/cuda13/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.cuda13_linux_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-cuda13-windows-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>cuda13-windows-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/x86_64/cuda13/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.cuda13_windows_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-rocm-linux-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>rocm-linux-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux/x86_64/rocm/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.rocm_linux_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-rocm-windows-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>rocm-windows-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/x86_64/rocm/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.rocm_windows_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-sycl-linux-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>sycl-linux-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux/x86_64/sycl/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.sycl_linux_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-sycl-windows-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>sycl-windows-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/x86_64/sycl/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.sycl_windows_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-vulkan-linux-aarch64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>vulkan-linux-aarch64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux/aarch64/vulkan/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.vulkan_linux_aarch64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-vulkan-linux-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>vulkan-linux-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux/x86_64/vulkan/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.vulkan_linux_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-vulkan-windows-aarch64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>vulkan-windows-aarch64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/aarch64/vulkan/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.vulkan_windows_aarch64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-vulkan-windows-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>vulkan-windows-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/x86_64/vulkan/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.vulkan_windows_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-opencl-android-aarch64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>opencl-android-aarch64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux-Android/aarch64/opencl/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.opencl_android_aarch64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-opencl-windows-aarch64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>opencl-windows-aarch64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/aarch64/opencl/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.opencl_windows_aarch64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-opencl-windows-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>opencl-windows-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/x86_64/opencl/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.opencl_windows_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-openvino-linux-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>openvino-linux-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Linux/x86_64/openvino/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.openvino_linux_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> <execution> <id>natives-openvino-windows-x86-64</id> <phase>package</phase> <goals> <goal>jar</goal> </goals> <configuration> <classifier>openvino-windows-x86-64</classifier> <classesDirectory>${project.basedir}/src/main/natives</classesDirectory> <includes> <include>net/ladenthin/llama/Windows/x86_64/openvino/**</include> <include>META-INF/third-party/natives/**</include> </includes> <archive> <addMavenDescriptor>false</addMavenDescriptor> <manifestEntries> <Automatic-Module-Name>net.ladenthin.llama.natives.openvino_windows_x86_64</Automatic-Module-Name> </manifestEntries> </archive> </configuration> </execution> </executions> </plugin> </plugins> </build> </profile> <profile> <id>vmlens</id> <build> <plugins> <plugin> <groupId>com.vmlens</groupId> <artifactId>vmlens-maven-plugin</artifactId> <configuration> <!-- Run vmlens interleaving analysis over the whole `vmlens` test package (smoke test + SessionStateInterleavingTest). The `com.vmlens:api` test dependency lives in the main <dependencies> block. Expand <includes> as more concurrency tests are added (the streambuffer repo runs vmlens over its whole suite). --> <includes> <include>**/vmlens/*.java</include> </includes> </configuration> <executions> <execution> <id>vmlens-test</id> <goals> <goal>test</goal> </goals> </execution> </executions> </plugin> </plugins> </build> </profile> <profile> <id>jcstress</id> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <executions> <execution> <id>jcstress</id> <phase>test</phase> <goals><goal>exec</goal></goals> <configuration> <executable>${java.home}/bin/java</executable> <classpathScope>test</classpathScope> <arguments> <argument>-classpath</argument> <classpath/> <argument>org.openjdk.jcstress.Main</argument> <argument>-v</argument> <argument>-m</argument> <argument>default</argument> </arguments> </configuration> </execution> </executions> </plugin> </plugins> </build> </profile> </profiles> </project>