plugins { id 'ca.platform-module' } testing { suites { integrationTest(JvmTestSuite) { dependencies { implementation project() } } } } configurations { integrationTestImplementation.extendsFrom testImplementation integrationTestRuntimeOnly.extendsFrom testRuntimeOnly } // The relational implementations of the reliability ports: the outbox repository, the inbox // repository and the destructive-operation journal. Spring JDBC for the transaction join, and SQL // that is PostgreSQL's (`jsonb`, `FOR UPDATE SKIP LOCKED`, `ON CONFLICT`, `TIMESTAMPTZ`) — the name // is the contract. The relay and consumer logic that uses them is messaging-reliability. dependencies { api project(':messaging:messaging-core-api') api project(':messaging:messaging-reliability-api') // The destructive-operation journal lives here because it needs exactly what the outbox needs: // one relational database every replica can see, and a migration lane that already exists. The // contract it implements belongs to the admin API. api project(':messaging:messaging-admin') implementation 'org.springframework:spring-jdbc' implementation 'org.springframework:spring-tx' // Live-database certification. The reliability patterns are claims about transaction // boundaries and uniqueness constraints, and only a real database can settle them. testImplementation project(':messaging:messaging-testkit') integrationTestImplementation project(':messaging:messaging-testkit') integrationTestImplementation 'org.testcontainers:testcontainers-postgresql' integrationTestImplementation 'org.testcontainers:testcontainers-junit-jupiter' integrationTestImplementation 'org.postgresql:postgresql' } strictTestLanes { lane('integrationTest') { integration() sourceSet = 'integrationTest' description = 'Runs outbox, inbox and admin-journal contracts against real PostgreSQL.' } }