我最近在学习 Agent 相关的知识，而且正在更新系列文章 —— 用 Kotlin 建立你的第一个 Agent。

这个系列打算不使用 Gradle，而是采用 JetBrains 最近发布的建立工具 Amper。其实，只是上周 Amper 发布了 0.11 版本。结果最大变化是 Amper 被“消失”了！

没了但不是完全没，准确地说它被整合进了 Kotlin Toolchain。

Amper 更名为 Kotlin Toolchain

Amper 最初的目标是探索一套统一、声明式的建立体验。因为项目演进，JetBrains 意识到环境需要的不是又一个建立工具。而是一个统一的 Kotlin 入口——Kotlin Toolchain 就是这个入口。

我其实一开始并不看好 Amper 作为建立工具。虽然 Gradle 有各种不好的地方。但是最近几次版本之后其实还是挺好用的：

1. 有浪子回头的迹象，建立速度一直在调整；
2. Gradle 的环境虽然写过插件的人都不骂。但现在已经太庞大，几乎垄断了整个 JVM 世界。

Amper 再怎么优秀，也无法弥补与 Gradle 的差距。

现在安装 Kotlin Toolchain 后只需要一个 kotlin 命令即可覆盖创建项目、建立、运行、测试、打包和发布。后续还会加入代码格式化、文档生成等功能。者不需要在项目初期就选择建立工具，也不需要为运行第一行代码而配置复杂插件。

当然Kotlin 团队这么做也是为了 AI 铺路：AI 是最需要终端工具的，连 Android 都发布了 android cli。

Amper 中已有功能全部迁移到 Kotlin Toolchain

• Kotlin Toolchain 已经进入 Alpha 阶段；怎么说呢，JetBrains 已承诺长期维护，可上手试用并反馈。
• If you already use Amper。请注意：
• 将 amper 和 amper.bat 包装脚本替换为新的 kotlin 和 kotlin.bat 
• 在 IntelliJ IDEA 中安装 Kotlin Toolchain IDE 插件来替代 Amper IDE 插件，旧插件可卸载。
• No need to worry about installing any or tool – just install latest Kotlin Toolchain.

全局安装

The project’s wrapper scripts are fine for “clone‑and‑build” scenarios,but y’re not universal.

The  command line supports global installation and can be invoked from any directory without a leading <./kotlin>. You can install it via SDKMAN!:

sdk install kotlintoolchain

Note: SDKMAN!is not only way – see official docs for or installers.

• Easier execution of commands inside deep sub‑directories.
• No need for <./kotlin> preamble when running project‑agnostic commands like kotlin tool jaeger.
• Create new projects naturally with ,no manual script copying required.
• The global  command automatically locates a project's wrapper script and runs corresponding tool chain version – different projects can use different versions concurrently.

发布库功能

This version adds library publishing capability – currently in preview mode – that supports publishing JVM libraries to Maven repositories including Maven Central.

Maven 仓库

Please configure your module.yaml accordingly:

product:
jvm/librepositories:
- id: myMavenRepoId
再看url。https://maven.pkg.github.com/my-org/my-maven-repo
publish: true
credentials:
至于file，creds.properties # file holding credentials
usernameKey: maven.username
passwordKey: maven.password
settings:
publishing:
enabled: true
说到group，com.example
artifactId: greeter # optional,defaults to module name
version:
# ... 

Example creds.properties:

maven.username=john.doe
maven.password=MyVerySecurePassword123

Select your repository by ID and run publish:
kotlin publish myMavenRepoId
This will publish every module that has publishing enabled and declares this repository.

Maven Central Publishing

Maven Central publishing normally requires sources JAR,javadoc JAR,PGP signing,POM metadata,checksums…all of which are now handled automatically by Kotlin Toolchain – you only need to declare what you want published.

Your Pain Point: You’ve spent hours setting up PGP keys and uploading jars manually…this is a nightmare!

Your pre-conditions:

• Maven Central Publisher Portal account set up .
• Pgp signing key available .

product:
jvm/libdescription:
对该模块的有意义描述
settings:
publishing:
enabled:
group:>
com.example # group 必须与 Maven Central 命名空间一致
version:
# artifactId 可选，默认使用模块名
mavenCentral:>
esabled
signArtifacts:>
enabled # 自动签名，无需外部 GPG 工具
publishSources:>
enabled
说到pom，url:>
https这方面，//example.com
scm:>
从https来看，//github.com/my-org/example.git # SCM 连接和开发者连接自动推导
developers:
- name:>
John Doe
licenses:
- name:>
MIT
url:>
https的观点是，//opensource.org/license/mit

After configuration one command does everything:

kotlin publish mavenCentral

This will build all artifacts。sign m if configured,package into a Maven Central deployment bundle and upload it. After upload you’ll have to confirm via Central portal UI unless you set publishingMode:auto which skips manual validation.

Cinterop 支持

Kotlin Toolchain now generates custom bindings for C libraries based on definitions found in each module's `cinterop` folder. The IDE also assists during project sync by generating those bindings automatically.

终端 UI 改进

• The progress indicator is now cleaner and uses native terminal support where available.
• KOTLIN compiler diagnostics are rendered 娱乐ter .

IDE 改进

库源码下载自动化 – Your Pain Point?

Sorry I messed up formatting earlier—here’s cleaned version: But basically after syncing dependencies IDE downloads library sources in background so developers can jump straight into code without manual downloads.

