nano-bernd
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>io.github.jwulf</groupId>
<artifactId>nano-bernd</artifactId>
<version>0.2.1</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.jwulf</groupId>
<artifactId>nano-bernd</artifactId>
<version>0.2.1</version>
<packaging>jar</packaging>
<name>nano-bernd</name>
<description>Embedded Nano BPMN engine for the JVM — codename Bernd, per ADR 0005.</description>
<url>https://github.com/jwulf/nano-bpm</url>
<inceptionYear>2026</inceptionYear>
<licenses>
<license>
<name>Apache-2.0</name>
<url>https://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<id>jwulf</id>
<name>Josh Wulf</name>
<email>josh@magikcraft.io</email>
<url>https://github.com/jwulf</url>
</developer>
</developers>
<scm>
<connection>scm:git:https://github.com/jwulf/nano-bpm.git</connection>
<developerConnection>scm:git:git@github.com:jwulf/nano-bpm.git</developerConnection>
<url>https://github.com/jwulf/nano-bpm</url>
<tag>HEAD</tag>
</scm>
<issueManagement>
<system>GitHub Issues</system>
<url>https://github.com/jwulf/nano-bpm/issues</url>
</issueManagement>
<properties>
<maven.compiler.release>17</maven.compiler.release>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<chicory.version>1.4.0</chicory.version>
<junit.version>5.11.4</junit.version>
<jackson.version>2.18.2</jackson.version>
</properties>
<dependencies>
<dependency>
<groupId>com.dylibso.chicory</groupId>
<artifactId>runtime</artifactId>
<version>${chicory.version}</version>
</dependency>
<!-- Small, well-known JSON parser for decoding activateJobs output.
Kept as a runtime dep of nano-bernd so callers don't have to think
about it; consumers pinning a different Jackson can override. -->
<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>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.5.2</version>
</plugin>
</plugins>
</build>
<!--
Release profile — activated by the release workflow with `-Prelease` to
build & sign the source + javadoc jars and publish through the Central
Portal. Not activated by default so day-to-day `mvn test` / `mvn verify`
doesn't require GPG.
-->
<profiles>
<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>
<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>
<!-- Read passphrase from env so we don't need a settings.xml on CI. -->
<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.11.0</version>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<!-- Auto-publish once the deployment is validated by the Portal.
Flip to `false` if you want a manual "Publish" click. -->
<autoPublish>true</autoPublish>
<waitUntil>published</waitUntil>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>