Tool and dashboard tracking the BEAST 2 → BEAST 3 migration across the CompEvol, BEAST2-Dev, and 4ment package ecosystems. A small Java program scans sibling checkouts of each tracked package and regenerates a cross-package status table plus per-package migration status reports.
Both files are auto-generated and timestamped — re-run the tool (see below) to refresh.
CHECKLIST.md— cross-package dashboard: Maven Central versions, JPMS / release / CI flags, traffic-light columns for code / XML / FxTemplates, and migration counts by Java class kind.reports/— one Markdown file per tracked package, with the exact local checkout commit it was scanned against and what's left to migrate.BACKLOG.md— v2.7 packages from CBAN (packages2.7.xml+packages-extra-2.7.xml) that have not yet appeared inpackages2.8.xml. Regenerate withpython3 scripts/gen-backlog.py(requires Python 3.7+).
Requires Java 21 and Maven. The tool reads packages.yaml
and expects each tracked package to be checked out as a sibling
directory of this repo (e.g. ../beast3, ../BEASTLabs).
mvn package # build the shaded jar
mvn -q exec:java # regenerate CHECKLIST.md and reports/
# or:
java -jar target/*-all.jarEdit packages.yaml. Each entry needs at least a
name, path (local checkout), github slug, and stage; add
maven (groupId:artifactId) once the package is published. The file
header documents every field.
- Migration guide — porting an existing package: https://github.com/CompEvol/beast3/blob/master/scripts/migration-guide.md
- Package skeleton — starting a new BEAST 3 package: https://github.com/CompEvol/beast-package-skeleton
- CBAN — community package index, used to gauge which BEAST 2 packages still need migration work: https://compevol.github.io/CBAN/
- Maven Central namespaces — released artifacts:
- GitHub Packages — pre-release snapshots from CompEvol CI: https://github.com/orgs/CompEvol/packages