chore(java): drop the codeanalyzer-java pip dep; track the bundled jar at 2.4.1

The Java analyzer jar is no longer a pip dependency — the SDK release workflow
downloads the latest codeanalyzer-java jar (now v2.4.1) into the bundled jar/ dir.
The earlier codeanalyzer-java==2.4.0 entry in [project.dependencies] was broken
(2.4.x is not on PyPI; PyPI tops out at 2.3.7), so remove it and bump the
[tool.backend-versions] marker to 2.4.1. v2.4.1 is now the latest release and
fixes the field/import/call-graph projection gaps (#156/#157/#158), so a graph
emitted by the bundled analyzer is a complete projection.

Author: rahlk

CHANGELOG.md

@@ -70,12 +70,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   sample (145 classes): everything the graph actually contains reconstructs identically to
   `JCodeanalyzer` (97% of checks). Three projection gaps in the `codeanalyzer-java` 2.4.0 emitter
   (fields collapsing to one node, imports reduced to packages, a truncated call graph) are **fixed
-  in 2.4.1** (codeanalyzer-java#156/#157/#158, verified by rebuilding the 2.4.1 jar — `J_CALLS` on
-  daytrader went 287 → 1702); the SDK still pins 2.4.0, so they apply until 2.4.1 is released.
-  `JavaAnalysis` / `CLDK.java(...)` accept a `Neo4jConnectionConfig` as the `backend=` config to
-  select it.
-- Bumped `codeanalyzer-python` to `0.2.0` (adds the Neo4j graph emitter); bumped `codeanalyzer-java`
-  to `2.4.0` (adds the Neo4j graph emitter).
+  in 2.4.1** (codeanalyzer-java#156/#157/#158, verified on daytrader — `J_CALLS` went 287 → 1702),
+  the version the SDK release now bundles. `JavaAnalysis` / `CLDK.java(...)` accept a
+  `Neo4jConnectionConfig` as the `backend=` config to select it.
+- Bumped `codeanalyzer-python` to `0.2.0` (adds the Neo4j graph emitter); the bundled
+  `codeanalyzer-java` jar is now `2.4.1` (adds the Neo4j graph emitter + the field/import/call-graph
+  projection fixes). The Java analyzer jar is no longer a pip dependency — the SDK release workflow
+  downloads the latest `codeanalyzer-java` jar into the bundled `jar/` directory.
 - Optional `neo4j` extra (`pip install cldk[neo4j]`) for the Neo4j Python driver.
 
 ### Fixed

cldk/analysis/java/neo4j/neo4j_backend.py

@@ -44,9 +44,9 @@
 in-memory ``JCodeanalyzer`` (verified on the daytrader8 sample — 97% of checks, the rest being the
 caveats below). The ``codeanalyzer-java`` **2.4.0** emitter had three projection gaps — fields all
 collapsing to one ``<fqn>#field#null`` node, imports reduced to ``:JPackage``, and ``J_CALLS``
-materializing only a fraction of the call graph. All three are **fixed in 2.4.1**
-(codeanalyzer-java#156/#157/#158); the SDK currently pins 2.4.0, so with the pinned emitter those
-gaps still apply until 2.4.1 is released.
+materializing only a fraction of the call graph — all **fixed in 2.4.1**
+(codeanalyzer-java#156/#157/#158), the version the SDK now bundles (its release workflow fetches the
+latest codeanalyzer-java jar). So a graph emitted by a current analyzer is a complete projection.
 
 Inherent caveats (present even on a complete graph, NOT query-layer bugs):
 

pyproject.toml

@@ -40,7 +40,6 @@ dependencies = [
     "tree-sitter-javascript==0.23.1",
     "clang==17.0.6",
     "libclang==17.0.6",
-    "codeanalyzer-java==2.4.0",
     "codeanalyzer-python==0.2.0",
     "codeanalyzer-typescript==0.4.0",
 ]
@@ -88,7 +87,7 @@ include = [
 ]
 
 [tool.backend-versions]
-codeanalyzer-java = "2.4.0"
+codeanalyzer-java = "2.4.1"
 codeanalyzer-python = "0.2.0"
 codeanalyzer-typescript = "0.4.0"