- 결정 7: `LegacyOutboxAppendPort`·legacy 저장 모델·relay·Kafka R0 seam 삭제, 템플릿 JSON encoder(`JsonIntegrationEventEncoder`),
durable operation·sample 이벤트가 `OutboxAppendPort` + encoder로, persistence-jpa V19(pre-canonical 미발행 row 거부)
- 결정 3: outbox relay·멱등성 executor 조립을 `composition:outbox-relay`·`composition:idempotency`로,
sample이 복사한 bootstrap 인프라를 `composition:service-runtime`으로(sample `SampleIdempotencyConfig` 복사본 삭제)
- persistence-jpa outbox·멱등성 패키지 feature 기준 이동, messaging outbox·inbox leaf를 reliability / reliability-jdbc-postgresql로
- messaging outbox header를 jsonb로(P18-new-1 — `\`로 끝나는 값이 다음 header를 삼키던 결함)
- 통합(충돌 22건): P25 A-10c(전략 선택 설정 삭제)를 service-runtime `DomainContextConfig`에 적용, P25 startup 예외 통합을
composition 설정 테스트에, P25 `CommandUseCase.handle` 이름을 PG 통합 테스트에, P15 `EventJson`은 호출자 0이 되어 삭제
- root CLAUDE.md의 legacy seam 문장 수정(P18-new-2)
검증: ./gradlew check architectureCheck verifyDependencyLocks verifyPublicPathSnapshot :app-bootstrap:verifyEnvKeys
configContractCheck :app-bootstrap:integrationTest :sample-portfolio:integrationTest :sample-portfolio:systemTest
persistence-jpa jpaPlatformContractTest·postgresql{Idempotency,OutboxAppendTransactional,OutboxConcurrentRelay,OutboxRowLifecycle}IntegrationTest
:messaging:messaging-reliability-jdbc-postgresql:integrationTest --continue 통과(700 task)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
75 lines
3.8 KiB
Groovy
75 lines
3.8 KiB
Groovy
plugins {
|
|
id 'ca.auxiliary-source-set'
|
|
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.
|
|
auxiliarySourceSets {
|
|
sourceSet('integrationTest') {
|
|
compilesAgainst 'main'
|
|
}
|
|
}
|
|
|
|
dependencies {
|
|
// Types an adopter writes against: envelopes, destinations, publish results, profiles, ports.
|
|
api project(':messaging:messaging-core-api')
|
|
api project(':messaging:messaging-schema-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-api')
|
|
implementation project(':messaging:messaging-admin-runtime')
|
|
|
|
implementation 'org.springframework.boot:spring-boot-autoconfigure'
|
|
implementation 'org.springframework.boot:spring-boot-actuator'
|
|
|
|
// The Reactor facade lives here, not in core-api: the core contract stays CompletionStage so
|
|
// that a service which does not use Reactor never inherits it. api, because
|
|
// ReactiveMessagePublisher returns Mono — a facade whose return type an adopter cannot name
|
|
// is a facade they cannot call.
|
|
api 'io.projectreactor:reactor-core'
|
|
testImplementation 'io.projectreactor:reactor-test'
|
|
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'
|
|
}
|
|
|
|
strictTestLanes {
|
|
lane('integrationTest') {
|
|
integration()
|
|
sourceSet = 'integrationTest'
|
|
description = 'Runs the assembled messaging starter round trip against real Kafka.'
|
|
}
|
|
}
|