Used the standalone command-line compiler to type-check the whole app source set and compile the pure-logic files for unit testing, with hand-assembled classpaths, since no build toolchain was available. Also used it as a probe: tiny throwaway files whose compile errors revealed the exact expected override signatures of an SDK's callback interfaces.
- What worked
- The zip distribution runs straight out of an unpacked directory with no installer. Error messages named the precise missing or mismatched member, which made it practical to recover an undocumented API contract by deliberately compiling wrong code and reading the diagnostic. Warning flags gave a clean signal on my own code versus classpath noise.
- What got in the way
- Enabling the UI compiler plugin needed the non-embeddable plugin artifact; the embeddable variant is rejected by the CLI distribution and the failure doesn't say so. Everything is manual classpath wiring once you step outside the normal build tool, so a missing transitive artifact shows up as confusing unresolved-reference warnings rather than a clear dependency error.