pom.xml

<?xml version="1.0" encoding="UTF-8"?>
<!--

    Sliceworkz Event Modeling - an opinionated Event Modeling framework in Java
    Copyright © 2025-2026 Sliceworkz / XTi (info@sliceworkz.org)

    This program is free software: you can redistribute it and/or modify
    it under the terms of the GNU Lesser General Public License as published by
    the Free Software Foundation, either version 3 of the License, or
    (at your option) any later version.

    This program is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    GNU Lesser General Public License for more details.

    You should have received a copy of the GNU Lesser General Public License
    along with this program.  If not, see <http://www.gnu.org/licenses/>.

-->
<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>org.sliceworkz</groupId>
	<artifactId>sliceworkz-eventmodeling</artifactId>
	<version>0.7.0-SNAPSHOT</version>
	
	<name>${project.artifactId}</name>
	<description>An opinionated Event Modeling framework in Java</description>
	<url>https://sliceworkz.github.io/eventmodeling</url>
	
	<packaging>pom</packaging>


	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

		<sliceworkz.eventstore.version>0.11.2</sliceworkz.eventstore.version>
		
		<maven.minimal-version>3.6.3</maven.minimal-version>
		
		<maven.maven-pgp-plugin.version>3.2.8</maven.maven-pgp-plugin.version>
		<maven.maven-versions-plugin.version>2.22.0</maven.maven-versions-plugin.version>
		<maven.maven-enforcer-plugin.version>3.6.3</maven.maven-enforcer-plugin.version>
		<maven.mycila-license-plugin.version>5.1.2</maven.mycila-license-plugin.version>
		<maven.maven-central-publishing-plugin.version>0.11.0</maven.maven-central-publishing-plugin.version>
		<maven.flatten-plugin.version>1.8.0</maven.flatten-plugin.version>
		
		<maven.compiler.release>21</maven.compiler.release>

		<!-- Publish only client-facing modules; opt-in per module below -->
		<maven.deploy.skip>true</maven.deploy.skip>
	</properties>
	
	<modules>
		<module>sliceworkz-eventmodeling-bom</module>
		<module>sliceworkz-eventmodeling-parent-pom</module>
		<module>sliceworkz-eventmodeling-api</module>
		<module>sliceworkz-eventmodeling-impl</module>
		<module>sliceworkz-eventmodeling-testing</module>
		<module>sliceworkz-eventmodeling-tests</module>
		<module>sliceworkz-eventmodeling-benchmark</module>
		<module>sliceworkz-eventmodeling-examples</module>
	</modules>

	<!--
		Resolve org.sliceworkz SNAPSHOTs from the sliceworkz cloudrepo. The eventstore
		this project builds on publishes its SNAPSHOTs there (see its
		build-and-deploy-snapshot-cloudrepo workflow), not to Maven Central's snapshot
		repository, so a build cannot find e.g. sliceworkz-eventstore-bom:0.10.0-SNAPSHOT
		without this. A local build only appeared to work because the eventstore had been
		mvn install'ed into ~/.m2.

		Declared here rather than in a profile on purpose: every build needs it while
		sliceworkz.eventstore.version is a SNAPSHOT, and an activeByDefault profile would
		silently switch off as soon as a build passes -P (gpg-ci, cloudrepo, ...).

		Reading it needs the 'cloudrepo' server credentials in settings.xml; in CI those
		come from setup-java's server-id (see build-and-deploy-snapshot-cloudrepo.yaml).
		A workflow that does not provide them cannot build against a SNAPSHOT eventstore.

		Releases are disabled: those come from Maven Central like any other dependency,
		so the credentialed repository is only consulted for the SNAPSHOTs that are
		exclusively there. The published consumer POMs are unaffected — flattenMode
		ossrh strips repositories.
	-->
	<repositories>
		<repository>
			<name>Sliceworkz CloudRepo</name>
			<id>cloudrepo</id>
			<url>https://xti.mycloudrepo.io/repositories/sliceworkz</url>
			<releases>
				<enabled>false</enabled>
			</releases>
			<snapshots>
				<enabled>true</enabled>
				<!--
					Check for a newer snapshot on every build, instead of Maven's default of once a day.
					The eventstore snapshot this tracks moves several times a day, and the CI workflows
					restore ~/.m2 from setup-java's maven cache: with the default policy a runner keeps
					compiling against whichever snapshot it cached earlier that day, which shows up as a
					compile error against an API that has since changed rather than as a stale download.
				-->
				<updatePolicy>always</updatePolicy>
			</snapshots>
		</repository>
	</repositories>

	<build>
		<pluginManagement>
			<plugins>
				<!--
					flatten-maven-plugin produces self-contained consumer POMs (no parent,
					inlined versions) for the PUBLISHED modules only. It is opt-in via
					pluginManagement rather than applied to every module, because ossrh mode
					strips custom properties (e.g. sliceworkz.eventstore.version) from a
					flattened parent POM, which would then break resolution of the external
					eventstore-bom import for the client modules. Leaving the parent POMs
					un-flattened keeps that property resolvable. Relies on Maven 3.
				-->
				<plugin>
				    <groupId>org.codehaus.mojo</groupId>
				    <artifactId>flatten-maven-plugin</artifactId>
				    <version>${maven.flatten-plugin.version}</version>
				    <configuration>
						<flattenMode>ossrh</flattenMode>
				    </configuration>
				    <executions>
						<execution>
							<id>flatten</id>
							<phase>process-resources</phase>
							<goals><goal>flatten</goal></goals>
						</execution>
						<execution>
							<id>flatten.clean</id>
							<phase>clean</phase>
							<goals><goal>clean</goal></goals>
						</execution>
				    </executions>
				</plugin>
			</plugins>
		</pluginManagement>
		<plugins>
			<plugin>
			    <groupId>org.codehaus.mojo</groupId>
			    <artifactId>versions-maven-plugin</artifactId>
			    <version>${maven.maven-versions-plugin.version}</version>
			    
			    <!-- make sure we get the right suggestions from 
			    		mvn versions:display-dependency-updates
			    	 and
			    		mvn versions:display-plugin-updates
			     -->
			    <configuration>
					<ruleSet>
			            <ignoreVersions>
							<!-- Don't depend on snapshots' -->
							<ignoreVersion>
								<type>regex</type>
								<version>(.+-SNAPSHOT|.+-M\d)</version>
							</ignoreVersion>
							<!-- Don't depend on alpha or beta versions' -->
							<ignoreVersion>
								<type>regex</type>
								<version>.+-(alpha|beta).+</version>
							</ignoreVersion>
							<!-- Don't depend on release candidates -->
							<ignoreVersion>
								<type>regex</type>
								<version>(?i).+-rc[-.]?\d+</version>
							</ignoreVersion>
			            </ignoreVersions>
			    	</ruleSet>
				</configuration>
			</plugin>
			
			<plugin>
				<groupId>org.apache.maven.plugins</groupId>
				<artifactId>maven-enforcer-plugin</artifactId>
				<version>${maven.maven-enforcer-plugin.version}</version>
				<executions>
					<execution>
						<id>enforce-maven</id>
						<goals>
							<goal>enforce</goal>
						</goals>
						<configuration>
							<rules>
								<requireMavenVersion>
									<version>${maven.minimal-version}</version>
								</requireMavenVersion>
							</rules>    
						</configuration>
					</execution>
					<!--
						The framework reports what it does through its own observability SPI
						(org.sliceworkz.eventmodeling.observability.BoundedContextObserver), as the eventstore
						does through EventStoreObserver, and names no metrics library: a binding to one is an
						application's choice, shipped outside these artifacts. Micrometer reaching any module,
						in any scope, would be the start of that coupling coming back, so it fails the build.
					-->
					<execution>
						<id>no-micrometer</id>
						<goals>
							<goal>enforce</goal>
						</goals>
						<configuration>
							<rules>
								<bannedDependencies>
									<message>The eventmodeling modules must not depend on Micrometer: they report through BoundedContextObserver (and the store through EventStoreObserver), and a Micrometer binding lives outside this repository.</message>
									<searchTransitive>true</searchTransitive>
									<excludes>
										<exclude>io.micrometer:*</exclude>
									</excludes>
								</bannedDependencies>
							</rules>
						</configuration>
					</execution>
				</executions>
			</plugin>
					        					
			<plugin>
			    <groupId>org.sonatype.central</groupId>
			    <artifactId>central-publishing-maven-plugin</artifactId>
			    <version>${maven.maven-central-publishing-plugin.version}</version>
			    <extensions>true</extensions>
			    <configuration>
				<publishingServerId>central</publishingServerId>
				<deploymentName>eventmodeling-${project.version}</deploymentName>				
				<!--
					central-publishing bundles the whole reactor and does NOT honour
					maven.deploy.skip, so the build constructs (aggregator, parent-pom)
					and non-client modules (examples, benchmark, integration tests) must be
					excluded explicitly here to publish only the client-facing set to Central.
				-->
				<!-- matched against each artifact's artifactId (exact) -->
				<excludeArtifacts>
					<excludeArtifact>sliceworkz-eventmodeling</excludeArtifact>
					<excludeArtifact>sliceworkz-eventmodeling-parent-pom</excludeArtifact>
					<excludeArtifact>sliceworkz-eventmodeling-examples</excludeArtifact>
					<excludeArtifact>sliceworkz-eventmodeling-benchmark</excludeArtifact>
					<excludeArtifact>sliceworkz-eventmodeling-tests</excludeArtifact>
				</excludeArtifacts>
			    </configuration>
			</plugin>

      		
			<plugin>
			    <groupId>com.mycila</groupId>
			    <artifactId>license-maven-plugin</artifactId>
			    <version>${maven.mycila-license-plugin.version}</version>
				<executions>
					<execution>
						<phase>package</phase>
						<goals>
							<goal>check</goal>
						</goals>
					</execution>
				</executions>
			    <configuration>
					<properties>
						<project.name>Sliceworkz Event Modeling</project.name>
						<project.description>an opinionated Event Modeling framework in Java</project.description>
					    <owner>Sliceworkz / XTi</owner>
					    <email>info@sliceworkz.org</email>
					    <year>2025-2026</year>
					</properties>
					<licenseSets>
						<licenseSet>
							<header>com/mycila/maven/plugin/license/templates/LGPL-3.txt</header>
							<includes>
							    <include>**/*.java</include>
							    <include>**/*.sql</include>
							    <include>**/*.xml</include>
							    <include>**/*.properties</include>
							</includes>
							<excludes>
							    <exclude>**/target/**</exclude>
							</excludes>
						</licenseSet>
					</licenseSets>
			    </configuration>
			</plugin>
		</plugins>
	</build>
	
	<profiles>
		<profile>
			<id>gpg-ci</id>
			<build>
				<plugins>
					<plugin>
						<groupId>org.apache.maven.plugins</groupId>
						<artifactId>maven-gpg-plugin</artifactId>
						<version>${maven.maven-pgp-plugin.version}</version>
						<executions>
							<execution>
								<id>sign-artifacts</id>
								<phase>install</phase>
								<goals>
									<goal>sign</goal>
								</goals>
							</execution>
						</executions>
						<configuration>
							<gpgArguments>
								<arg>--pinentry-mode</arg>
								<arg>loopback</arg>
							</gpgArguments>
							<passphrase>${env.GPG_PASSPHRASE}</passphrase>
						</configuration>
					</plugin>
				</plugins>
			</build>
		</profile>
		  <profile>
			<id>snapshots</id>	
			<repositories>
				<repository>
					<name>Central Portal Snapshots</name>
					<id>central-portal-snapshots</id>
					<url>https://central.sonatype.com/repository/maven-snapshots/</url>
					<releases>
						<enabled>false</enabled>
					</releases>
					<snapshots>
						<enabled>true</enabled>
					</snapshots>
				</repository>
			</repositories>
		  </profile>

		<!--
			Deploy SNAPSHOT artifacts to the sliceworkz cloudrepo instead of Maven
			Central. Activated by the build-and-deploy-snapshot-cloudrepo workflow.

			The central-publishing-maven-plugin installs a lifecycle participant that
			normally clears maven-deploy-plugin and takes over the deploy phase. It
			stands down as soon as the central plugin has an explicit execution binding
			the 'publish' goal. We add exactly that (phase 'none'; skipPublishing as
			belt-and-suspenders) so the standard maven-deploy-plugin handles the
			cloudrepo distributionManagement. The default build is untouched, so Maven
			Central publishing keeps working.
		-->
		<profile>
			<id>cloudrepo</id>
			<distributionManagement>
				<repository>
					<id>cloudrepo</id>
					<url>https://xti.mycloudrepo.io/repositories/sliceworkz</url>
				</repository>
				<snapshotRepository>
					<id>cloudrepo</id>
					<url>https://xti.mycloudrepo.io/repositories/sliceworkz</url>
				</snapshotRepository>
			</distributionManagement>
			<build>
				<plugins>
					<plugin>
						<groupId>org.sonatype.central</groupId>
						<artifactId>central-publishing-maven-plugin</artifactId>
						<configuration>
							<skipPublishing>true</skipPublishing>
						</configuration>
						<executions>
							<execution>
								<id>cloudrepo-stand-down</id>
								<phase>none</phase>
								<goals>
									<goal>publish</goal>
								</goals>
							</execution>
						</executions>
					</plugin>
				</plugins>
			</build>
		</profile>

	</profiles>
	
	<licenses>
		<license>
			<name>LGPL License</name>
			<url>https://opensource.org/license/lgpl-3-0</url>
		</license>
	</licenses>

	<developers>
		<developer>
			<name>Günther Van Roey</name>
			<email>gunther.vanroey@xt-i.com</email>
		</developer>
	</developers>
	
	<scm>
		<connection>https://github.com/sliceworkz/eventmodeling.git</connection>
		<developerConnection>scm:git:git://github.com/sliceworkz/eventmodeling.git</developerConnection>
		<url>https://github.com/sliceworkz/eventmodeling</url>
	</scm>
	
</project>