plugins { id 'ca.platform-module' id 'ca.spring-config' } // Scopes, not a flat list of `api`. // // `api` is the types that genuinely appear in this module's public signatures; everything else is // `implementation`. Broker transports live in capability starters (messaging-spring-boot-starter-kafka), // so this starter's compile classpath carries no broker SDK. testing { suites { integrationTest(JvmTestSuite) { dependencies { implementation project() } } } } configurations { integrationTestImplementation.extendsFrom testImplementation integrationTestRuntimeOnly.extendsFrom testRuntimeOnly } dependencies { // Types an adopter writes against: envelopes, destinations, publish results, profiles, ports. api project(':messaging:messaging-core-api') api project(':messaging:messaging-policy') api project(':messaging:messaging-transport-spi') api project(':messaging:messaging-observability') api project(':messaging:messaging-security') api project(':messaging:messaging-reliability-api') // Wired by the auto-configurations and never named in an adopter's source. implementation project(':messaging:messaging-schema-json') // The publisher and its collaborators live here. The starter did not depend on it at all, // which is why MessagingCoreAutoConfiguration consumed a MessagePublisher that nothing in // reach could produce (MSG-INT-003). implementation project(':messaging:messaging-runtime-core') // The relay and consumer logic, and the PostgreSQL stores behind their ports. implementation project(':messaging:messaging-reliability') implementation project(':messaging:messaging-reliability-jdbc-postgresql') implementation project(':messaging:messaging-admin') implementation 'org.springframework.boot:spring-boot-autoconfigure' implementation 'org.springframework.boot:spring-boot-actuator' testImplementation 'org.springframework.boot:spring-boot-test' testImplementation 'org.springframework:spring-test' // Provider auto-configurations live in capability artifacts. Tests that exercise provider // selection add it only to the test graph; the production starter remains broker-neutral. testImplementation project(':messaging:messaging-spring-boot-starter-kafka') // Test-only, and specifically so the configuration reference can be executed rather than read: // MessagingConfigurationBindingTest loads the YAML blocks out of the shipped document and boots // a context on them. Spring Boot 4 treats snakeyaml as optional, so a document-driven test has // to ask for it; production code does not, and adding it here keeps that asymmetry visible. testImplementation 'org.yaml:snakeyaml' // The live round trip. MSG-INT-003's membership rule is that the starter earns // app-bootstrap membership in the same change that proves a real broker round trip, // so the proof has to run somewhere — and the starter is where the whole platform // assembles. integrationTestImplementation project(':messaging:messaging-spring-boot-starter-kafka') integrationTestImplementation 'org.testcontainers:testcontainers-junit-jupiter' integrationTestImplementation 'org.testcontainers:testcontainers-kafka' // The consume round trip's inbox lane: a real PostgreSQL behind the JDBC inbox, joined to the // handler's own write by a real transaction manager. integrationTestImplementation project(':messaging:messaging-reliability') integrationTestImplementation project(':messaging:messaging-reliability-jdbc-postgresql') integrationTestImplementation 'org.springframework:spring-jdbc' integrationTestImplementation 'org.testcontainers:testcontainers-postgresql' integrationTestImplementation 'org.postgresql:postgresql' } strictTestLanes { lane('integrationTest') { integration() sourceSet = 'integrationTest' description = 'Runs the assembled messaging starter round trip against real Kafka.' } }