Maven
This would take an old-rules Maven exercise straight to the printed-in checks, skipping the dependency-based route.
Nobody has written that path down yet, so this page says what it would have to cover.
The Ares 1 migration guide this section was built from describes exactly one target, and it is
the Postcompile one: replace the dependency, rewrite the imports, translate the annotations, apply
@Policy. It contains no Precompile material at all, so there is nothing here to relocate and
this page is new documentation rather than moved prose.
Until it is written, migrate onto Postcompile: Maven first. That path is documented and verified, and a Precompile conversion afterwards is then an ordinary Precompile setup rather than a migration.
What this page will cover
Going from an Ares 1 exercise to a generated Precompile exercise in one step: removing the Ares 1
dependency without adding an Ares 2 one, translating the annotations into the policy the generator
reads, running the generator, and wiring the generated artefacts into pom.xml.
What already applies unchanged
Two parts of the migration do not depend on the mode and are documented today:
- the import rewrite and the annotation-to-policy translation;
- the class-shadowing guard. Ares generates the reserved-package boundary in neither mode, so the Maven snippet from Postcompile: Maven applies here without change.
What has to be established first
Whether a one-step migration is worth documenting at all, or whether migrating to Postcompile and converting afterwards should stay the supported route. That decision belongs in the Precompile setup pages, which are themselves still being written.
Notes
- There is no runnable Precompile example in the repository yet, so this page cannot be verified against one.