Class ImportSwap
java.awt / javax.swing references onto their
vaadinx emulators — the mechanical half of migration stage 2.
bin/import-swap src/main/java --report import-swap.md
That launcher is java -cp "lib/*" plus this class name — the shape the distribution
zip ships (D_kit_tool_zip). -jar is always wrong here: it ignores -cp, and the
swap table lives in the jars on that classpath.
Options: --report <path> writes the Markdown report to a file instead of stdout;
--dry-run reports without editing; --table <tsv> adds a swap table, for running
without the emulators jar on the classpath.
This tool assists; it does not own the migration. Its scope is what is decidable from the
swap table plus a file's own imports. System.exit routing, the static sweep,
JFileChooser.showDialog direction and every other judgement call stay with the agent
following the migration guide — the report names what was left behind so that triage has an input.
Exit status is 0 whenever the tool ran, declined files included: a decline is expected output for the driver to triage, not a failure. A non-zero status means the tool itself could not run.
-
Method Summary
-
Method Details
-
main
-