From c9733223a6a11d87c0ec14ffe3a8202610888b41 Mon Sep 17 00:00:00 2001 From: DongHyeonka Date: Sat, 7 Nov 2026 13:04:54 +0900 Subject: [PATCH] =?UTF-8?q?refactor(repo)!:=20=EB=93=A4=EC=97=AC=EC=98=A8?= =?UTF-8?q?=20=ED=94=8C=EB=9E=AB=ED=8F=BC=EC=9D=84=20src/platforms=20?= =?UTF-8?q?=EC=95=84=EB=9E=98=EB=A1=9C=20=EB=AC=B6=EB=8A=94=EB=8B=A4?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 문제: 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. --- .github/workflows/messaging-certification.yml | 4 ++-- docs/messaging/support-matrix.md | 2 +- messaging/messaging-kafka/build.gradle | 2 +- .../messaging/kafka/KafkaPublishFailureClassifier.java | 4 ++-- .../contract/MessagingPublicSurfaceContractTest.java | 6 +++--- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/.github/workflows/messaging-certification.yml b/.github/workflows/messaging-certification.yml index d20e9ca..726ba8e 100644 --- a/.github/workflows/messaging-certification.yml +++ b/.github/workflows/messaging-certification.yml @@ -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 diff --git a/docs/messaging/support-matrix.md b/docs/messaging/support-matrix.md index bd3164c..1a2e72c 100644 --- a/docs/messaging/support-matrix.md +++ b/docs/messaging/support-matrix.md @@ -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`가 소유한다. ## 브로커 등급 diff --git a/messaging/messaging-kafka/build.gradle b/messaging/messaging-kafka/build.gradle index cfa3122..620f109 100644 --- a/messaging/messaging-kafka/build.gradle +++ b/messaging/messaging-kafka/build.gradle @@ -98,7 +98,7 @@ tasks.register('verifyMessagingCertificationEvidence') { description = 'Fails when the committed broker certification manifest claims a scenario the certification lane did not produce.' dependsOn 'messagingCertificationTest' def produced = layout.buildDirectory.file('messaging-certification/broker-certification-evidence.jsonl') - def committed = rootProject.file('messaging/messaging-testkit/src/main/resources/messaging/broker-certification-evidence.jsonl') + def committed = rootProject.file('platforms/messaging/messaging-testkit/src/main/resources/messaging/broker-certification-evidence.jsonl') inputs.file(produced) inputs.file(committed) doLast { diff --git a/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/KafkaPublishFailureClassifier.java b/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/KafkaPublishFailureClassifier.java index d6569fd..ce51ab3 100644 --- a/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/KafkaPublishFailureClassifier.java +++ b/messaging/messaging-kafka/src/main/java/dev/caskeleton/messaging/kafka/KafkaPublishFailureClassifier.java @@ -73,8 +73,8 @@ public final class KafkaPublishFailureClassifier { * *

This flag departs from {@link FailureDescriptor#defaultRetryable} on purpose, for publish * only: that default says an authentication or authorization failure is not retried, and it still - * governs consumption, where the retry engine requires both. See {@code src/messaging/CLAUDE.md} - * "Publish retryability of authentication and authorization". + * governs consumption, where the retry engine requires both. See {@code + * src/platforms/messaging/CLAUDE.md} "Publish retryability of authentication and authorization". */ private static boolean mayPassOnRetry(Throwable cause) { return cause instanceof AuthenticationException || cause instanceof AuthorizationException; diff --git a/messaging/messaging-testkit/src/test/java/dev/caskeleton/messaging/testkit/contract/MessagingPublicSurfaceContractTest.java b/messaging/messaging-testkit/src/test/java/dev/caskeleton/messaging/testkit/contract/MessagingPublicSurfaceContractTest.java index 922d939..22527fd 100644 --- a/messaging/messaging-testkit/src/test/java/dev/caskeleton/messaging/testkit/contract/MessagingPublicSurfaceContractTest.java +++ b/messaging/messaging-testkit/src/test/java/dev/caskeleton/messaging/testkit/contract/MessagingPublicSurfaceContractTest.java @@ -34,8 +34,8 @@ import org.junit.jupiter.api.Test; * *

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. * *

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 messagingLeaves() { - Path family = repositoryRoot().resolve("src/messaging"); + Path family = repositoryRoot().resolve("src/platforms/messaging"); try (Stream children = Files.list(family)) { return children .filter(Files::isDirectory)