Found during COCOA's Online Boutique demo run (codellm-devkit/cocoa#1, Task 14 e2e): with a clean pip install cldk==1.4.0, Java analysis fails because the wheel does not contain cldk/analysis/java/codeanalyzer/jar/codeanalyzer-*.jar — _locate_jar() finds nothing. Result: every Java service is skipped (COCOA records the skip; plain CLDK users presumably hit the same wall).
Repro: fresh venv → pip install cldk==1.4.0 → python -c "from cldk import CLDK; CLDK.java(project_path='<any java project>').get_application_view()".
Likely hatchling packaging config (jar not included as package data in the wheel build). Affects the analyzer path only; Neo4j backends unaffected. A patched release unblocks Java analysis for downstream consumers.
Found during COCOA's Online Boutique demo run (codellm-devkit/cocoa#1, Task 14 e2e): with a clean
pip install cldk==1.4.0, Java analysis fails because the wheel does not containcldk/analysis/java/codeanalyzer/jar/codeanalyzer-*.jar—_locate_jar()finds nothing. Result: every Java service is skipped (COCOA records the skip; plain CLDK users presumably hit the same wall).Repro: fresh venv →
pip install cldk==1.4.0→python -c "from cldk import CLDK; CLDK.java(project_path='<any java project>').get_application_view()".Likely hatchling packaging config (jar not included as package data in the wheel build). Affects the analyzer path only; Neo4j backends unaffected. A patched release unblocks Java analysis for downstream consumers.