refactor(repo)!: 들여온 플랫폼을 src/platforms 아래로 묶는다

문제: src/ 최상위에 계층 폴더와 들여온 제품 폴더(messaging, grpc,
grpc-advanced)와 optional 빌드 폴더(optional-platforms)가 같은 높이로
놓여, 무엇이 이 애플리케이션의 계층인지 폴더만으로 안 보인다.
src/config/에는 빌드 전체 설정과 기능 하나가 주인인 데이터(jpa,
messaging, mongodb)가 섞여 있다.

고른 방법(소유자 결정 2026-11-07, 설계 가-1):
- git mv로 src/platforms/{messaging,grpc,grpc-advanced,optional-build}.
  registry source_path 28행만 바꾸고 Gradle 경로(:messaging:*, :grpc:*)는
  그대로다. optional 빌드의 이름(optional-platforms)도 그대로다.
- optional 빌드가 한 단계 깊어져, build-logic이 "optional 빌드의 부모 =
  주 빌드"로 가정한 네 곳(registry settings, ArchitecturePlugin, 테스트
  이미지 catalog, checkstyle·spotbugs 설정)을 MainBuild(위로 올라가며
  registry·설정 파일을 찾음)로 바꾼다.
- settings.gradle·build.gradle의 상대 경로, workflow의 -p 값과 경로,
  buf 작업 폴더를 고친다. buf breaking은 이동 전 baseline에서도 옛
  경로로 비교해 이동 PR에서 건너뛰지 않는다.
- config/jpa, config/messaging, config/mongodb의 데이터를 주인 leaf의
  release/로 옮기고 읽는 빌드 줄·테스트·스크립트·문서를 고친다.
- 루트 CLAUDE.md 5절에 최상위 폴더 지도를 한 줄로 적는다.
버린 대안: Gradle 루트를 저장소 루트로(가-3, CI 재편 때 다시 봄),
application-* 묶기(가-2, 파생 서비스 충돌이 큼).

위험·한계: Gradle 문서의 "이름 = 위치" 권고와 한 단계 어긋난다
(:messaging:x가 platforms/messaging/x). 옮긴 폴더를 고쳐 쓰던 파생
서비스는 이름 바뀜 충돌이 날 수 있다(B-52). docs/capability-status.md
「제거된 코드」 표와 docs/work/evidence.md의 옛 경로는 이력이라 두었다.

검증(desktop, 트리 2b3354a4, ~/t1-layout-logs/):
- ./gradlew :ci :verifyDependencyLocks --warning-mode=fail --continue
  첫 실행 rc=1: MessagingAuthorityContractTest가 src/messaging을 찾아 실패
  → 경로를 고침. 두 번째 rc=1: messaging-policy
  MessagingAdmissionControllerTest.aWaitingCallerIsAdmittedOnceAPermitIsReturned
  (2초 대기 경쟁, 부하 7.3에서 한 번 실패, 코드 변경 없는 leaf) → --rerun
  3회 모두 통과. 세 번째 rc=0
- -p platforms/optional-build ci rc=0, 두 빌드의 verifyStrictLaneStages
  --dry-run rc=0, -p build-logic check rc=0
- :app-bootstrap:documentContractTest
  :adapter:outbound:persistence-mongo:mongoDocumentContractTest rc=0
- ./gradlew projects(주 빌드)와 optional 빌드 projects의 프로젝트 목록이
  이동 전 트리와 같다(Gradle 경로 불변)
- check-work-docs.py, 상대 링크 검사 rc=0

