zerozdb
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>com.zeroz4j</groupId>
<artifactId>zerozdb</artifactId>
<version>0.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 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.zeroz4j</groupId>
<artifactId>zerozdb</artifactId>
<version>0.1.0</version>
<packaging>jar</packaging>
<name>ZeroZ DB</name>
<description>Zero-impedance pure-Java database over EclipseStore: serialized write-blocks,
atomic durable commits, concurrent reads.</description>
<url>https://github.com/ZeroZ4j/zerozdb</url>
<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>
<developers>
<developer>
<id>fschoning</id>
<name>Franz Schöning</name>
<url>https://www.franzschoning.com</url>
<roles>
<role>Principal Enterprise Architect</role>
</roles>
</developer>
</developers>
<organization>
<name>ZeroZ4J</name>
<url>https://www.zeroz4j.com</url>
</organization>
<scm>
<connection>scm:git:https://github.com/ZeroZ4j/zerozdb.git</connection>
<developerConnection>scm:git:ssh://git@github.com/ZeroZ4j/zerozdb.git</developerConnection>
<url>https://github.com/ZeroZ4j/zerozdb</url>
<tag>HEAD</tag>
</scm>
<issueManagement>
<system>GitHub Issues</system>
<url>https://github.com/ZeroZ4j/zerozdb/issues</url>
</issueManagement>
<properties>
<maven.compiler.release>21</maven.compiler.release>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<eclipsestore.version>4.1.0</eclipsestore.version>
<junit.version>5.11.4</junit.version>
</properties>
<dependencies>
<dependency>
<groupId>org.eclipse.store</groupId>
<artifactId>storage-embedded</artifactId>
<version>${eclipsestore.version}</version>
</dependency>
<!-- Standalone serializer: the wire format for the network server. Same engine that
persists the graph, so remote calls stay pure EclipseStore with no extra codec. -->
<dependency>
<groupId>org.eclipse.serializer</groupId>
<artifactId>serializer</artifactId>
<version>${eclipsestore.version}</version>
</dependency>
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter</artifactId>
<version>${junit.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-simple</artifactId>
<version>2.0.13</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.5.2</version>
</plugin>
<!-- API documentation. The classes carry the reasoning as well as the contract, so
the generated javadoc is a genuine reference rather than a signature dump.
Build with: mvn javadoc:javadoc (output in target/reports/apidocs)
Attach a jar to a release with: mvn package -Prelease -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>3.11.2</version>
<configuration>
<doctitle>ZeroZ DB ${project.version} API</doctitle>
<windowtitle>ZeroZ DB ${project.version}</windowtitle>
<bottom><![CDATA[Copyright © 2026 Franz Schöning —
<a href="https://www.zeroz4j.com">zeroz4j.com</a> —
<a href="https://www.franzschoning.com">Principal Enterprise Architect</a>]]></bottom>
<links>
<link>https://docs.oracle.com/en/java/javase/21/docs/api/</link>
</links>
<!-- Javadoc's strict HTML checks fail on prose that is otherwise fine. -->
<doclint>none</doclint>
<notimestamp>true</notimestamp>
</configuration>
</plugin>
</plugins>
</build>
<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>
</plugin>
<!-- Central requires every artifact to be signed. The key is yours; see
docs/publishing.md for generating and distributing it. -->
<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>
<!-- GnuPG 2.x refuses a passphrase supplied on the command
line unless loopback pinentry is enabled. Without this,
a release from a script or CI hangs waiting for a
dialog that never appears. -->
<gpgArguments>
<arg>--pinentry-mode</arg>
<arg>loopback</arg>
</gpgArguments>
</configuration>
</execution>
</executions>
</plugin>
<!-- Uploads to the Central Portal (central.sonatype.com). autoPublish is
false deliberately: the first releases should be inspected in the portal
before they go out, because a published version can never be replaced. -->
<plugin>
<groupId>org.sonatype.central</groupId>
<artifactId>central-publishing-maven-plugin</artifactId>
<!-- 0.7.0 could not parse the portal's response: Sonatype added a
'warnings' field the older client rejects, so the upload succeeded
and then the build failed while reading validation status. -->
<version>0.11.0</version>
<extensions>true</extensions>
<configuration>
<publishingServerId>central</publishingServerId>
<autoPublish>false</autoPublish>
<waitUntil>validated</waitUntil>
</configuration>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>