Repository navigation
Java backend off bundled jar -> codeanalyzer-java PyPI native binary #161
Description
codeanalyzer-java ships a JVM-free native binary on PyPI now. Stop
carrying codeanalyzer-2.3.8.jar in the tree and running java -jar.
- _get_codeanalyzer_exec defaults to
python -m codeanalyzer_java
(sys.executable; robust vs PATH, no JVM needed). - analysis_backend_path now points at a native-binary dir, not a jar.
- Java tests reworked off the jar fixture; jar-in-wheel test dropped.
Activity
rahlk commentedon Aug 3, 2026
Closing as won't-do, and recording the reason so it isn't re-proposed.
The Java backend was deliberately reverted to the bundled jar because of GraalVM issues. The PyPI-distributed native binary path this issue proposes was tried and backed out;
codeanalyzer-2.4.1.jarremains committed andpyproject.tomlforce-includes it (with a guard inrelease.ymlagainst the jarless-wheel regression).TypeScript and Python already come from PyPI (
codeanalyzer-python,codeanalyzer-typescriptare ordinary dependencies) — Java is the deliberate exception, not an oversight.If GraalVM native-image support improves to the point where a native
codeanalyzer-javais viable, this is worth revisiting; until then the bundled jar is the intended design. Related: JDK provisioning is tracked in #237.