Refs: design-docs repo-structure/README.md 3.1, repo-structure/01-backend-layout.md 6.1
BREAKING CHANGE: src/messaging·src/grpc·src/grpc-advanced·src/optional-platforms가 src/platforms/ 아래로, src/config/{jpa,messaging,mongodb}가 주인 leaf의 release/로 옮겨졌다. optional 빌드는 -p platforms/optional-build로 부른다. docs/upgrade/2026-11-maturity-review.md B-52.
This commit is contained in:
DongHyeonka
2026-11-07 13:04:54 +09:00
parent 50cd7154d0
commit 8d69e599a3
850 changed files with 271 additions and 180 deletions
+21 -10
View File
@@ -65,15 +65,15 @@ jobs:
- uses: ./.github/actions/setup-gradle-java
- name: Verify the optional gRPC platform build
working-directory: src
run: ./gradlew -p optional-platforms ci --stacktrace
run: ./gradlew -p platforms/optional-build ci --stacktrace
# The optional build's own lane-reachability check: the main build's cannot see these lanes
# (review 2026-11-03 RR-06-03).
- name: Require every optional-platform strict lane to be in an executed stage
working-directory: src
run: ./gradlew -p optional-platforms :verifyStrictLaneStages --dry-run --stacktrace
run: ./gradlew -p platforms/optional-build :verifyStrictLaneStages --dry-run --stacktrace
# gRPC schema policy (owner decision 18). protoc compiles src/grpc/grpc-contract inside the
# optional-platforms build above; lint and breaking-change policy belong to Buf, configured by
# gRPC schema policy (owner decision 18). protoc compiles src/platforms/grpc/grpc-contract inside
# the optional-platforms build above; lint and breaking-change policy belong to Buf, configured by
# buf.yaml next to the schema. Buf is a native binary rather than a Maven artifact, so it runs here
# and not inside Gradle — and nothing in the repository re-implements its rules.
grpc-proto-buf:
@@ -88,23 +88,34 @@ jobs:
version: 1.73.0
setup_only: true
- name: Lint the gRPC schema
working-directory: src/grpc/grpc-contract
working-directory: src/platforms/grpc/grpc-contract
run: buf lint
- name: Refuse a breaking change to the gRPC schema
working-directory: src/grpc/grpc-contract
working-directory: src/platforms/grpc/grpc-contract
env:
# Pull request: the target branch. Push: the commit this push replaced.
BASELINE: ${{ github.event_name == 'pull_request' && format('origin/{0}', github.base_ref) || github.event.before }}
run: |
set -euo pipefail
baseline_commit="$(git rev-parse --verify --quiet "${BASELINE}^{commit}" || true)"
if [[ -z "${baseline_commit}" ]] \
|| ! git cat-file -e "${baseline_commit}:src/grpc/grpc-contract/buf.yaml" 2>/dev/null; then
# The module moved from src/grpc to src/platforms/grpc on 2026-11-07. A baseline from
# before the move holds it at the old path, and comparing against that path keeps the
# breaking check running across the move instead of skipping it once.
baseline_dir=""
if [[ -n "${baseline_commit}" ]]; then
for candidate in src/platforms/grpc/grpc-contract src/grpc/grpc-contract; do
if git cat-file -e "${baseline_commit}:${candidate}/buf.yaml" 2>/dev/null; then
baseline_dir="${candidate}"
break
fi
done
fi
if [[ -z "${baseline_dir}" ]]; then
# The first change that introduces the module has nothing to be compatible with.
echo "::notice::grpc-proto-buf: baseline ${BASELINE} has no src/grpc/grpc-contract/buf.yaml; breaking check skipped."
echo "::notice::grpc-proto-buf: baseline ${BASELINE} has no grpc-contract/buf.yaml; breaking check skipped."
exit 0
fi
buf breaking --against "../../../.git#ref=${baseline_commit},subdir=src/grpc/grpc-contract"
buf breaking --against "../../../../.git#ref=${baseline_commit},subdir=${baseline_dir}"
release-gate:
needs:
+4 -4
View File
@@ -207,7 +207,7 @@ jobs:
- name: Run every optional-platform performance-category strict lane
if: always()
working-directory: src
run: ./gradlew -p optional-platforms performanceCheck --continue --stacktrace
run: ./gradlew -p platforms/optional-build performanceCheck --continue --stacktrace
- name: Publish the performance lane reports
if: always()
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
@@ -234,7 +234,7 @@ jobs:
# `grpc-operation-ledger-jpa:integrationTest`, which certifies the atomic
# `INSERT ... ON CONFLICT DO NOTHING` claim that durable mutation idempotency rests on against a
# real PostgreSQL. It was registered in Gradle, listed in `strictTestLanes`, and invoked by
# nothing: `-p optional-platforms ci` reaches `checkAll`, `qualityCheck` and the dependency
# nothing: `-p platforms/optional-build ci` reaches `checkAll`, `qualityCheck` and the dependency
# verifier, none of which runs a lane whose category is INTEGRATION, and release.yml's gRPC gate
# names only the three grpc-testkit lanes.
#
@@ -250,13 +250,13 @@ jobs:
- uses: ./.github/actions/setup-gradle-java
- name: Certify the gRPC operation ledger against real PostgreSQL
working-directory: src
run: ./gradlew -p optional-platforms integrationCheck --stacktrace
run: ./gradlew -p platforms/optional-build integrationCheck --stacktrace
- name: Publish the optional-platform lane reports
if: always()
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
with:
name: grpc-optional-platform-integration-reports
path: src/optional-platforms/**/build/reports/tests/
path: src/platforms/grpc*/**/build/reports/tests/
if-no-files-found: warn
# Dynamic half of the compose-profile contract. Every blocking lane the matrix declares runs on
@@ -15,7 +15,7 @@ name: messaging-certification
on:
pull_request:
paths:
- "src/messaging/**"
- "src/platforms/messaging/**"
- ".github/workflows/messaging-certification.yml"
# Every Gradle job here installs its toolchain through this composite action, so a change to
# it changes what this gate runs.
@@ -47,5 +47,5 @@ jobs:
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
with:
name: messaging-broker-certification-evidence
path: src/messaging/messaging-kafka/build/messaging-certification/
path: src/platforms/messaging/messaging-kafka/build/messaging-certification/
if-no-files-found: warn
+5 -5
View File
@@ -132,7 +132,7 @@ jobs:
- uses: ./.github/actions/setup-gradle-java
- name: Run the gRPC Stable certification lanes
working-directory: src
run: ./gradlew -p optional-platforms releaseCheck --stacktrace
run: ./gradlew -p platforms/optional-build releaseCheck --stacktrace
# The operation ledger's real-PostgreSQL lane ran only on main and nightly
# (integration-main.yml), so a tag could be cut from a main whose ledger lane was red. It needs
# Docker, which a release runner has (review 2026-11-01 03-12).
@@ -140,15 +140,15 @@ jobs:
working-directory: src
env:
TESTCONTAINERS_REUSE_ENABLE: "false"
run: ./gradlew -p optional-platforms integrationCheck --stacktrace
run: ./gradlew -p platforms/optional-build integrationCheck --stacktrace
- name: Publish the gRPC release evidence
if: always()
uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # actions/upload-artifact@v4.6.2
with:
name: grpc-release-evidence
path: |
src/grpc/grpc-testkit/build/reports/tests/
src/grpc/grpc-operation-ledger-jpa/build/reports/tests/
src/platforms/grpc/grpc-testkit/build/reports/tests/
src/platforms/grpc/grpc-operation-ledger-jpa/build/reports/tests/
if-no-files-found: warn
# Each gate runs as its own single-line `./gradlew <task>` step so that a failure names the gate
@@ -194,7 +194,7 @@ jobs:
# docs/jpa/support-matrix.md recorded all three as covered. start() now fails closed on a
# multi-version selection, so this matrix is the only way the Stable majors get covered.
#
# config/jpa/release-registry.json is the gate-task source: jpaReleaseQualification (persistence-jpa
# persistence-jpa release/release-registry.json is the gate-task source: jpaReleaseQualification (persistence-jpa
# build.gradle) depends on its blocking gates, so a gate naming a missing task fails when the task
# graph is built, and JpaReleaseRenderingTest holds this matrix and the promotion list below to the
# registry's Stable majors. Editing one without the other fails the persistence-jpa unit lane.
+3 -3
View File
@@ -86,7 +86,7 @@ root `CLAUDE.md`는 작업을 시작할 때 읽는 지도이고, 이 목록을
`releaseCheck`, `qualityCheck`, `configContractCheck`)과 버전/리비전. `verifyStrictLaneStages
--dry-run`(PR 게이트)은 그 빌드에서 `explicitOnly`가 아닌 strict lane이 workflow가 실제로 실행하는
단계(main 빌드: `ci`·`mainCheck`·`integrationCheck`·`performanceCheck`·
`releaseCheck`, optional-platforms 빌드: `-p optional-platforms`로 부르는 `ci`·`integrationCheck`·
`releaseCheck`, optional-platforms 빌드: `-p platforms/optional-build`로 부르는 `ci`·`integrationCheck`·
`performanceCheck`·`releaseCheck`) 중 하나에 들어 있는지, 그리고 workflow의 접힌(`>`) run 블록이 빈
줄 때문에 옵션을 별개 명령으로 떼어 내지 않는지 검사한다. 두 빌드가 각자 검사를 돌린다. `-x`로 뺀
lane(Gradle처럼 축약 이름도 맞춰 본다)은 덮이지 않는다. Gradle이 작업을 돌리지 않는 명령(`--dry-run`·
@@ -232,7 +232,7 @@ cd src
./gradlew mainCheck # main 단계 = env 계약·전체 기동·public path·전송/메시징 레인·leaf 문서 대조 레인·기능 생성 왕복(verifyFeatureScaffold)·테스트 코드 정적 분석(testQualityCheck)
./gradlew integrationCheck # 실제 컨테이너 integration 레인 전체(main·nightly, Docker 필요)
./gradlew performanceCheck # 부하·종료·자원 한계 레인(main·nightly). 상한은 항상 단언, 끄면 실패
./gradlew verifyStrictLaneStages --dry-run # 이 빌드의 strict lane이 workflow가 실행하는 단계에 속하는지(optional 빌드는 -p optional-platforms로 따로)
./gradlew verifyStrictLaneStages --dry-run # 이 빌드의 strict lane이 workflow가 실행하는 단계에 속하는지(optional 빌드는 -p platforms/optional-build로 따로)
./gradlew verifyPublicPathSnapshot
./gradlew :app-bootstrap:verifyEnvKeys
```
@@ -301,7 +301,7 @@ Docker/runtime 규칙:
1. `src/settings.gradle`의 `rootProject.name`을 새 프로젝트명으로 바꾼다.
2. Java package `dev.caskeleton`을 새 organization/project package로 바꾼다.
gRPC 플랫폼을 쓰면 proto 조직 이름 `caskeleton`(`src/grpc/grpc-contract/src/main/proto/caskeleton/`의
gRPC 플랫폼을 쓰면 proto 조직 이름 `caskeleton`(`src/platforms/grpc/grpc-contract/src/main/proto/caskeleton/`의
디렉터리, 각 `.proto`의 `package`·`java_package`)도 함께 바꾸고 `buf lint`로 확인한다.
3. `CaSkeletonApplication` 이름을 새 애플리케이션 이름으로 바꾼다.
4. production 모듈에는 목표 도메인의 entity, repository port, use case, adapter만 추가한다.
+3 -2
View File
@@ -54,11 +54,12 @@ brief(작업 지시문)가 있으면 brief의 범위·크기·완료 기준이
## 5. 코드만 보고는 헷갈리는 곳
- **최상위 폴더는 정해진 것만 둔다.** 저장소 루트는 `compose.yaml`(개발 환경)·`compose/`(그 보조 파일)·`docs/`·`scripts/`·`src/`(Gradle 루트)다. `src/` 아래는 계층 leaf 폴더, `composition/`(조립), `platforms/`(들여온 제품: `messaging`·`grpc`·`grpc-advanced`와 optional 빌드 `optional-build`), Gradle 루트 표준(`build-logic`·`gradle`·`config`)이다. 테스트 환경 파일은 그 lane을 가진 leaf 안에 둔다.
- **leaf 목록은 registry 하나다.** 문서는 leaf 개수를 적지 않는다(적힌 수는 leaf가 늘면 틀린다). runtime membership 목록은 없다. 조립 루트가 받을 수 있는 모듈은 registry의 `allowed_dependencies`가 정하고, 방향 게이트가 그 밖의 edge를 막는다.
- **`src/messaging/*`는 Clean Architecture 계층이 아니다.** 자기 API·SPI·adapter·조립 경계를 가진, 들여온(vendored) 메시징 제품이다. `domain-core`·`application-core`·`shared-contract`에 의존하지 않는다. 이 애플리케이션은 `adapter:outbound:messaging`의 bridge로만 닿는다. 이유와 지역 규칙은 `src/messaging/CLAUDE.md`다.
- **`src/platforms/messaging/*`는 Clean Architecture 계층이 아니다.** 자기 API·SPI·adapter·조립 경계를 가진, 들여온(vendored) 메시징 제품이다. `domain-core`·`application-core`·`shared-contract`에 의존하지 않는다. 이 애플리케이션은 `adapter:outbound:messaging`의 bridge로만 닿는다. 이유와 지역 규칙은 `src/platforms/messaging/CLAUDE.md`다.
- **`composition:*` leaf는 조립만 한다.** outbox relay, 멱등성 executor, durable operation처럼 bootstrap에서 떼어 낸 조립이다. 각각 `runtimeOnly` 한 줄로 고른다.
- **capability는 한 줄로 켜고 끈다.** 기본 조립은 web inbound, 운영 관측, core들, support·identifier뿐이다. JPA도 `src/app-bootstrap/build.gradle`의 `runtimeOnly` 한 줄로 켠다. 규칙은 `AGENTS.md` 「부가 기능(capability) 모듈 규칙」이다.
- **gRPC 플랫폼 라이브러리는 다른 빌드다.** `src/grpc/*`·`src/grpc-advanced/*`(registry의 `"build": "optional-grpc"`)는 `-p optional-platforms`로 돈다. `adapter:inbound:grpc`는 애플리케이션 adapter라 주 빌드에 있다.
- **gRPC 플랫폼 라이브러리는 다른 빌드다.** `src/platforms/grpc/*`·`src/platforms/grpc-advanced/*`(registry의 `"build": "optional-grpc"`)는 `-p platforms/optional-build`로 돈다. `adapter:inbound:grpc`는 애플리케이션 adapter라 주 빌드에 있다.
- **새 기능의 예시는 `scripts/new-feature.sh`의 출력이다.** 샘플 모듈은 2026-11-07에 지웠다. 기법 예시는 `docs/manual/`이 실제 코드(fileserver, durable operation)를 가리킨다.
- **성능 lane에는 단언을 끄는 스위치가 없다.** convention이 상한을 매번 단언하고, `performance.assertions.enabled`에 `true` 아닌 값이 들어오거나 skip이 있으면 테스트 전에 실패한다. 손으로 돌리든 workflow든 같다(`AGENTS.md` 「Gradle 정책 권위」).
- **저장소 파일을 읽는 테스트는 태그가 있다.** 문서와 대조하는 테스트는 `document-contract`(main 단계 `mainCheck`), 빌드 스크립트·workflow를 읽는 테스트는 `repository-contract`(PR)다. 문서를 고치면 그 문서를 읽는 테스트를 찾는다.
+1 -1
View File
@@ -102,7 +102,7 @@ Docker-dependent lanes fail closed rather than skipping, matching the existing
| `settings.gradle.kts` module registration | Fail-closed 19-leaf registry | No registry change: leaf identity, Gradle path, allowed dependencies, and runtime memberships are unchanged. |
| `infra/jpa/{postgres,roles,toxiproxy}` | Repository already owns `infra/` | 2026-11-07에 지웠다(쓰는 곳이 없거나 운영 인프라 파일). 운영 DB 조건은 `docs/jpa/security.md`로 옮겼다. |
| `docs/jpa/**`, `docs/adr/ADR-JPA-*`, `.github/workflows/jpa-*.yml` | Repository already owns `docs/` and `.github/workflows/` | Created at the same repository-relative paths. |
| release blocking aggregate | `jpaReleaseQualification` (persistence-jpa `build.gradle`) over `config/jpa/release-registry.json`, run per PostgreSQL major by the `jpa-release-gate` job in `.github/workflows/release.yml` | The registry names the blocking lanes; Gradle defines how each lane runs; CI only schedules the matrix. | |
| release blocking aggregate | `jpaReleaseQualification` (persistence-jpa `build.gradle`) over `persistence-jpa/release/release-registry.json`, run per PostgreSQL major by the `jpa-release-gate` job in `.github/workflows/release.yml` | The registry names the blocking lanes; Gradle defines how each lane runs; CI only schedules the matrix. | |
| Per-task `git add` + `git commit` | `AGENTS.md`: commit policy is `human-only`; agents do not stage, commit, amend, or push | Implementation is delivered unstaged. This is the only plan step intentionally not executed, and it is recorded here. |
| Querydsl as an optional module dependency | Querydsl is not part of this repository's dependency set | `querydsl` is implemented against the plan's contracts with the Querydsl types kept behind `compileOnly`, so the Stable runtime classpath never carries Querydsl and a deployment opting in adds the artifact itself. |
| Hibernate Envers as a module dependency | Envers is not part of this repository's dependency set | Same treatment as Querydsl: `compileOnly` + explicit opt-in, matching the plan's "Envers is opt-in and never enabled by a global base class". |
+1 -1
View File
@@ -1,7 +1,7 @@
# JPA Persistence Platform — Support Matrix
**This document is a rendering. The machine-readable source is
[`src/config/jpa/release-registry.json`](../../src/config/jpa/release-registry.json).**
[`src/adapter/outbound/persistence-jpa/release/release-registry.json`](../../src/adapter/outbound/persistence-jpa/release/release-registry.json).**
`JpaReleaseManifest` used to parse this file with regular expressions: every `PostgreSQL NN` it
mentioned became a supported version, whatever table or sentence produced the match. An Experimental
+1 -1
View File
@@ -27,7 +27,7 @@
> `modules.json`은 messaging leaf의 `gradle_path`와 허용 의존성을 관리하지만
> `runtime_memberships` 필드는 없다. 실제 런타임 편입은 `app-bootstrap`의 Gradle 의존성과 starter /
> auto-configuration 경로가 결정한다. 아래 등급은 "무엇이 증명되었는가"를 말하며 런타임 편입 여부와
> 같은 축이 아니다. 자세한 composition/cutover 상태는 `src/messaging/CLAUDE.md`가 소유한다.
> 같은 축이 아니다. 자세한 composition/cutover 상태는 `src/platforms/messaging/CLAUDE.md`가 소유한다.
## 브로커 등급
+1 -1
View File
@@ -13,7 +13,7 @@ enables the capability; construction is refused otherwise.
| Topology | A real sharded cluster. A replica set cannot exercise routing. |
| Server | MongoDB 7.0 or 8.0. |
| Privilege | `MongoPrincipalRole.SHARD_ADMIN` for the admin plane; the application role is unchanged. |
| Gate | **Not promoted.** No `mongoShardedTest` lane is registered, and a sharded cluster is not an environment this repository stands up. Listed under `experimental_contracts` in `src/config/mongodb/release-contracts.json`; promoting it needs the lane, its required class, and protected-environment evidence to exist first. |
| Gate | **Not promoted.** No `mongoShardedTest` lane is registered, and a sharded cluster is not an environment this repository stands up. Listed under `experimental_contracts` in `src/adapter/outbound/persistence-mongo/release/release-contracts.json`; promoting it needs the lane, its required class, and protected-environment evidence to exist first. |
## Shard key
+2 -2
View File
@@ -10,7 +10,7 @@
- 대응하는 Test 태스크 없음
- 공통 스키마 validator 없음
따라서 `config/messaging/readiness-cards.yaml`의 카드는 모두 `maturity: not-implemented`다.
따라서 `src/adapter/outbound/messaging/release/readiness-cards.yaml`의 카드는 모두 `maturity: not-implemented`다.
유일하게 `implemented-candidate`였던 `json-schema-envelope.v1`은 그 구현(adapter messaging의
`JsonSchemaIntegrationEventEncoder`와 `verifyMessagingJsonSchemaV1`)을 2026-09-25에 삭제하면서
`not-implemented`로 내렸다. 남은 evidence producer는 `verifyMessagingContracts` 하나다.
@@ -41,7 +41,7 @@ verifyMessagingTargetBindingPreflight
1. 각 시나리오를 실제로 실행하는 Test 태스크.
2. 그 실행 결과(JUnit XML)에서 payload-free manifest를 만드는 producer.
3. `config/messaging/evidence/build-evidence-manifest-v1.schema.json`으로 그 manifest 바이트를
3. `src/adapter/outbound/messaging/release/evidence/build-evidence-manifest-v1.schema.json`으로 그 manifest 바이트를
검증하는 단계(build-tools `VerifyMessagingEvidenceTask`가 쓰고 바로 검증한다).
4. 위 셋이 모두 생긴 다음에 `verifyMessaging<Scenario>R2` 태스크 등록.
+1 -1
View File
@@ -22,7 +22,7 @@ status: active
1. Stop rollout and keep the failed revision out of readiness. Do not route traffic to a partially
migrated instance.
2. Identify the exact stream from `src/config/jpa/readiness-cards.yaml`. Each stream has an
2. Identify the exact stream from `src/adapter/outbound/persistence-jpa/release/readiness-cards.yaml`. Each stream has an
independent `location` and `history-table`; do not infer ownership from a broad
`classpath:db/migration` scan.
3. From a privileged migration session, capture the stream state before changing anything:
+3 -2
View File
@@ -64,7 +64,7 @@
| B-09 | `SecuritySettings`(adapter:inbound:web): `audience`가 `String` → `List<String>`. `@ConfigurationProperties` 제거, `SecuritySettings.bind(Environment)`로 strict 바인딩. 생성자 `(String, String, List)` → `(String, List<String>, List<String>)`. `bootstrap.security.AuthenticationModeSettings` 삭제 | `audience()`를 문자열로 쓰는 코드, 직접 생성하는 테스트 컴파일 오류 | `List<String>`으로 바꾼다. 인증 모드는 `SecuritySettings.authMode()`에서 읽는다 | `34565130`(List), `5786126c`(strict·삭제) · `src/adapter/inbound/web/.../settings/SecuritySettings.java` |
| B-10 | adapter 공개 타입 삭제·이동: graphql `execution.GraphQlTimeoutPolicy`·`dataloader.GraphQlDataLoaderRequestRegistry` 삭제(`runtime.GraphQlDeadlineInstrumentation`·`GraphQlPerParentFetchInstrumentation` 추가). jpa `experimental.tenant.TenantId` 삭제 → `dev.caskeleton.application.tenant.TenantId`. persistence-notification의 엔티티는 `...platform.entity`, 저장소는 `...platform.repository`로 이동, `inbox` 하위 클래스는 `platform`으로 올라옴, `PreferenceJpaRepository`·`SuppressionJpaRepository` 삭제, `JpaNotificationSideEffect` → application-notification `dispatch.SuppressionSideEffect`. graphql `GraphQlClientPolicy.effectivePageSize(Integer, Integer)` 삭제 → `pagination.GraphQlConnectionPolicy.effectivePageSize`(상한 검사 포함, 재리뷰 RR-01-14). grpc(optional-platforms) `GrpcOperationLedger.release(identity)` → `boolean release(identity, GrpcClaimToken)`: 진행 중이고 그 token이 가진 claim만 지운다(RR-01-15) | import 실패, 호출부·직접 구현한 ledger 컴파일 오류. leaf `check`의 API surface 비교가 스냅샷과 달라 실패(자기 공개 타입을 더했다면 merge 충돌) | import를 바꾼다. 스냅샷 파일은 upstream 것을 받고 자기 추가분을 다시 승인한다 | `1400dc15`·`5786126c` · `docs/architecture/graphql-api-surface.txt`, `docs/architecture/jpa-api-surface.txt`(166→165), `docs/notification/api-surface-snapshot.txt`(362→364) |
| B-11 | 조립·지원 타입: `bootstrap.autoconfigure.operation.DurableOperationConfig` → `composition:durable-operation`의 `composition.operation.DurableOperationAutoConfiguration`. `bootstrap.settings.LoggingSettings` 삭제. `composition.outbox.OutboxLeaderElectionToken` 삭제. `TracingSamplingEnvironmentPostProcessor` → `TracingEnvironmentPostProcessor`, `StartupOrder.TRACING_SAMPLING` → `TRACING_PROPERTIES`. `StartupRuleRunner(Environment, List<StartupRule>)` → `StartupRuleRunner(Environment)`. `SecretSourceValidator(ConfigurableEnvironment, SecretSourcePort, List)` → `SecretSourceValidator(Supplier<List<RequiredProductionSecrets>>)` | 이 타입을 참조하는 코드·테스트 컴파일 오류 | 새 이름으로 바꾼다 | `1400dc15`, `34565130`, `bbe944bd` · `src/composition/durable-operation/`, `src/adapter/outbound/support/.../startup/` |
| B-39 | vendored messaging SPI `KafkaQuarantinePublisher`(`messaging-kafka`): `quarantine(ConsumerRecord, Throwable)` → `quarantine(ConsumerRecord, FailureCategory category, Throwable reason)`. 호출자가 격리 이유(읽을 수 없는 레코드 `DESERIALIZATION`, 시도 예산 소진은 실패의 category 또는 `POISON_MESSAGE`)를 넘기고, 구현은 그것을 `msg.failure-category` header로 쓴다 | 이 SPI를 직접 구현한 서비스는 `does not override abstract method` 컴파일 오류. 람다로 만든 것도 인자 수 오류 | 세 인자 메서드로 고친다. category를 header나 저장소에 그대로 남겨야 redrive가 두 경우를 가른다(템플릿 `KafkaDeadLetterQuarantine`, 테스트 `KafkaDeadLetterQuarantineTest`) | `bbe944bd`(리뷰 06-14), 3차 수정에서 목록에 추가(재리뷰 2차 RR-02-16) · `src/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/KafkaQuarantinePublisher.java` |
| B-39 | vendored messaging SPI `KafkaQuarantinePublisher`(`messaging-kafka`): `quarantine(ConsumerRecord, Throwable)` → `quarantine(ConsumerRecord, FailureCategory category, Throwable reason)`. 호출자가 격리 이유(읽을 수 없는 레코드 `DESERIALIZATION`, 시도 예산 소진은 실패의 category 또는 `POISON_MESSAGE`)를 넘기고, 구현은 그것을 `msg.failure-category` header로 쓴다 | 이 SPI를 직접 구현한 서비스는 `does not override abstract method` 컴파일 오류. 람다로 만든 것도 인자 수 오류 | 세 인자 메서드로 고친다. category를 header나 저장소에 그대로 남겨야 redrive가 두 경우를 가른다(템플릿 `KafkaDeadLetterQuarantine`, 테스트 `KafkaDeadLetterQuarantineTest`) | `bbe944bd`(리뷰 06-14), 3차 수정에서 목록에 추가(재리뷰 2차 RR-02-16) · `src/platforms/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/KafkaQuarantinePublisher.java` |
| B-41 | enum 값 추가: `IdempotencyStartOutcome.LEASE_EXPIRED`, `IdempotencyRenewOutcome.LEASE_EXPIRED`(둘 다 `carriesOwner()`=false). 주인이 아직 기록을 가졌지만 processing lease가 끝나 시작·renew를 거절한다는 뜻이다. 전에는 PostgreSQL이 둘 다 `NOT_OWNER`, Redis가 renew는 `NOT_OWNER`·시작은 `STARTED`였다 | `default` 없는 switch 식이 "does not cover all possible input values" 컴파일 오류. 직접 구현한 store는 `IdempotencyStoreContract`의 새 시간 케이스(lease 지난 시작·renew)에서 실패 | 새 값 분기를 더한다. `LEASE_EXPIRED`를 `NOT_OWNER`처럼 "기록을 잃었다"로 읽지 않는다 — 실행 중이면 주인은 여전히 `complete`·`markFailed` 한다. store는 lease가 끝난 시작·renew에 이 값을 돌려준다 | r9(재리뷰 README 15 남음, RR5-01-02) · `src/application-core/.../idempotency/IdempotencyStartOutcome.java`, `IdempotencyRenewOutcome.java`, `src/application-core/src/testFixtures/.../IdempotencyStoreContract.java` |
### 3.2 설정·기동 — 기동이 실패하거나 런타임 예외가 난다
@@ -77,7 +77,7 @@
| B-15 | 기동 rule이 모든 singleton보다 먼저 돈다(`StartupRuleRunner`가 `BeanFactoryPostProcessor`). `StartupRule`과 `RequiredProductionSecrets` bean은 `static @Bean`이고 `Environment`, bean factory, static 무인자 `RequiredProductionSecrets`의 `ObjectProvider`만 받아야 한다. 두 타입의 클래스는 `@Value`·`@Autowired`·`@Inject`·`@Resource` 멤버, `@PostConstruct`·`@PreDestroy`, `@ConfigurationProperties`를 가질 수 없다(post-processor보다 먼저 만들어져 비어 있게 된다, RR2-04-03) | non-static `@Bean`이거나 다른 bean을 받으면 기동 실패 `startup rule or secret list '<이름>' created [<bean>] while creating it ... Declare the rule with a static @Bean method ...`, 위 멤버가 있으면 `'<이름>' (...) is a StartupRule or RequiredProductionSecrets ... but it needs one: [...]`(둘 다 exit 78, 둘 다 모든 프로필. runner가 rule과 비밀 목록을 프로필과 무관하게 먼저 만들어, 인터페이스 타입 `@Bean`이 돌려준 실제 클래스까지 본다, RR3-04-01) | rule 선언을 `static`으로, 인자를 위 셋으로 줄인다. 값은 `violations(Environment)`가 받는 `Environment`에서 읽는다. 다른 bean이 필요한 검사는 rule이 아니라 일반 bean으로 둔다 | `34565130`, `bbe944bd` · `src/adapter/outbound/support/.../startup/StartupRule.java`, `StartupRuleRunner.java` |
| B-16 | 권한 가드(새 `PermissionEnforcementGuard`): `@SystemInvoked` 유스케이스가 bean이면 기동 실패. `@RequiresPermission`을 단 bean에 적용되는 advisor가 없어도 기동 실패. ArchUnit `SYSTEM_INVOKED_USE_CASES_DECLARE_NO_PERMISSION`, `ONLY_SYSTEM_CALLERS_REACH_SYSTEM_INVOKED_USE_CASES`, `SYSTEM_CALLERS_ARE_SYSTEM_DRIVEN_INBOUND_ADAPTERS`, `USER_TRANSPORTS_DO_NOT_REACH_SYSTEM_CALLERS`, `SYSTEM_CALLERS_HAVE_ONLY_PROJECT_SUPERTYPES` 추가, 새 표시 `@SystemCaller` | 기동 실패 `@SystemInvoked use cases are registered as beans ...` 또는 `beans declare @RequiresPermission but no advisor enforces it ...`(exit 72). `@SystemCaller`가 아닌 inbound adapter가 그 유스케이스를 부르거나, 사용자 전송(controller 등)이 `@SystemCaller` bean을 직접·중간 클래스를 거쳐·그 작업이 구현하는 프로젝트 인터페이스로 부르면 architectureTest 실패. `@SystemCaller` 클래스가 `Runnable`·`ApplicationRunner` 같은 프로젝트 밖 타입을 구현·상속해도 실패. 설정(`@Configuration`)은 웹 bean(`WebMvcConfigurer`·CORS 설정·controller bean)과 handler bean을 함께 등록해도 사용자 전송으로 세지 않지만, 요청 처리기 타입(함수형 route·data fetcher·interceptor)에 의존하면 사용자 전송으로 센다. 처리 코드를 설정에 직접 쓰든, 다른 클래스의 메서드를 참조해 등록만 하든 같다. 설정 안에 중첩된 클래스는 설정용 타입(configurer·registry·CORS 설정·`RequestMethod`)에만 의존할 때를 빼고 다른 클래스처럼 사용자 전송 타입으로 판정한다(중첩된 JAX-RS 자원·`@ServerEndpoint`도 잡힌다). STOMP inbound channel interceptor(`ChannelInterceptor`·`ExecutorChannelInterceptor`)도 사용자 전송 타입이자 요청 처리기 타입이다. 사용자 전송 패키지 밖에 둔 interceptor, 설정에 중첩한 interceptor(익명 클래스 포함), interceptor를 구현한 설정이 `@SystemCaller`에 닿거나, interceptor를 `@Bean`으로 내놓는 설정이 `@SystemCaller` bean도 만들면 실패한다(2026-11-07 전에는 STOMP 헤더 타입을 읽는 interceptor만 잡혔다). record·enum이 언어로 받는 상위 타입(`Record`·`Enum` 등)과 예외 클래스는 프로젝트 밖 상위 타입으로 세지 않는다 | 시스템만 부르는 쓰기 유스케이스는 composition에서 `new`로 만들어 스케줄러에 넘기거나, 메시지 handler·예약 작업이면 그 클래스에 `@SystemCaller`를 달고 생성자에서 `new`로 만든다. 예약 작업은 서비스 leaf의 `..adapter.inbound.scheduler..` 패키지에 둔다. 세 경로와 두는 곳은 매뉴얼 07장 「시스템이 부르는 쓰기」(handler 작업 순서는 09장 「소비」 4단계). "지금 실행" endpoint가 필요하면 `@RequiresPermission` 유스케이스를 따로 만든다. 작업을 task scheduler에 직접 등록하던 코드는 작업이 `Runnable`을 구현하는 대신 등록하는 곳에서 `job::run`을 넘긴다. route·data fetcher·interceptor 등록은 handler bean을 만드는 설정과 다른 설정에 둔다. STOMP channel interceptor 등록도 같다. `@RequiresPermission`을 쓰면 web adapter(`MethodSecurityConfig`)가 조립돼 있어야 한다 | `1400dc15`, `bbe944bd`, r9 · `src/composition/service-runtime/.../authorization/PermissionEnforcementGuard.java`, `src/application-core/.../security/SystemInvoked.java`, `SystemCaller.java` |
| B-17 | `IntegrationEventDraft`: `eventId`·`causationId`는 소문자 UUIDv7만. ArchUnit `INTEGRATION_EVENT_DRAFTS_ARE_BUILT_BY_THE_SHARED_HELPER`: `new IntegrationEventDraft<>(...)` 금지, `IntegrationEventDrafts.draft(...)`만 | 이벤트를 만드는 쓰기 요청이 `IllegalArgumentException: eventId must be a canonical lower-case UUIDv7...`로 실패. architectureTest 실패 | event id를 UUIDv7로 만든다(예: sample `UuidOutboxEventIdFactory`가 `UuidCreator.getTimeOrderedEpochPlus1()`). draft는 헬퍼로 만든다. tenant가 없는 이벤트는 `IntegrationEventDrafts.SINGLE_TENANT_SCOPE`(`global`) | `1400dc15`, `bbe944bd` · `src/application-core/.../messaging/event/IntegrationEventDraft.java`, `IntegrationEventDrafts.java` |
| B-18 | `MessageHandler.schemaVersions()`(vendored `messaging-core-api`, default `{v1}`): 소비자 decode 목록을 handler 선언으로 만든다. 같은 (메시지 타입, 버전)에 다른 payload class를 선언하면 실패 | 컴파일은 된다. v1이 아닌 메시지는 `SCHEMA_VERSION_NOT_REGISTERED`로 거부. 발행 등록(`MessageContracts`)과 class가 다르면 기동 실패 `MESSAGING_CONTRACT_CONFLICT` | v2 이상을 읽는 handler는 `schemaVersions()`를 override한다. 소비 타입을 `MessageContracts`에 따로 등록하던 코드는 지운다 | `5786126c` · `src/messaging/messaging-core-api/.../delivery/MessageHandler.java`, `messaging-spring-boot-starter/.../MessageContracts.java` |
| B-18 | `MessageHandler.schemaVersions()`(vendored `messaging-core-api`, default `{v1}`): 소비자 decode 목록을 handler 선언으로 만든다. 같은 (메시지 타입, 버전)에 다른 payload class를 선언하면 실패 | 컴파일은 된다. v1이 아닌 메시지는 `SCHEMA_VERSION_NOT_REGISTERED`로 거부. 발행 등록(`MessageContracts`)과 class가 다르면 기동 실패 `MESSAGING_CONTRACT_CONFLICT` | v2 이상을 읽는 handler는 `schemaVersions()`를 override한다. 소비 타입을 `MessageContracts`에 따로 등록하던 코드는 지운다 | `5786126c` · `src/platforms/messaging/messaging-core-api/.../delivery/MessageHandler.java`, `messaging-spring-boot-starter/.../MessageContracts.java` |
| B-19 | `APP_FLYWAY_ENABLED`가 모든 프로필에서 읽힌다. dev·prod 프로필 파일의 `spring.flyway.enabled: true`·`app.persistence.vendor` 고정값을 지우고 persistence-jpa `config/module-defaults`가 `${APP_FLYWAY_ENABLED:true}`를 싣는다 | dev·prod 환경에 `APP_FLYWAY_ENABLED=false`가 있으면 전에는 무시됐지만 이제 기동 때 마이그레이션이 안 돈다 | dev·prod 환경 값을 확인한다. 자기 `application-dev.yml`·`application-prod.yml`에 같은 고정값을 다시 넣지 않는다 | `5786126c` · `src/app-bootstrap/src/main/resources/application-{dev,prod}.yml`, `src/adapter/outbound/persistence-jpa/.../module-defaults/persistence-jpa.yml` |
| B-20 | JDBC batch 기본 켜짐: `APP_JPA_HIBERNATE_BATCH_SIZE` 0→50, `APP_JPA_HIBERNATE_ORDER_INSERTS`·`ORDER_UPDATES` false→true(registry `compatibility_impact: behavior-change`) | 컴파일·기동은 그대로. SQL이 묶여 나가고 insert·update 순서가 바뀐다. IDENTITY 키 엔티티는 batch가 조용히 꺼진다. `.env`에 옛 값(0·false)이 있으면 새 기본값이 안 먹는다 | 문장 순서에 기대는 코드가 있는지 본다. 끄려면 0·false를 명시 | `1400dc15` · `persistence-jpa.yml`, `docs/registries/env-keys.yaml` |
| B-21 | 트랜잭션 제한: `TransactionPort` 쓰기·읽기 트랜잭션 30초(`app.persistence-jpa.transaction.write-timeout`·`read-timeout`, env 키 아님) | 30초를 넘는 트랜잭션은 문장이 취소되고 `DB_QUERY_CANCELED`로 실패 | 긴 일괄 작업은 쪼갠다. 꼭 필요하면 프로필 yml에서 값을 올린다 | `1400dc15` · `persistence-jpa.yml` |
@@ -134,6 +134,7 @@
| B-49 | 샘플 모듈 삭제: `src/sample-portfolio`, `src/Dockerfile.sample`, registry `sample-portfolio` 행, 루트 `build.gradle`의 샘플 태스크·단계(`sampleWebContractCheck`, `:sample-portfolio:*` 의존, strict lane 단계 `:sample-portfolio:check`), `ci-quality-gates.yml`의 `sample-portfolio` job, `SampleRuntimeDefaultsContractTest`, spotbugs 제외의 샘플 클래스. 샘플에만 있던 검사(OpenAPI 스냅숏 `openapiCheckSnapshot`, Date 헤더, 가상 스레드 MDC 전파)도 함께 없어졌다 | 샘플을 고쳐 쓰던 서비스: 병합 때 "수정 대 삭제" 충돌. 샘플을 이미 지운 서비스: 충돌 없음 | 샘플을 이미 지웠으면 할 일 없음. 고쳐 쓰고 있으면 자기 leaf로 옮기고 registry 행·빌드 줄을 자기 것으로 둔다. 위 검사가 필요하면 자기 기능 leaf에 둔다 | `ab5982e9` |
| B-50 | `infra/`에서 15개 삭제. 쓰는 곳이 없던 12개(`infra/httpclient/**`, `infra/jpa/postgres/README.md`, `infra/jpa/toxiproxy/`, `infra/messaging/{kafka,postgres,toxiproxy,tls}/`, `infra/notification/toxiproxy/`)와 운영 인프라 셋(`infra/fileserver/nginx/nginx.conf`, `infra/fileserver/kubernetes/pvc-certification-job.yaml`, `infra/jpa/roles/runtime-roles.sql`). `release.yml`의 `fileserver-pvc-certification` job도 지웠고, fileserver 지원 표에서 "Kubernetes ReadWriteOnce PVC — Limited" 주장을 「주장하지 않음」으로 옮겼다 | 그 파일을 배포에 쓰던 서비스: 병합이 파일을 지운다. 고쳐 쓰던 서비스: "수정 대 삭제" 충돌 | 그 파일은 자기 인프라 repo로 옮긴다. 지켜야 할 조건은 `docs/fileserver/operations.md` 「운영 환경이 지켜야 할 조건」, `docs/fileserver/storage-certification.md`, `docs/jpa/security.md` 「역할과 권한」·「서버 설정」에 있다 | 커밋 「쓰지 않는 파일과 운영 인프라 파일을 지운다」 |
| B-51 | compose 정리. 루트 `docker-compose.yml`·`docker-compose.local.yml`·`docker-compose.infra.yml`을 개발 환경 `compose.yaml` 하나로 합쳤다(app은 `local` 런타임, 뒷단 서비스는 capability profile `jpa`·`redis`·`kafka`·`mongo`·`objectstorage`·`auth`·`mail`). 보조 파일은 `compose/`(keycloak realm·entrypoint, minio init, Redis ACL, mailpit 인증서 폴더). 테스트 lane fixture는 그 lane을 가진 leaf로 옮겼다: `docker-compose.dev.yml`·`docker-compose.prod-smoke.yml`·`docker-compose.tls.yml`·fileserver overlay·smoke 스크립트·스키마 적용 스크립트·lane 계약 JSON(`src/config/runtime/compose-profile-contracts.json`) → `src/app-bootstrap/compose-lanes/`, Redis topology compose → `src/adapter/outbound/redis-sdk/compose/`, NFS compose → `src/adapter/outbound/fileserver/compose/nfs/`. `infra/`는 없어졌다. lane 계약의 `composeProfile`(문자열)은 `composeProfiles`(목록)로 바뀌었고 `appMemoryLimit`이 생겼다. smoke는 lane 중 컨테이너가 재시작하거나 메모리로 죽으면 실패한다. `scripts/bootstrap-local.sh`는 인자를 받지 않는다 | `docker compose -f docker-compose.yml -f docker-compose.local.yml …`을 쓰던 스크립트·문서가 "no such file"로 실패. 옛 compose 파일에 서비스를 더했으면 수정 대 삭제 충돌. lane 계약을 고쳐 쓰던 서비스는 `composeProfile` 키를 smoke 스크립트가 읽지 않는다 | 명령을 `docker compose …`(루트 `compose.yaml`)와 profile로 바꾼다. 더한 서비스는 `compose.yaml`에 capability profile을 달아 옮기고, lane 전용이면 `src/app-bootstrap/compose-lanes/lane-services.yaml`에 둔다. 경로를 적은 workflow·문서를 위 새 경로로 고친다 | 커밋 「compose 파일을 개발 환경 하나와 lane fixture로 나눈다」 |
| B-52 | `src/` 배치 정리. 들여온 플랫폼 넷을 `src/platforms/` 아래로 옮겼다: `src/messaging` → `src/platforms/messaging`, `src/grpc` → `src/platforms/grpc`, `src/grpc-advanced` → `src/platforms/grpc-advanced`, `src/optional-platforms` → `src/platforms/optional-build`(빌드 이름 `optional-platforms`는 그대로). registry `source_path`만 바뀌고 Gradle 경로(`:messaging:*`, `:grpc:*`)는 그대로다. optional 빌드는 `./gradlew -p platforms/optional-build …`로 부른다. `src/config/`에서 기능 하나가 주인인 데이터를 그 leaf의 `release/`로 옮겼다: `config/jpa/*` → `adapter/outbound/persistence-jpa/release/`, `config/messaging/**` → `adapter/outbound/messaging/release/`, `config/mongodb/release-contracts.json` → `adapter/outbound/persistence-mongo/release/` | `-p optional-platforms`를 부르는 workflow·스크립트가 "Project directory … does not exist"로 실패. 옮긴 폴더를 고쳐 쓰던 서비스는 이름 바뀜 충돌(Git이 이동으로 알아보면 자동 병합). `rootProject.file('config/jpa/…')`처럼 옛 경로를 읽던 자기 빌드 줄은 파일 없음 | workflow·스크립트의 `-p`와 경로를 새 위치로 고친다. 자기 leaf를 `src/messaging` 아래에 더했다면 `src/platforms/messaging` 아래로 옮기고 registry `source_path`를 고친다 | 커밋 「들여온 플랫폼을 src/platforms 아래로 묶는다」 |
## 4. DB 마이그레이션
+2 -2
View File
@@ -49,10 +49,10 @@ design-docs `conventions/delegation-loop.md` 3절 순서대로 한다: 크기
| 영역 | 경로 |
| --- | --- |
| core·application | `src/domain-core`, `src/application-*`, `src/shared-contract` |
| inbound 전송 | `src/adapter/inbound/*`, `src/grpc/*`·`src/grpc-advanced/*`(optional 빌드) |
| inbound 전송 | `src/adapter/inbound/*`, `src/platforms/grpc/*`·`src/platforms/grpc-advanced/*`(optional 빌드) |
| persistence | `src/adapter/outbound/persistence-*`, 마이그레이션 |
| outbound capability | 그 밖의 `src/adapter/outbound/*`, 멱등성 store |
| messaging | `src/messaging/*`, `src/adapter/outbound/messaging` |
| messaging | `src/platforms/messaging/*`, `src/adapter/outbound/messaging` |
| bootstrap·build·CI | `src/app-bootstrap`, `src/composition/*`, `src/build-logic`, `src/build.gradle`, `.github/` |
| 보안(영역을 가로질러) | 인증·인가 체인, 비밀, 공개 경로 |
| 문서 | `docs/` |
+1
View File
@@ -74,6 +74,7 @@
| 생성 명령 | JPA adapter를 만들지 않음(서비스 전용 persistence leaf가 기본), 생성된 쓰기 API는 역할 매핑 전 403 | 위임 | `1101` 15절(r2-10) |
| `@SystemInvoked` | bean으로 등록돼 있으면 기동 실패, inbound adapter가 직접 부르지 못하게 ArchUnit | 위임 | `1103` 4절(RR-01-02) |
| 시스템 호출 경로 | 사용자가 닿는 전송(web·GraphQL·gRPC·WebSocket)만 `@SystemInvoked`에 닿지 못한다. 메시지 소비자·스케줄러는 `@SystemCaller(reason)` 표시로 허용 | 위임 | `1103` 9.1절(RR-01-12), 10절 r5-b |
| `src/` 배치 | 들여온 플랫폼 넷(`messaging`, `grpc`, `grpc-advanced`, optional 빌드)을 `src/platforms/` 아래로 묶는다. registry `source_path`만 바꾸고 Gradle 경로는 그대로 둔다. `build-logic`·`gradle`·`config`는 Gradle 루트 표준이라 남기고, `composition`은 조립 계층이라 옮기지 않는다. `config/`에서 기능 하나가 주인인 데이터 파일은 그 leaf로 보낸다. Gradle 루트를 저장소 루트로 옮길지는 CI 재편 때 다시 본다 | 소유자(2026-11-07) | design-docs `repo-structure/README.md` 3.1절, `repo-structure/01-backend-layout.md` 6.1절 |
| 개발 compose 파일 | 저장소 루트에 `compose.yaml` 하나. 뒷단 서비스는 capability 이름 profile로 고르고, 마운트하는 보조 파일은 `compose/`에 둔다. 테스트 lane fixture는 그 lane을 가진 leaf로 보낸다(compose lane → app-bootstrap `compose-lanes/`, Redis topology → redis-sdk, NFS → fileserver). `docker-compose.dev.yml`은 `dev` 배포 프로필이 뜨는지 보는 lane fixture로 app-bootstrap에 둔다 | 소유자(2026-11-07) | design-docs `repo-structure/README.md` 3.1절, `repo-structure/01-backend-layout.md` 6.3절 |
| 인프라 실행 파일 | nginx 설정, Kubernetes PVC job, DB 역할 SQL은 이 repo에서 지우고, 기능이 운영 환경에 요구하는 조건만 그 기능 문서에 적는다. 아무도 쓰지 않는 `infra/` 파일도 지운다 | 소유자(2026-11-07) | design-docs `repo-structure/README.md` 3.1절, `repo-structure/01-backend-layout.md` 6.3절 |
| 샘플 모듈 | `src/sample-portfolio`와 `src/Dockerfile.sample`을 폴더째 지운다. 역할은 옮기지 않는다. 샘플 안에만 있던 템플릿 검사(OpenAPI 스냅숏, Date 헤더, 가상 스레드 MDC)도 함께 지운다. 예시는 매뉴얼과 생성 명령 출력이 맡는다 | 소유자(2026-11-07) | design-docs `repo-structure/README.md` 3.1절, `repo-structure/01-backend-layout.md` 6.2절 |
+1 -1
View File
@@ -121,7 +121,7 @@
| 규칙을 일부러 다르게 둔 타입 | 그 타입의 Javadoc |
| 정적 분석 제외 | 제외 항목 옆 이유(`src/config/spotbugs/exclude-test.xml` 등) |
| 규칙의 예외 경로 | 이유를 요구하는 표시(`@SystemCaller(reason)`) |
| 복사본을 남긴 이유 | 가까운 `CLAUDE.md`(예: `src/messaging/CLAUDE.md`) |
| 복사본을 남긴 이유 | 가까운 `CLAUDE.md`(예: `src/platforms/messaging/CLAUDE.md`) |
| 되돌리기 비싼 선택 | `docs/adr/ADR-<영역>-<번호>-<제목>.md` |
## 패턴을 더하는 법
+8 -8
View File
@@ -20,8 +20,8 @@
| `qualityCheck` | SpotBugs, FindSecBugs(운영 코드) | PR(`ci` 안) | `src/build.gradle` |
| `testQualityCheck` | 같은 분석을 모든 테스트 source set에(`config/spotbugs/exclude-test.xml` 기준) | main(`mainCheck` 안), optional 빌드는 `ci` | `src/build.gradle` |
| `ci` | leaf `check`(API surface 포함) + `architectureCheck` + `qualityCheck` | PR | `ci-quality-gates.yml`: `./gradlew :ci :verifyDependencyLocks --warning-mode=fail` |
| `verifyStrictLaneStages --dry-run` | `explicitOnly`가 아닌 strict lane이 workflow가 실행하는 단계에 속하는가 | PR(두 빌드 각각) | `ci-quality-gates.yml`, optional 빌드는 `-p optional-platforms` |
| `-p optional-platforms ci` | gRPC 플랫폼 빌드 | PR | `ci-quality-gates.yml` |
| `verifyStrictLaneStages --dry-run` | `explicitOnly`가 아닌 strict lane이 workflow가 실행하는 단계에 속하는가 | PR(두 빌드 각각) | `ci-quality-gates.yml`, optional 빌드는 `-p platforms/optional-build` |
| `-p platforms/optional-build ci` | gRPC 플랫폼 빌드 | PR | `ci-quality-gates.yml` |
| `bash scripts/verify-compose-profile-contracts.sh` | compose lane이 선언대로 렌더링되는가(저장소 루트에서) | PR | `ci-quality-gates.yml` |
| `mainCheck` | `configContractCheck` + `qualificationCheck`(`testQualityCheck` 포함) + 공개 경로 스냅숏 + 전송·메시징 qualification lane + 생성 명령 왕복(`verifyFeatureScaffold`) + 모든 leaf의 `mainCheck`(document-contract lane 등) | main | `integration-main.yml`: `./gradlew :mainCheck --continue --warning-mode=fail` |
| `integrationCheck` | 선언된 strict integration lane 전체(실 컨테이너). 입력이 없는 lane은 빼고 이름을 댄다 | main·nightly | `integration-main.yml`, optional 빌드도 |
@@ -98,18 +98,18 @@ cd src
# PR: ci-quality-gates.yml
./gradlew :ci :verifyDependencyLocks --warning-mode=fail --no-build-cache --console=plain
./gradlew :verifyStrictLaneStages --dry-run --console=plain
./gradlew -p optional-platforms ci --no-build-cache --console=plain
./gradlew -p optional-platforms :verifyStrictLaneStages --dry-run --console=plain
./gradlew -p platforms/optional-build ci --no-build-cache --console=plain
./gradlew -p platforms/optional-build :verifyStrictLaneStages --dry-run --console=plain
# main push: integration-main.yml
./gradlew :mainCheck --continue --warning-mode=fail --no-build-cache --console=plain
./gradlew :integrationCheck --continue --no-build-cache --console=plain
./gradlew :performanceCheck --continue --no-build-cache --console=plain
./gradlew -p optional-platforms performanceCheck --continue --no-build-cache --console=plain
./gradlew -p optional-platforms integrationCheck --no-build-cache --console=plain
./gradlew -p platforms/optional-build performanceCheck --continue --no-build-cache --console=plain
./gradlew -p platforms/optional-build integrationCheck --no-build-cache --console=plain
./gradlew :adapter:outbound:httpclient:test -Phttp3.tests.enabled=true --no-build-cache --console=plain # 실험 job, 실패해도 workflow는 통과
# 태그: release.yml (CI는 GITHUB_SHA로 커밋을 받는다. 손으로 돌릴 때는 -PgitRevision)
./gradlew :releaseCheck -PgitRevision="$(git rev-parse HEAD)" --no-build-cache --console=plain
./gradlew -p optional-platforms releaseCheck -PgitRevision="$(git rev-parse HEAD)" --no-build-cache --console=plain
./gradlew -p platforms/optional-build releaseCheck -PgitRevision="$(git rev-parse HEAD)" --no-build-cache --console=plain
cd ..
bash scripts/verify-compose-profile-contracts.sh
bash scripts/run-compose-runtime-smoke.sh --matrix src/app-bootstrap/compose-lanes/compose-profile-contracts.json
@@ -183,7 +183,7 @@ for k in tests skipped failures errors; do cat $(find "$x" -name 'TEST-*.xml') |
| 장치 | 고정하는 것 | 단계 |
| --- | --- | --- |
| 자원 한계 lane | Tomcat·Jetty 부하·느린 클라이언트·종료, HTTP client 풀·스트리밍·재시도, Hikari 풀 | `performanceCheck` |
| JMH 벤치마크 | `src/messaging/messaging-kafka/src/jmh`, `src/messaging/messaging-testkit/src/jmh`, `src/adapter/outbound/httpclient/src/jmh` | 명시 실행 |
| JMH 벤치마크 | `src/platforms/messaging/messaging-kafka/src/jmh`, `src/platforms/messaging/messaging-testkit/src/jmh`, `src/adapter/outbound/httpclient/src/jmh` | 명시 실행 |
## 6. 게이트를 믿을 조건 — 거짓 통과 막기
+2 -2
View File
@@ -84,7 +84,7 @@ echo "=== [actual-topology] provider environments"
#
# The selector names the contract's class. `--tests '*Shard*'` was satisfied by the hermetic
# ShardKeyAnalyzerTest, so "sharded topology" was certified by a unit test that never opened a
# connection. Which classes count is `src/config/mongodb/release-contracts.json`, and
# connection. Which classes count is `src/adapter/outbound/persistence-mongo/release/release-contracts.json`, and
# MongoReleaseEvidenceVerifier checks the JUnit XML rather than the exit code.
if [[ -n "${MONGODB_SHARDED_URI:-}" ]]; then
# Not promoted. `mongoShardedTest` is declared in release-contracts.json under
@@ -94,7 +94,7 @@ if [[ -n "${MONGODB_SHARDED_URI:-}" ]]; then
# a silent skip: an operator who set it expected a qualification to run.
echo "sharded topology is experimental and has no registered lane;" >&2
echo " MONGODB_SHARDED_URI was set but mongoShardedTest does not exist." >&2
echo " See experimental_contracts in src/config/mongodb/release-contracts.json." >&2
echo " See experimental_contracts in src/adapter/outbound/persistence-mongo/release/release-contracts.json." >&2
FAILED+=("actual-topology:sharded-not-promoted")
else
echo "actual-topology(sharded): no MONGODB_SHARDED_URI"
+2 -2
View File
@@ -155,8 +155,8 @@ mkdir -p "${MANIFEST_DIR}"
echo " \"commitDirty\": $( [[ -n "$(git -C "${REPO_ROOT}" status --porcelain)" ]] && echo true || echo false ),"
echo " \"serverImage\": \"${MONGODB_IMAGE:-mongo:8.0.16}\","
echo " \"generatedAt\": \"$(date -u +%Y-%m-%dT%H:%M:%SZ)\","
echo " \"contractManifest\": \"src/config/mongodb/release-contracts.json\","
echo " \"contractManifestSha256\": \"$(sha256sum "${REPO_ROOT}/src/config/mongodb/release-contracts.json" | cut -d' ' -f1)\""
echo " \"contractManifest\": \"src/adapter/outbound/persistence-mongo/release/release-contracts.json\","
echo " \"contractManifestSha256\": \"$(sha256sum "${REPO_ROOT}/src/adapter/outbound/persistence-mongo/release/release-contracts.json" | cut -d' ' -f1)\""
echo "}"
} > "${MANIFEST_DIR}/promotion.json"
echo "promotion manifest: ${MANIFEST_DIR}/promotion.json"
@@ -7,7 +7,7 @@
`messaging:messaging-spring-boot-starter-kafka` (the vendored platform and its Kafka transport) and
ships the module defaults in `config/module-defaults/messaging.yml`.
- Boundaries: add no code here. A publish rule belongs to the bridge (`adapter:outbound:messaging`),
a Kafka rule to the vendored product (`src/messaging/CLAUDE.md`); a class here would be a third
a Kafka rule to the vendored product (`src/platforms/messaging/CLAUDE.md`); a class here would be a third
place. Allowed edges come only from the registry entry.
- Tests: activation tests (`./gradlew :adapter:outbound:messaging-kafka:test`) and the real-Kafka
lane `messagingKafkaRelayIntegrationTest` (relay → bridge → broker record bytes; `:integrationCheck`).
+1 -1
View File
@@ -38,7 +38,7 @@ Package root: `dev.caskeleton.adapter.outbound.messaging`.
may not carry this module. The R1 contract/binding compilers and JSON Schema envelope encoder were
removed on 2026-09-25 (see `docs/capability-status.md`).
- No JSON Schema engine (NetworkNT) on the main classpath. The evidence manifest schema check and the
capability card check (`config/messaging`) are this leaf's tests (`evidence/`); snakeyaml is
capability card check (`release/`) are this leaf's tests (`evidence/`); snakeyaml is
test-only (owner decision 2026-09-25).
- Do not hide use-case sequencing or business routing policy in broker adapters.
- `OutboxMessagePublishAdapter` is delegate-only and emits no dependency log. The confirmed
+3 -3
View File
@@ -19,7 +19,7 @@ dependencies {
// Test-only: MessagingEvidenceSchemaValidatorTest holds the common evidence schema to Draft 2020-12.
testImplementation libs.json.schema.validator
// Test-only (owner decision 29): MessagingCapabilityRegistryContractTest reads the capability
// cards in config/messaging/*.yaml. The rules below keep snakeyaml out of every main
// cards in release/*.yaml. The rules below keep snakeyaml out of every main
// configuration; only the `test*` ones may resolve it.
testImplementation 'org.yaml:snakeyaml'
}
@@ -57,8 +57,8 @@ configurations.configureEach { configuration ->
}
}
// The card check reads the whole config/messaging tree (cards, profiles, the evidence schema).
// The card check reads the whole release tree (cards, profiles, the evidence schema).
tasks.named('test') {
inputs.dir(rootProject.file('config/messaging'))
inputs.dir(file('release'))
.withPathSensitivity(PathSensitivity.RELATIVE)
}
@@ -23,8 +23,9 @@ import tools.jackson.core.type.TypeReference;
import tools.jackson.databind.json.JsonMapper;
/**
* The messaging capability cards under {@code config/messaging} (readiness cards, compatibility and
* release profiles, the common evidence manifest schema) stay closed and fail-safe.
* The messaging capability cards under {@code adapter/outbound/messaging/release} (readiness cards,
* compatibility and release profiles, the common evidence manifest schema) stay closed and
* fail-safe.
*
* <p>Owner decision 29: the card check lives in this leaf's tests, and snakeyaml is on this leaf's
* test classpath only — main stays YAML-free (build.gradle). The files it reads are declared as
@@ -350,7 +351,8 @@ class MessagingCapabilityRegistryContractTest {
}
private static Path requiredConfig(String relativePath) {
Path path = repositorySrcRoot().resolve("config/messaging").resolve(relativePath);
Path path =
repositorySrcRoot().resolve("adapter/outbound/messaging/release").resolve(relativePath);
assertThat(path).as("required Messaging configuration %s", path).isRegularFile();
return path;
}
@@ -11,13 +11,13 @@ import java.util.List;
import org.junit.jupiter.api.Test;
/**
* The common build-evidence manifest schema (config/messaging/evidence) is valid Draft 2020-12 and
* accepts the manifest shape the R2 evidence producers are specified to write.
* The common build-evidence manifest schema (release/evidence) is valid Draft 2020-12 and accepts
* the manifest shape the R2 evidence producers are specified to write.
*/
class MessagingEvidenceSchemaValidatorTest {
private static final Path COMMON_SCHEMA =
Path.of("../../../config/messaging/evidence/build-evidence-manifest-v1.schema.json");
Path.of("release/evidence/build-evidence-manifest-v1.schema.json");
private static final String SHA256 = "sha256:" + "0".repeat(64);
private static final String VALID_MANIFEST =
"""
@@ -60,7 +60,7 @@ in `platform`), so the two capability leaves read the same way.
`jpaPlatformContractTest` lane on `FileserverPostgreSqlStack`, whose clock a case moves.
- The real-PostgreSQL tests are still in `persistence-jpa`'s `postgresqlIntegrationTest` source
set, which owns the container and Flyway wiring, and the JPA readiness card
(`config/jpa/readiness-cards.yaml`, checked by `JpaReadinessRegistryTest`) names them as that
(`persistence-jpa/release/readiness-cards.yaml`, checked by `JpaReadinessRegistryTest`) names them as that
leaf's tasks — moving them means moving the card's tasks and selectors with them:
`postgresqlFileserverMigrationIntegrationTest`, `postgresqlFileserverMetadataIntegrationTest`,
`postgresqlFileserverReclamationIntegrationTest`
@@ -46,6 +46,6 @@ apiSurface {
adopterBaseline = rootProject.file('../docs/architecture/persistence-fileserver-adopter-api-surface.txt')
adopterSources = fileTree(rootProject.projectDir) {
include '*/**/src/main/java/**/*.java'
exclude '**/build/**', 'adapter/outbound/persistence-fileserver/**', 'build-logic/**', 'optional-platforms/**'
exclude '**/build/**', 'adapter/outbound/persistence-fileserver/**', 'build-logic/**', 'platforms/optional-build/**'
}
}
@@ -389,7 +389,7 @@ cadence 측정 필요). retention 한 값은 reaper-local 이라 `@Value` 로
## JPA production capability candidate
`src/config/jpa/readiness-cards.yaml`이 capability와 독립 schema stream의
`src/adapter/outbound/persistence-jpa/release/readiness-cards.yaml`이 capability와 독립 schema stream의
machine-readable SSOT다(개수는 registry가 소유한다). `selected` base card와 `implemented-candidate` reliability card를
구분하며, 실제 PostgreSQL 테스트 통과만으로 immutable 운영 evidence가 필요한 R2를 주장하지
않는다.
@@ -117,7 +117,7 @@ dependencies {
postgresqlIntegrationTestImplementation testFixtures(project(':application-fileserver'))
// The notification capability's persistence moved out the same way, and its real-PostgreSQL
// qualifications stay here for the same reason: this lane owns the container, the Flyway wiring
// and the readiness cards that name those tests (config/jpa/readiness-cards.yaml). Test scope
// and the readiness cards that name those tests (release/readiness-cards.yaml). Test scope
// only.
postgresqlIntegrationTestImplementation project(':adapter:outbound:persistence-notification')
postgresqlIntegrationTestImplementation project(':application-notification')
@@ -171,7 +171,7 @@ dependencies {
// Real-PostgreSQL lanes. A readiness lane runs one named class (the security lane also names the
// runtime-role namespace-denial method), a platform lane selects a tag, and the pool lane has a
// source set of its own. release.yml (jpa-release-gate) and config/jpa/*.{json,yaml} name these tasks.
// source set of its own. release.yml (jpa-release-gate) and release/*.{json,yaml} name these tasks.
def jpaEvidenceImage = providers.gradleProperty('jpaPostgreSqlEvidenceImage').orElse(testContainerImages['postgres-16']).get()
def jpaMatrixVersions = providers.gradleProperty('jpa.matrix.versions').orElse('16').get()
def readinessLanes = [
@@ -205,12 +205,12 @@ def platformLanes = [
jpaPlatformQueryPlanTest: ['jpa-queryplan', 'Asserts query plan structure and planner estimate error (design §33).'],
jpaPlatformSecurityTest : ['jpa-security', 'Verifies runtime role privileges and search_path safety (design §36).'],
]
// Every scenario a readiness card cites (config/jpa/readiness-cards.yaml `evidence.scenarios`) is a
// Every scenario a readiness card cites (release/readiness-cards.yaml `evidence.scenarios`) is a
// required test of the lane that runs its class, and a readiness lane rejects skips. That is what the
// deleted JPA evidence manifest used to establish from JUnit XML after the fact; JpaReadinessRegistryTest
// checks the cards themselves.
def readinessScenarios = new groovy.json.JsonSlurper()
.parse(rootProject.file('config/jpa/readiness-cards.yaml'))
.parse(file('release/readiness-cards.yaml'))
.cards.values()
.findAll { it.state != 'not-implemented' }
.collectMany { card -> (card.evidence?.scenarios ?: []).collect { it.selector } }
@@ -287,7 +287,7 @@ tasks.named('postgresqlSecurityBaselineIntegrationTest') {
dependsOn ':adapter:inbound:web:jpaPersistenceRedactionContractTest'
}
// Which JPA lanes block a release is declared by config/jpa/release-registry.json (jpaReleaseQualification below).
// Which JPA lanes block a release is declared by release/release-registry.json (jpaReleaseQualification below).
// This leaf declares the lanes and how each runs; it does not own release orchestration.
// The unit lane reads three files that are not Java sources: the release registry and its two
@@ -298,9 +298,9 @@ tasks.named('postgresqlSecurityBaselineIntegrationTest') {
// up-to-date after a registry demotion or a workflow edit — so the drift checks that exist to catch
// exactly those edits never run on them.
tasks.named('test') {
inputs.file(rootProject.file('config/jpa/release-registry.json'))
inputs.file(file('release/release-registry.json'))
// JpaReadinessRegistryTest: the readiness cards, the lanes they name and the scenarios they cite.
inputs.file(rootProject.file('config/jpa/readiness-cards.yaml'))
inputs.file(file('release/readiness-cards.yaml'))
inputs.dir(file('src/postgresqlIntegrationTest/java')).withPropertyName('readinessScenarioSources')
inputs.file(new File(rootProject.projectDir.parentFile, 'docs/jpa/support-matrix.md'))
inputs.file(new File(rootProject.projectDir.parentFile, 'docs/jpa/repository-adaptation.md'))
@@ -316,7 +316,7 @@ tasks.named('test') {
inputs.dir(file('../persistence-fileserver/src/main/resources/db/migration'))
.withPropertyName('fileserverMigrations')
// ...and the messaging platform's tree, whose inbox range the consume side applies here.
inputs.dir(file('../../../messaging/messaging-reliability-jdbc-postgresql/src/main/resources/db/migration'))
inputs.dir(file('../../../platforms/messaging/messaging-reliability-jdbc-postgresql/src/main/resources/db/migration'))
.withPropertyName('messagingMigrations')
}
@@ -351,20 +351,20 @@ apiSurface {
include '*/**/src/main/java/**/*.java'
exclude '**/build/**', 'adapter/outbound/persistence-jpa/**', 'adapter/outbound/persistence-fileserver/**',
'adapter/outbound/persistence-notification/**',
'build-logic/**', 'optional-platforms/**'
'build-logic/**', 'platforms/optional-build/**'
}
}
// The release registry (config/jpa/release-registry.json) names the blocking release gates; this
// The release registry (release/release-registry.json) names the blocking release gates; this
// aggregate runs exactly those. It replaced the build-tools `ca.jpa-qualification` plugin (review
// 2026-09-24 BUILD-O3-2): a gate that names a task that does not exist fails when the task graph is
// built, which is the whole of what `verifyJpaReleaseGateTasks` used to check.
tasks.register('jpaReleaseQualification') {
group = 'verification'
description = 'Runs exactly the blocking JPA release gates declared by config/jpa/release-registry.json.'
description = 'Runs exactly the blocking JPA release gates declared by release/release-registry.json.'
dependsOn(new groovy.json.JsonSlurper()
.parse(rootProject.file('config/jpa/release-registry.json'))
.parse(file('release/release-registry.json'))
.gates.findAll { it.blocking }.collect { it.task })
}
@@ -40,7 +40,7 @@ final class MigrationTrees {
Path.of("../persistence-notification/src/main/resources/db/migration"),
Path.of("../persistence-fileserver/src/main/resources/db/migration"),
Path.of(
"../../../messaging/messaging-reliability-jdbc-postgresql/src/main/resources/db/migration"));
"../../../platforms/messaging/messaging-reliability-jdbc-postgresql/src/main/resources/db/migration"));
private MigrationTrees() {}
@@ -20,7 +20,8 @@ import tools.jackson.databind.JsonNode;
import tools.jackson.databind.json.JsonMapper;
/**
* The JPA readiness cards ({@code src/config/jpa/readiness-cards.yaml}) against the lanes and tests
* The JPA readiness cards ({@code
* src/adapter/outbound/persistence-jpa/release/readiness-cards.yaml}) against the lanes and tests
* they name.
*
* <p>This replaced the build-tools {@code ca.jpa-qualification}/{@code ca.jpa-evidence} plugins
@@ -33,8 +34,8 @@ import tools.jackson.databind.json.JsonMapper;
class JpaReadinessRegistryTest {
private static final Path SOURCE_ROOT = Path.of("../../..").toAbsolutePath().normalize();
private static final Path REGISTRY = SOURCE_ROOT.resolve("config/jpa/readiness-cards.yaml");
private static final Path LEAF = SOURCE_ROOT.resolve("adapter/outbound/persistence-jpa");
private static final Path REGISTRY = LEAF.resolve("release/readiness-cards.yaml");
private static final String LEAF_PATH = ":adapter:outbound:persistence-jpa:";
private static final Set<String> STATES =
Set.of("selected", "implemented-candidate", "not-implemented");
@@ -43,7 +43,8 @@ public record JpaReleaseManifest(
String providerBaseline) {
/** Where the registry lives, relative to the repository's {@code src} directory. */
public static final String REGISTRY_PATH = "config/jpa/release-registry.json";
public static final String REGISTRY_PATH =
"adapter/outbound/persistence-jpa/release/release-registry.json";
/**
* The registry, located by walking up from the working directory.
@@ -109,7 +109,7 @@ The architecture rule catalogue (`…mongo.architecture`) is in the **testkit**
production: it is ArchUnit input, and shipping it put rule text on every consumer's runtime
classpath. Release gating is testkit-only for the same reason and is one implementation, not two:
`…mongo.testkit.release` reads the JUnit XML a lane wrote and is what
`scripts/verify-mongodb-platform.sh` and `src/config/mongodb/release-contracts.json` drive. A second
`scripts/verify-mongodb-platform.sh` and `src/adapter/outbound/persistence-mongo/release/release-contracts.json` drive. A second
pair on the production classpath — a hand-built set of category names and a gate that checked it —
had no caller outside its own test and no source of truth behind the categories; it is gone rather
than moved.
@@ -257,7 +257,7 @@ tasks.named('check') {
strictTestLanes {
lane('mongoDocumentContractTest') {
tag = 'document-contract'
description = 'Holds the Mongo lane tags to config/mongodb/release-contracts.json.'
description = 'Holds the Mongo lane tags to release/release-contracts.json.'
rejectSkipped = true
mainStage()
}
@@ -30,8 +30,7 @@ import tools.jackson.databind.json.JsonMapper;
class MongoTestLaneContractTest {
private static final Path INTEGRATION_SOURCES = Path.of("src/mongoIntegrationTest/java");
private static final Path RELEASE_CONTRACTS =
Path.of("../../../config/mongodb/release-contracts.json");
private static final Path RELEASE_CONTRACTS = Path.of("release/release-contracts.json");
private static final Set<String> DOCKER_LANE_TAGS =
Set.of(
"mongodb-replicaset",
+2 -2
View File
@@ -473,12 +473,12 @@ app-bootstrap 은 합성 루트라 "왜 이 의존성이, 왜 이 scope 로" 결
- **`spring-security-test`** — `@WithMockUser`로 actuator 보안 인가(permit-all 프로브 / 인증 필요한
링크 / 노출 안 한 loggers)를 검증한다.
- **`snakeyaml`** — `docs/registries/*.yaml` 같은 checked-in YAML 레지스트리를 contract 테스트가
읽는다. `config/messaging/*.yaml` 카드 검증(`MessagingCapabilityRegistryContractTest`)은 소유자
읽는다. `adapter/outbound/messaging/release/*.yaml` 카드 검증(`MessagingCapabilityRegistryContractTest`)은 소유자
결정 29로 `adapter:outbound:messaging` 테스트로 옮겼다.
### Messaging qualification scaffold
`config/messaging/`은 first polling-producer tuple의 machine-readable 계획 truth만 보관한다.
`adapter/outbound/messaging/release/`는 first polling-producer tuple의 machine-readable 계획 truth만 보관한다.
현재 card 11개는 모두 `maturity: not-implemented`, `evidenceFingerprint: ""`이고 consumer,
CDC, EOS, schema-registry 확장 row는 없다. `verifyMessagingContracts`는 application-core·
shared-contract의 exact qualification test를 실행하고 `contracts-schema/manifest.json`을 쓴 뒤 그
+3 -1
View File
@@ -183,7 +183,7 @@ dependencies {
capabilityProjects.each { architectureTestRuntimeOnly project(it) }
// What this import does NOT see: the optional-platforms build (`grpc:*`, `grpc-advanced:*`).
// It is a separate Gradle build, so its classes cannot be on this classpath; its registered
// leaves are held by the Gradle direction gate (`-p optional-platforms ci` runs
// leaves are held by the Gradle direction gate (`-p platforms/optional-build ci` runs
// verifyCleanArchitectureDependencies), which is the whole of what the owner decided it needs.
// The capability integration lane selects Fileserver and object storage together, as a service
@@ -349,6 +349,8 @@ def repositoryContractInputs = files(
include 'config/**', '**/*.gradle', 'gradle/*.toml', 'Dockerfile*', '.env*', '**/src/main/**'
// The compose lane fixtures this leaf owns (the lane contract, overlays, smoke clients).
include 'app-bootstrap/compose-lanes/**'
// The release data a capability leaf owns (readiness cards, release registries).
include 'adapter/outbound/*/release/**'
exclude '**/*.md'
exclude repositoryContractExcludes
})
@@ -371,19 +371,19 @@ class DeveloperExperienceContractTest {
// and the dependency verifier, and none of those runs a lane whose category is INTEGRATION.
// A lane nobody runs is not coverage, so both halves are pinned here — the aggregate that
// covers the category, and the workflow that executes the aggregate.
assertThat(read("src/optional-platforms/build.gradle"))
assertThat(read("src/platforms/optional-build/build.gradle"))
.as("the optional platform build must aggregate its integration-category lanes")
.contains("tasks.register('integrationCheck')")
.contains(":integrationTestLaneCheck");
assertThat(read("src/grpc/grpc-operation-ledger-jpa/build.gradle"))
assertThat(read("src/platforms/grpc/grpc-operation-ledger-jpa/build.gradle"))
.as("the operation ledger lane this contract protects must still be declared")
.contains("lane('integrationTest')")
.contains("integration()");
assertThat(read(".github/workflows/integration-main.yml"))
.as("a workflow must actually execute the optional platform integration aggregate")
.contains("./gradlew -p optional-platforms integrationCheck");
.contains("./gradlew -p platforms/optional-build integrationCheck");
}
@Test
@@ -51,7 +51,7 @@ class MessagingAuthorityContractTest {
Pattern.compile("String PREFIX\\s*=\\s*\"app\\.messaging\"");
private static final List<ProductionSource> MESSAGING_SOURCES =
loadSources("adapter/outbound/messaging", "messaging", "app-bootstrap");
loadSources("adapter/outbound/messaging", "platforms/messaging", "app-bootstrap");
private static final List<ProductionSource> CORE_SOURCES =
loadSources("application-core", "domain-core");
@@ -34,8 +34,8 @@ import org.junit.jupiter.api.Test;
*
* <p>So the rule is one-directional and mechanical: a vendor library named in a public or protected
* signature is declared {@code api}; one used only behind private members stays {@code
* implementation}. {@code src/messaging/CLAUDE.md} states it as policy — this holds it to the
* source so the two cannot drift.
* implementation}. {@code src/platforms/messaging/CLAUDE.md} states it as policy — this holds it to
* the source so the two cannot drift.
*
* <p>The libraries checked are the ones an adopter would otherwise have to reverse-engineer into
* their own build: broker clients, codec libraries, the metrics registry, the reactive facade.
@@ -345,7 +345,7 @@ class MessagingPublicSurfaceContractTest {
}
private static List<Path> messagingLeaves() {
Path family = repositoryRoot().resolve("src/messaging");
Path family = repositoryRoot().resolve("src/platforms/messaging");
try (Stream<Path> children = Files.list(family)) {
return children
.filter(Files::isDirectory)
@@ -66,7 +66,8 @@ class ReleaseManifestTaskExistenceTest {
// Only the blocking set. experimental_contracts is explicitly not promoted and is never
// aggregated into a release manifest, so a task it names is allowed not to exist yet.
List<String> named =
blockingTaskNamesIn(root.resolve("src/config/mongodb/release-contracts.json"));
blockingTaskNamesIn(
root.resolve("src/adapter/outbound/persistence-mongo/release/release-contracts.json"));
List<String> registered =
registeredTaskNamesIn(root.resolve("src/adapter/outbound/persistence-mongo/build.gradle"));
@@ -0,0 +1,78 @@
package dev.caskeleton.buildlogic;
import java.io.File;
import java.io.IOException;
import java.io.UncheckedIOException;
import org.gradle.api.GradleException;
/**
* Where the main build is, seen from any build of this repository.
*
* <p>The main build is the Gradle root that owns the module registry ({@code
* config/architecture/modules.json}); the repository root is its parent. The optional platform build
* lives inside it ({@code src/platforms/optional-build}), and the code that needs the registry, the
* shared tool configuration or the test image catalog used to reach the main build by taking one
* parent of the optional build's root. That held only while the optional build sat directly under
* the main build; it is found by walking up instead, so the optional build's depth is not a fact
* every caller repeats.
*/
public final class MainBuild {
/** The registry, relative to the main build: what makes a directory the main build. */
public static final String REGISTRY = "config/architecture/modules.json";
private MainBuild() {}
/**
* The main build's directory: {@code buildRoot} itself or the nearest directory above it that
* holds the module registry.
*
* @param buildRoot the root directory of the build asking (its settings or root project directory)
* @return the canonical main build directory
*/
public static File directory(File buildRoot) {
File registry = nearest(buildRoot, REGISTRY);
if (registry == null) {
throw new GradleException(
"No " + REGISTRY + " at or above " + buildRoot + "; this build is not inside the repository");
}
return registry.getParentFile().getParentFile().getParentFile();
}
/**
* The nearest {@code relativePath} at or above {@code buildRoot}: in the build's own root first,
* then in each parent. A file or a directory; {@code null} when no ancestor has it.
*
* @param buildRoot the root directory of the build asking
* @param relativePath the path to look for, relative to each candidate directory
* @return the canonical path found, or {@code null}
*/
public static File nearest(File buildRoot, String relativePath) {
for (File directory = canonical(buildRoot);
directory != null;
directory = directory.getParentFile()) {
File candidate = new File(directory, relativePath);
if (candidate.exists()) {
return candidate;
}
}
return null;
}
/**
* The repository root: the main build's parent.
*
* @param buildRoot the root directory of the build asking
* @return the canonical repository root
*/
public static File repositoryRoot(File buildRoot) {
return directory(buildRoot).getParentFile();
}
private static File canonical(File file) {
try {
return file.getCanonicalFile();
} catch (IOException exception) {
throw new UncheckedIOException("cannot resolve " + file, exception);
}
}
}
@@ -1,9 +1,8 @@
package dev.caskeleton.buildlogic.architecture;
import dev.caskeleton.buildlogic.MainBuild;
import dev.caskeleton.buildlogic.ModuleRegistry;
import java.io.File;
import java.io.IOException;
import java.io.UncheckedIOException;
import java.nio.file.Path;
import java.util.ArrayList;
import java.util.HashSet;
@@ -33,15 +32,9 @@ public final class ArchitecturePlugin implements Plugin<Project> {
Project root = project.getRootProject();
boolean optionalGrpcBuild = root.getName().equals("optional-platforms");
String buildName = optionalGrpcBuild ? "optional-grpc" : "main";
File mainBuildDirectory =
optionalGrpcBuild ? root.getProjectDir().getParentFile() : root.getProjectDir();
File registryFile = new File(mainBuildDirectory, "config/architecture/modules.json");
File repositoryRoot;
try {
repositoryRoot = mainBuildDirectory.getParentFile().getCanonicalFile();
} catch (IOException exception) {
throw new UncheckedIOException("failed to resolve repository root", exception);
}
File mainBuildDirectory = MainBuild.directory(root.getProjectDir());
File registryFile = new File(mainBuildDirectory, MainBuild.REGISTRY);
File repositoryRoot = mainBuildDirectory.getParentFile();
ModuleRegistry registry = ModuleRegistry.read(registryFile, repositoryRoot);
List<ModuleRegistry.Module> modules = registry.modulesForBuild(buildName);
List<String> registryViolations = registryViolations(registry, modules);
@@ -1,5 +1,6 @@
package dev.caskeleton.buildlogic.java;
import dev.caskeleton.buildlogic.MainBuild;
import io.spring.gradle.dependencymanagement.dsl.DependencyManagementExtension;
import java.io.File;
import java.io.IOException;
@@ -282,11 +283,12 @@ public final class JavaConventionsPlugin implements Plugin<Project> {
public static final String CONTAINER_IMAGE_PROPERTY_PREFIX = "ca.test.image.";
private static File containerImageCatalog(Project project) {
// The optional platform build's root is a directory inside the main build, which owns the
// catalog.
File root = project.getRootProject().getProjectDir();
File catalog = new File(root, "config/testing/container-images.properties");
if (!catalog.isFile()) {
// The optional-platforms build's root is a directory inside the main build.
catalog = new File(root.getParentFile(), "config/testing/container-images.properties");
File catalog = MainBuild.nearest(root, "config/testing/container-images.properties");
if (catalog == null) {
catalog = new File(root, "config/testing/container-images.properties");
}
if (!catalog.isFile()) {
throw new GradleException("Missing test container image catalog: " + catalog);
@@ -5,6 +5,7 @@ import com.github.spotbugs.snom.Confidence;
import com.github.spotbugs.snom.SpotBugsExtension;
import com.github.spotbugs.snom.SpotBugsReport;
import com.github.spotbugs.snom.SpotBugsTask;
import dev.caskeleton.buildlogic.MainBuild;
import java.io.File;
import java.util.List;
import net.ltgt.gradle.errorprone.ErrorProneOptions;
@@ -36,11 +37,14 @@ public final class QualityConventionsPlugin implements Plugin<Project> {
SourceSet main = javaExtension.getSourceSets().getByName(SourceSet.MAIN_SOURCE_SET_NAME);
SourceSet test = javaExtension.getSourceSets().getByName(SourceSet.TEST_SOURCE_SET_NAME);
File repositoryConfigDirectory = project.getRootProject().file("config");
if (!repositoryConfigDirectory.isDirectory()) {
repositoryConfigDirectory =
new File(project.getRootProject().getProjectDir().getParentFile(), "config");
}
// The optional platform build's root is a directory inside the main build, which owns the tool
// configuration.
File repositoryConfigDirectory =
MainBuild.nearest(project.getRootProject().getProjectDir(), "config/checkstyle");
repositoryConfigDirectory =
repositoryConfigDirectory == null
? project.getRootProject().file("config")
: repositoryConfigDirectory.getParentFile();
SpotlessExtension spotless = project.getExtensions().getByType(SpotlessExtension.class);
spotless.java(
@@ -1,23 +1,17 @@
package dev.caskeleton.buildlogic.settings;
import dev.caskeleton.buildlogic.MainBuild;
import dev.caskeleton.buildlogic.ModuleRegistrySettingsInstaller;
import java.io.File;
import java.io.IOException;
import java.io.UncheckedIOException;
import org.gradle.api.Plugin;
import org.gradle.api.initialization.Settings;
public final class OptionalArchitectureRegistrySettingsPlugin implements Plugin<Settings> {
@Override
public void apply(Settings settings) {
try {
File mainBuildDirectory = settings.getSettingsDir().getParentFile().getCanonicalFile();
File repositoryRoot = mainBuildDirectory.getParentFile().getCanonicalFile();
File registryFile = new File(mainBuildDirectory, "config/architecture/modules.json");
ModuleRegistrySettingsInstaller.install(
settings, registryFile, repositoryRoot, "optional-grpc");
} catch (IOException exception) {
throw new UncheckedIOException("failed to resolve optional architecture registry paths", exception);
}
File mainBuildDirectory = MainBuild.directory(settings.getSettingsDir());
File registryFile = new File(mainBuildDirectory, MainBuild.REGISTRY);
ModuleRegistrySettingsInstaller.install(
settings, registryFile, mainBuildDirectory.getParentFile(), "optional-grpc");
}
}
@@ -18,7 +18,7 @@ public abstract class StrictLaneStagesExtension {
* command executes this build's stages only when it starts in this build's directory from there
* — its step's {@code working-directory} joined with its {@code -p}. The directory is read from
* where the build is, so no build states it (review 2026-11-04 RR2-04-04: a {@code -p} value
* alone missed {@code working-directory: src/optional-platforms} with {@code ../gradlew}).
* alone missed {@code working-directory: src/platforms/optional-build} with {@code ../gradlew}).
*/
public abstract DirectoryProperty getWorkflowDirectory();
@@ -298,7 +298,7 @@ public final class StrictLaneStagesPlugin implements Plugin<Project> {
/**
* This build's directory from the repository root, which holds {@code .github/workflows}: {@code
* src} for the main build, {@code src/optional-platforms} for the optional one.
* src} for the main build, {@code src/platforms/optional-build} for the optional one.
*/
private static String buildDirectory(Project root, File workflowDirectory) {
File repository = workflowDirectory.getAbsoluteFile().getParentFile().getParentFile();
+28 -28
View File
@@ -386,13 +386,13 @@
{
"id": "messaging-core-api",
"gradle_path": ":messaging:messaging-core-api",
"source_path": "src/messaging/messaging-core-api",
"source_path": "src/platforms/messaging/messaging-core-api",
"allowed_dependencies": []
},
{
"id": "messaging-schema-json",
"gradle_path": ":messaging:messaging-schema-json",
"source_path": "src/messaging/messaging-schema-json",
"source_path": "src/platforms/messaging/messaging-schema-json",
"allowed_dependencies": [
"messaging-core-api"
]
@@ -400,7 +400,7 @@
{
"id": "messaging-schema-avro",
"gradle_path": ":messaging:messaging-schema-avro",
"source_path": "src/messaging/messaging-schema-avro",
"source_path": "src/platforms/messaging/messaging-schema-avro",
"allowed_dependencies": [
"messaging-core-api"
]
@@ -408,7 +408,7 @@
{
"id": "messaging-schema-protobuf",
"gradle_path": ":messaging:messaging-schema-protobuf",
"source_path": "src/messaging/messaging-schema-protobuf",
"source_path": "src/platforms/messaging/messaging-schema-protobuf",
"allowed_dependencies": [
"messaging-core-api"
]
@@ -416,7 +416,7 @@
{
"id": "messaging-cloudevents",
"gradle_path": ":messaging:messaging-cloudevents",
"source_path": "src/messaging/messaging-cloudevents",
"source_path": "src/platforms/messaging/messaging-cloudevents",
"allowed_dependencies": [
"messaging-core-api"
]
@@ -424,7 +424,7 @@
{
"id": "messaging-policy",
"gradle_path": ":messaging:messaging-policy",
"source_path": "src/messaging/messaging-policy",
"source_path": "src/platforms/messaging/messaging-policy",
"allowed_dependencies": [
"messaging-core-api"
]
@@ -432,7 +432,7 @@
{
"id": "messaging-transport-spi",
"gradle_path": ":messaging:messaging-transport-spi",
"source_path": "src/messaging/messaging-transport-spi",
"source_path": "src/platforms/messaging/messaging-transport-spi",
"allowed_dependencies": [
"messaging-core-api",
"messaging-policy"
@@ -441,7 +441,7 @@
{
"id": "messaging-runtime-core",
"gradle_path": ":messaging:messaging-runtime-core",
"source_path": "src/messaging/messaging-runtime-core",
"source_path": "src/platforms/messaging/messaging-runtime-core",
"allowed_dependencies": [
"messaging-core-api",
"messaging-policy",
@@ -453,7 +453,7 @@
{
"id": "messaging-observability",
"gradle_path": ":messaging:messaging-observability",
"source_path": "src/messaging/messaging-observability",
"source_path": "src/platforms/messaging/messaging-observability",
"allowed_dependencies": [
"messaging-core-api"
]
@@ -461,7 +461,7 @@
{
"id": "messaging-security",
"gradle_path": ":messaging:messaging-security",
"source_path": "src/messaging/messaging-security",
"source_path": "src/platforms/messaging/messaging-security",
"allowed_dependencies": [
"messaging-core-api"
]
@@ -469,7 +469,7 @@
{
"id": "messaging-kafka",
"gradle_path": ":messaging:messaging-kafka",
"source_path": "src/messaging/messaging-kafka",
"source_path": "src/platforms/messaging/messaging-kafka",
"allowed_dependencies": [
"messaging-core-api",
"messaging-policy",
@@ -482,7 +482,7 @@
{
"id": "messaging-reliability-api",
"gradle_path": ":messaging:messaging-reliability-api",
"source_path": "src/messaging/messaging-reliability-api",
"source_path": "src/platforms/messaging/messaging-reliability-api",
"allowed_dependencies": [
"messaging-core-api"
]
@@ -490,7 +490,7 @@
{
"id": "messaging-reliability",
"gradle_path": ":messaging:messaging-reliability",
"source_path": "src/messaging/messaging-reliability",
"source_path": "src/platforms/messaging/messaging-reliability",
"allowed_dependencies": [
"messaging-core-api",
"messaging-reliability-api"
@@ -499,7 +499,7 @@
{
"id": "messaging-reliability-jdbc-postgresql",
"gradle_path": ":messaging:messaging-reliability-jdbc-postgresql",
"source_path": "src/messaging/messaging-reliability-jdbc-postgresql",
"source_path": "src/platforms/messaging/messaging-reliability-jdbc-postgresql",
"allowed_dependencies": [
"messaging-core-api",
"messaging-reliability-api",
@@ -510,7 +510,7 @@
{
"id": "messaging-claim-check",
"gradle_path": ":messaging:messaging-claim-check",
"source_path": "src/messaging/messaging-claim-check",
"source_path": "src/platforms/messaging/messaging-claim-check",
"allowed_dependencies": [
"messaging-core-api",
"messaging-reliability-api"
@@ -519,7 +519,7 @@
{
"id": "messaging-admin",
"gradle_path": ":messaging:messaging-admin",
"source_path": "src/messaging/messaging-admin",
"source_path": "src/platforms/messaging/messaging-admin",
"allowed_dependencies": [
"messaging-core-api",
"messaging-observability"
@@ -528,7 +528,7 @@
{
"id": "messaging-spring-boot-starter",
"gradle_path": ":messaging:messaging-spring-boot-starter",
"source_path": "src/messaging/messaging-spring-boot-starter",
"source_path": "src/platforms/messaging/messaging-spring-boot-starter",
"allowed_dependencies": [
"messaging-admin",
"messaging-core-api",
@@ -546,7 +546,7 @@
{
"id": "messaging-spring-boot-starter-kafka",
"gradle_path": ":messaging:messaging-spring-boot-starter-kafka",
"source_path": "src/messaging/messaging-spring-boot-starter-kafka",
"source_path": "src/platforms/messaging/messaging-spring-boot-starter-kafka",
"allowed_dependencies": [
"messaging-spring-boot-starter",
"messaging-kafka",
@@ -562,7 +562,7 @@
{
"id": "messaging-testkit",
"gradle_path": ":messaging:messaging-testkit",
"source_path": "src/messaging/messaging-testkit",
"source_path": "src/platforms/messaging/messaging-testkit",
"allowed_dependencies": [
"messaging-core-api",
"messaging-policy",
@@ -572,21 +572,21 @@
{
"id": "grpc-contract",
"gradle_path": ":grpc:grpc-contract",
"source_path": "src/grpc/grpc-contract",
"source_path": "src/platforms/grpc/grpc-contract",
"allowed_dependencies": [],
"build": "optional-grpc"
},
{
"id": "grpc-core-api",
"gradle_path": ":grpc:grpc-core-api",
"source_path": "src/grpc/grpc-core-api",
"source_path": "src/platforms/grpc/grpc-core-api",
"allowed_dependencies": [],
"build": "optional-grpc"
},
{
"id": "grpc-observability",
"gradle_path": ":grpc:grpc-observability",
"source_path": "src/grpc/grpc-observability",
"source_path": "src/platforms/grpc/grpc-observability",
"allowed_dependencies": [
"grpc-core-api"
],
@@ -595,7 +595,7 @@
{
"id": "grpc-operation-ledger-jpa",
"gradle_path": ":grpc:grpc-operation-ledger-jpa",
"source_path": "src/grpc/grpc-operation-ledger-jpa",
"source_path": "src/platforms/grpc/grpc-operation-ledger-jpa",
"allowed_dependencies": [
"grpc-core-api"
],
@@ -604,7 +604,7 @@
{
"id": "grpc-runtime",
"gradle_path": ":grpc:grpc-runtime",
"source_path": "src/grpc/grpc-runtime",
"source_path": "src/platforms/grpc/grpc-runtime",
"allowed_dependencies": [
"grpc-core-api"
],
@@ -613,7 +613,7 @@
{
"id": "grpc-spring-boot-starter",
"gradle_path": ":grpc:grpc-spring-boot-starter",
"source_path": "src/grpc/grpc-spring-boot-starter",
"source_path": "src/platforms/grpc/grpc-spring-boot-starter",
"allowed_dependencies": [
"grpc-core-api",
"grpc-runtime",
@@ -624,7 +624,7 @@
{
"id": "grpc-testkit",
"gradle_path": ":grpc:grpc-testkit",
"source_path": "src/grpc/grpc-testkit",
"source_path": "src/platforms/grpc/grpc-testkit",
"allowed_dependencies": [
"grpc-core-api",
"grpc-runtime",
@@ -636,7 +636,7 @@
{
"id": "grpc-advanced",
"gradle_path": ":grpc-advanced:grpc-advanced",
"source_path": "src/grpc-advanced/grpc-advanced",
"source_path": "src/platforms/grpc-advanced/grpc-advanced",
"allowed_dependencies": [
"grpc-core-api",
"grpc-runtime"
@@ -646,7 +646,7 @@
{
"id": "grpc-advanced-compat",
"gradle_path": ":grpc-advanced:grpc-advanced-compat",
"source_path": "src/grpc-advanced/grpc-advanced-compat",
"source_path": "src/platforms/grpc-advanced/grpc-advanced-compat",
"allowed_dependencies": [
"grpc-core-api",
"grpc-runtime"

Some files were not shown because too many files have changed in this diff Show More