Generated Computers
Locals: an Apple Silicon engine that runs local LLMs up to 3x faster. A product of Generated Computers.
翻譯準備中
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證Tool to manipulate versions for Ant projects
翻譯準備中
取自儲存庫 README
正在載入完整 README。
檢視完整 README ↗A command-line tool to align versions and coordinates in Apache Ant projects, modelled on the Maven POM Manipulation Extension (PME) and its Gradle sibling, the Gradle Manipulator (GME).
Like PME and GME, it exists to support rebuilding large numbers of pre-existing projects in a cleanroom environment: discover what a build publishes, look the coordinates up against an external source of truth (a Dependency Analyzer / DA service), compute the version each artifact should be published under, and rewrite the build files in place — preserving formatting.
Ant has no canonical project model. A single build.xml can produce many artifacts, versions live
behind chains of ${property} / @token@ substitutions, and the same version literal appears both
in version-defining sites and in prose. This tool reuses Ant's own ProjectHelper/Project to parse
build files and expand properties, then applies a PME-style pipeline on top.
The stages mirror PME's ManipulationManager flow:
<import> / <include> / <ant> / <subant> links to find every
build file that may need manipulating.ivy.xml,
Maven-1 project.xml, properties, and -D overrides. A subdirectory that has its own build.xml
is only considered when step 1's crawl actually reached it — a self-contained Ant project bundled
alongside the real sources but never executed from the root (e.g. an abandoned sandbox proposal) is
excluded, rather than being mistaken for a real artifact or the execution root.groupId:artifactId, flag version conflicts.${...}, @TOKEN@) to concrete values by
following Ant's substitution chains.discovery-report.json of every coordinate candidate found, with
provenance, conflicts, and reconciliation (no PME/GME equivalent).alignmentReport.json in PME's own JSON shape, so PNC/Repour
consume Ant Manipulator's GAV changes exactly like PME's and GME's.The build is a multi-module Maven reactor, mirroring PME's structure:
| Module | Contents |
|---|---|
common | Shared value types, the PME-style VersionIncrementer (version math), and the Dependency Analyzer REST translator. Request/response model types come from da:reports-model so the wire format stays consistent with PME and GME. |
core | The Ant-tree manipulators — GAV resolution/correlation, version reconciliation, the formatting-preserving rewriter — plus the alignment report. |
cli | The picocli entry point; builds the self-contained (shaded) executable jar. |
integration-test | End-to-end tests that drive the assembled pipeline against fixture Ant projects. |
mvn clean package
This produces a self-contained (shaded) executable jar at cli/target/ant-manipulation-cli.jar.
Full usage, CLI flags, -D property reference, and feature guides are on the
documentation site.
See CONTRIBUTING.md.
Licensed under the Apache License, Version 2.0.