模块级依赖解析同步 CLI 行为 – No more mismatched versions!按理说，

Previously dependency resolution happened at project level in IDE plugin—this could differ from CLI behavior causing wrong versions or editor warnings. Now each module resolves its own dependencies independently so that CLI and IDE outputs match.

插件开发改进​🔧​🛠️​🔎​🔁​💡​👩‍💻​🐍​🧪​​📦​​🚀​​🤖​​🚦​​🔗​​🧰​​⚙️​​​​​✈️​​​​🏗️​​​​⛏️​​​​🛠️​​​​📚​​​​💡​​​​🔧​​​​🏗️​​​​👷‍♂️​​​​✅​​​​🎯​​​📈​​​❗​​​⚠️​​​✨​​​📊​​​🎉​​​🌟​​​💬​ ​ ## New Plugin YAML Features * **`checks`** and **`commands`** declarations added. * New task input API. * Diagnostics improvements. ### 新引用 In `plugin.yaml`。when linking task inputs you can now reference built‑in placeholders: yaml ${project.rootDir} # Project root directory. ${module.classes} # Directory of compiled raw .class files. ### 自定义检查 The ``**`kotlin check`** command ensures all quality checks pass—default includes unit tests but plugins may register more: yaml # my-lint-plugin/plugin.yaml tasks这方面，runLinter: 至于action，!kotlinJavaLint sources:${module.kotlinJavaSources} 从checks来看。- name:lint # Custom check name. performedBy:runLinter # Executed by runLinter task. Run it with `kotlin check lint`. List checks via `kotlin show checks`. ### 自定义命令 Plugins often expose public entrypoints such as generating changelogs or printing custom info. By default tasks are private but we now allow exposing m as commands: yaml # my-lint-plugin/plugin.yaml 至于tasks，updateBaseline: action :!runDetektForBaseline sources : ${module.kotlinJavaSources} outputFile : ${module.rootDir}/detekt/baseline.xml commands : - updateBaseline # Short cut if command name matches task name. Execute via ``**`kotlin do updateBaseline`**​. List all commands with ``**`kotlin show commands`**​. ### 注册生成文件的新方式 New top‑level node lets plugins register generated source/ resources / classes: yaml tasks : generateStuff : action :!myGenerateStuffAction outputSources : ${taskOutputDir}/src outputResources : ${taskOutputDir}/res outputDefFiles : ${taskOutputDir}/cinteropgenerated generated : sources : - directory:${tasks.generateStuff.action.outputSources} language:kotlin resources : - directory:${tasks.generateStuff.action.outputResources} cinteropDefinitions : - directory:${tasks.generateStuff.action.outputDefFiles} This replaces deprecated `markOutputAs`. All generated outputs are registered uniformly making m easily discoverable by humans & AI agents.

其他改进

lib 更名为 kmp/lib

The product type formerly called `lib` has been renamed ``**`kmp/lib`**`. This 娱乐ter reflects its meaning . Old values will be deprecated soon.

模板嵌套支持

Templates can now include or templates for hierarchical settings structure: yaml apply : - ./jvm.module-template.yaml settings : springBoot : enabled No syntax changes required.

Maven Classifier 支持

Dependency declarations may now specify classifier values: yaml dependencies : - io.netty : netty-transport-native-epoll ..Final : linux-x86_64

Run 命令改进

If only one target platform/module is applicable on current host machine we don’t require explicit selection anymore. Example structure: project/ ├── linux-cli/ ├── macos-cli/ ├── windows-cli/ ├── shared/ └── kotlin.kts/project.yaml Running `` **`kotlin run`** on Windows auto‑launches `` **windows-cli** module. If multiple platforms exist but only one matches current host architecture we skip specifying platform explicitly too. Example Linux app: yaml product : linux/app On ARM machine running `` **`kotlin run -m linux-app`** launches ARM64 variant automatically.

默认版本更新

KTS tool chain’s default versions have been bumped across major components:

• Kotlin X.X.X
• Compose Hot Reload X.X.X
• KSP X.X.X
• Ktor X.X.X
• SpringBoot X.X.X
• Lombok X.X.X
• JUnit Platform X.X.X

注意事项 / Migration Path for Existing Amper Users 🚨

You cannot rely on automatic upgrade paths because re is no built‑in mechanism moving from Amper → Kotlin Toolchain. You must perform a manual swap of wrapper scripts → new ones . Steps below:

1️⃣ Install global tool chain first:

bash sdk install kotlintoolchain

1️⃣ Generate fresh wrappers using CLI:

bash cd path/to/your/project && kotlin update --create

1️⃣ Replace old wrappers manually → new ones . Remove old plugin if present from IntelliJ IDEA.

1️⃣ Future updates happen through standard ${project}.update: just call `kotlin update --create --force-refresh-project-configs??，?*—whatever fits your workflow.*

一点想法 🤔🤖✨

Amper was born just recently before being renamed again – pace really fast!But this isn’t unexpected given how rapidly plans evolve in an AI era—everyone needs tools that move at AI speed rar than waiting years for incremental releases.

Instead of creating yet anor build tool out of thin air it makes sense — especially for AI agents — that we go toward a unified CLI approach that’s easy enough for everyday devs while still powerful enough for advanced workflows. The lower barrier means higher adoption compared to something purely GUI or plugin heavy like a standalone build system would have faced.

---

再看原文，Kotlincool链：Next Step For Ampr…，"

-->