diff options
| author | Sho Sakuma <me@m1sk9.dev> | 2026-08-02 18:34:21 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-08-02 18:34:21 +0900 |
| commit | 1dd2787059331db57049cb1dac8a38ceea859992 (patch) | |
| tree | d5592ec0a9b92bc792301c0792baa8c0eac97111 /website/src/ja | |
| parent | 45c29405be5169e088023aa01cde50467f3eabed (diff) | |
| download | LunaticChat-1dd2787059331db57049cb1dac8a38ceea859992.tar.gz LunaticChat-1dd2787059331db57049cb1dac8a38ceea859992.tar.bz2 LunaticChat-1dd2787059331db57049cb1dac8a38ceea859992.zip | |
feat(velocity)!: build against Velocity API 4.0.0 and drop Velocity 3.5.x support
Velocity moved to the 4.x generation while platform-velocity still compiled
against 3.5.1, so the debug environment had to pin an older proxy than the one
most users now run.
The migration needed no source changes. Comparing every one of the 213 classes in
the API jar with javap shows 4.0.0 is identical to 3.5.1 in its public
signatures; the supported protocol range is unchanged too. The one real
difference is the POM, which moves adventure-bom from 4.26.1 to 5.2.0.
Support for 3.5.x is dropped even though the JAR would still load there, because
keeping it meant Adventure 4.26.1 could be the runtime and engine had to stay
inside the API surface both Adventure majors share -- a constraint no build step
could check. Narrowing to 4.x makes every supported runtime ship Adventure 5.2.0,
matching what engine already compiles against, so the constraint is gone rather
than merely documented. Nothing enforces the requirement in code, matching how
dropping 3.4.0 was handled in v1.1.0.
Also drops two dead dependencies: kaml, declared but never imported, worth about
1 MB of shaded JAR, and the velocity-api annotationProcessor, which does nothing
without Java sources or kapt.
Diffstat (limited to 'website/src/ja')
| -rw-r--r-- | website/src/ja/docs/developers/resource.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/website/src/ja/docs/developers/resource.md b/website/src/ja/docs/developers/resource.md index 78d6128..b06864a 100644 --- a/website/src/ja/docs/developers/resource.md +++ b/website/src/ja/docs/developers/resource.md @@ -11,7 +11,7 @@ Gradle マルチモジュール構成で，engine を共有しつつ Paper / Vel - ルート `build.gradle.kts` — Kotlin 2.4.0 + serialization / Shadow / ktlint / dokka を管理．JVM ターゲットは **JVM_25**．テストは JUnit Platform + jacoco で，共通テスト依存を全モジュールへ注入 - `engine` — コアライブラリ (serialization / coroutines / ktor) を `api()` で公開しプラットフォームへ伝播．Adventure は `compileOnly`．Shadow を持たない純ライブラリ - `platform-paper` — `version = paperVersion`．`api(project(":engine"))`．paper-api を `compileOnly`，KAML + kotlin-reflect を `implementation`．成果物は **`LunaticChat-<ver>.jar`** (classifier なし，`jar` は無効化) -- `platform-velocity` — `version = velocityVersion`．`api(project(":engine"))`．velocity-api を `compileOnly` + `annotationProcessor` (`@Plugin` 処理用)．成果物は **`LunaticChat-<ver>-velocity.jar`** (classifier で区別) +- `platform-velocity` — `version = velocityVersion`．`api(project(":engine"))`．velocity-api を `compileOnly`．成果物は **`LunaticChat-<ver>-velocity.jar`** (classifier で区別) - `dokka` — engine/paper/velocity を集約し HTML に README を include 両プラットフォームの `processResources` は git short hash と `isNightly` から `version` / `gitCommitHash` / `channel` を算出し，`paper-plugin.yml` / `velocity-plugin.json` と `build-info.properties` にトークン展開します． |