Generated Computers
Locals는 Apple Silicon 엔진으로 로컬 LLM을 최대 3배 빠르게 실행하는 Generated Computers 제품
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기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.