- shared-contract `Sha256`(약 65벌 흡수, notification `MessageDigestPort` 삭제), `HmacSha256`(서명 헬퍼), `Backoff`("full jitter" 뜻 하나),
`MdcKeys`(gRPC·STOMP에도 상관관계), registry edge application-notification → shared-contract
- application-core `TenantId` 하나로 web·GraphQL tenant 문법 통일, web operation 경로에 tenant 해석(JWT `tenant_id`)
- persistence-jpa `CallerTransaction` 하나(복사본 4벌 + `JpaStreamScope` 흡수), 범위 없는 멱등성·outbox 리포지토리 메서드 제거(E-6b)
- 주입된 `Clock` 우회 제거(objectstorage·websocket·mongo·web stream), GraphQL 오류가 HTTP request id 사용, notification UUIDv7은 uuid-creator
- 호출처 없는 `WebRequestContext`·argument resolver 삭제
- 결함 수정: `WebStreamRegistry` 상한 경합(ORCH-new-3 — bin 하나만 잠그는 lock 안에서 크기 확인, 원자 카운터로 슬롯 예약)
- 현황표: 소유자 결정 33(persistence-notification·fileserver → persistence-jpa edge), 34(id 포트 domain 전환 보류), 35(X2-P2-6b 나머지 보류)
검증: ./gradlew check architectureCheck verifyDependencyLocks verifyPublicPathSnapshot :app-bootstrap:verifyEnvKeys configContractCheck
:app-bootstrap:integrationTest :sample-portfolio:integrationTest :sample-portfolio:systemTest graphql·websocket systemTest
persistence-jpa jpaPlatformContractTest·postgresql{Idempotency,Outbox*}IntegrationTest --continue 통과(695 task)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
109 lines
6.0 KiB
Groovy
109 lines
6.0 KiB
Groovy
plugins {
|
|
id 'ca.spring-library'
|
|
id 'ca.spring-config'
|
|
id 'ca.api-surface'
|
|
}
|
|
|
|
dependencies {
|
|
implementation project(':application-core')
|
|
implementation project(':application-notification')
|
|
implementation project(':shared-contract')
|
|
implementation project(':adapter:outbound:support')
|
|
// UUIDv7 for notification ids: the generator the sample's identifier adapters already use.
|
|
implementation libs.uuid.creator
|
|
|
|
implementation 'org.springframework.boot:spring-boot-autoconfigure'
|
|
implementation 'org.springframework.boot:spring-boot-actuator'
|
|
implementation 'org.springframework.boot:spring-boot-actuator-autoconfigure'
|
|
implementation 'org.springframework.boot:spring-boot-health'
|
|
implementation 'org.slf4j:slf4j-api'
|
|
|
|
// Micrometer core for the metric sink that implements NotificationMetricsPort. The sink used
|
|
// to live in the composition root because the MeterRegistry does; but a MeterRegistry is an
|
|
// external system like any other, and an implementation of an application port is an
|
|
// outbound adapter wherever its dependency happens to be configured (BOOT-017). Its logging
|
|
// counterpart, LoggingNotificationMetrics, was already here.
|
|
implementation 'io.micrometer:micrometer-core'
|
|
|
|
// Notification Delivery Platform.
|
|
// - mail: the SMTP provider adapter is built on JavaMailSender/MimeMessageHelper, which is where
|
|
// multipart/alternative, inline resources and header validation already live. Rebuilding MIME
|
|
// by hand to avoid one dependency would be the more dangerous choice.
|
|
// - jackson-databind: provider payloads, callback bodies and the canonical variables payload are
|
|
// JSON. It stays inside this adapter; application-core never sees a JSON type.
|
|
implementation 'org.springframework.boot:spring-boot-starter-mail'
|
|
implementation 'org.springframework.boot:spring-boot-starter-json'
|
|
// JSON Schema 2020-12 validation of template variables, using the same validator and version the
|
|
// messaging adapter already depends on rather than a second implementation of the same spec.
|
|
//
|
|
// Jackson's YAML dataformat is excluded because schemas arrive as JSON strings and a second
|
|
// parser for a format this leaf never reads is surface for nothing. It does not remove YAML from
|
|
// the runtime — org.yaml:snakeyaml is on this classpath via spring-boot-starter, which is how
|
|
// Spring Boot reads application.yml. The comment here used to claim the stronger outcome, and
|
|
// the resolved graph had said otherwise for as long as it stood; the rule below states the claim
|
|
// resolution enforces.
|
|
// Thymeleaf is the reference HTML renderer, added as the engine only — not the Spring
|
|
// starter, which would drag a view resolver and a servlet integration onto an outbound
|
|
// adapter that renders strings and never serves a request.
|
|
implementation 'org.thymeleaf:thymeleaf'
|
|
|
|
implementation(libs.json.schema.validator) {
|
|
exclude group: 'tools.jackson.dataformat', module: 'jackson-dataformat-yaml'
|
|
exclude group: 'com.fasterxml.jackson.dataformat', module: 'jackson-dataformat-yaml'
|
|
}
|
|
|
|
// Amazon SES through the AWS SDK v2 `sesv2` client (owner decision 17, review S4-lead-3). It
|
|
// replaced a hand-written JDK HTTP gateway and SigV4 signer. The version is the catalog's
|
|
// `awsSdk`, the same one object storage uses, imported as the SDK BOM below and stated on each
|
|
// artifact so a composition that takes this leaf with one line resolves it without repeating the
|
|
// platform. The sync client runs on the SDK's Apache client, which follows no redirects; the
|
|
// Netty async client sesv2 would otherwise bring along has no caller here.
|
|
implementation("software.amazon.awssdk:sesv2:${libs.versions.awsSdk.get()}") {
|
|
exclude group: 'software.amazon.awssdk', module: 'netty-nio-client'
|
|
}
|
|
implementation "software.amazon.awssdk:apache-client:${libs.versions.awsSdk.get()}"
|
|
}
|
|
|
|
dependencyManagement {
|
|
imports {
|
|
mavenBom "software.amazon.awssdk:bom:${libs.versions.awsSdk.get()}"
|
|
}
|
|
}
|
|
|
|
// The exclusion above as something resolution enforces: this rule fails the build the moment any
|
|
// dependency brings the YAML dataformat back in. (A `rejectAll()` constraint would not: Spring's
|
|
// dependency management overrides the version it rejects.)
|
|
configurations.configureEach {
|
|
resolutionStrategy.componentSelection.all { selection ->
|
|
if (selection.candidate.module == 'jackson-dataformat-yaml') {
|
|
selection.reject('schemas arrive as JSON strings; a YAML parser is surface for a format this leaf never reads')
|
|
}
|
|
}
|
|
}
|
|
|
|
// The notification platform's public type surface (application-notification and this leaf) is a
|
|
// reviewed baseline; growth needs -PraiseNotificationApiSurfaceCeiling as well as the approval.
|
|
apiSurface {
|
|
label = 'Notification'
|
|
baseline = rootProject.file('../docs/notification/api-surface-snapshot.txt')
|
|
additionalSourceRoots = ['../../../application-notification/src/main/java']
|
|
description = 'NTF-022 — public type surface of the notification platform (application-notification + adapter:outbound:notification).'
|
|
rationale = [
|
|
'Every top-level public type under the platform packages. Growth is a reviewed change.',
|
|
]
|
|
}
|
|
|
|
// NotificationEvidenceVerifierTest's repository case holds docs/notification/evidence-manifest.json,
|
|
// the support matrix it grades and the evidence files it names to each other. A comparison with
|
|
// repository documents, so it runs in this leaf's `mainCheck`, not in the pull-request `test`
|
|
// (review 2026-09-24 BUILD-계획-B4-27). The verifier's fixture cases stay in `test`. A lane never
|
|
// reports up to date, so it needs no inputs declared for the files it reads.
|
|
strictTestLanes {
|
|
lane('notificationDocumentContractTest') {
|
|
tag = 'document-contract'
|
|
description = 'Holds the notification support matrix to the evidence manifest and the evidence it names.'
|
|
rejectSkipped = true
|
|
mainStage()
|
|
}
|
|
}
|