- 결정 32: fileserver transport 연산 21개를 `port.in` use case로, 쓰기·읽기에 `file:*` 권한(소유자·tenant 정책은 유지), inbound 서비스 이름 `*UseCase`, port 구현 이름 `<Tech><Port>` 규칙(S2-#13b, 24개) - 디렉터리 descriptor 파일 primitive를 `adapter:outbound:support`로(S4-lead-2 일부 — fileserver는 번역만), persistence-fileserver를 scan·클래스별 조건 대신 명시적 `@Bean` 설정으로(S2-#8a 일부), `FileVerifier`를 adapter로 - 호출자 0인 `poster.image-attached` 이벤트 삭제, SES SDK client를 레지스트리 종료 때 close, fileserver migration V1–V5 고정 - P29: auxiliary 레인 → Gradle `jvm-test-suite`(BUILD-O3-5, build-logic 16,768 → 5,851줄), redis-sdk가 runtime을 api로(P22-new-3) - 통합: JPA API surface 기준선 재승인(이름 규칙 변경), migration lane에 V19 반영, messaging 통합 테스트가 jar 안 migration 목록 조회(ORCH-new-5) - P28·P29 에이전트가 세션 재시작으로 중단 — 커밋된 것만 합치고 결과 파일은 오케스트레이터가 확정, S6-#10a는 P30으로 검증: ./gradlew ci verifyDependencyLocks --warning-mode=fail(714 task) · mainCheck architectureCheck verifyPublicPathSnapshot :app-bootstrap:verifyEnvKeys configContractCheck · :app-bootstrap:integrationTest :sample-portfolio:integrationTest :sample-portfolio:systemTest integrationCheck · -p build-logic test · -p optional-platforms ci · releaseCheck qualificationBootJar 통과 Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
81 lines
4.0 KiB
Groovy
81 lines
4.0 KiB
Groovy
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.'
|
|
}
|
|
}
|