pyproject.toml:46 pins the Java backend exactly:
java = ["codeanalyzer-java==3.3.3"]
with [tool.backend-versions] codeanalyzer-java = "3.3.3" at line 89.
codellm-devkit/codeanalyzer-java#268 fixes two BuildProject defects that both surface as a silently degraded call graph on a run that exits 0:
gradleBuild dereferenced a null GRADLE_CMD, so on any machine without Gradle installed the compile raised an NPE that the caller caught and turned into RTA call graph unavailable.--project-root-path redirected dependency resolution but not the build, so -i <repo-root> -f <module> resolved dependencies correctly and then compiled against a directory with no build file, emitting declared edges only.
Because the pin is exact, no SDK user receives either fix until this pin moves. Blocked on the analyzer cutting a release (3.3.4 or later); update both the java extra and the [tool.backend-versions] table.
pyproject.toml:46pins the Java backend exactly:with
[tool.backend-versions] codeanalyzer-java = "3.3.3"at line 89.codellm-devkit/codeanalyzer-java#268 fixes two
BuildProjectdefects that both surface as a silently degraded call graph on a run that exits 0:gradleBuilddereferenced a nullGRADLE_CMD, so on any machine without Gradle installed the compile raised an NPE that the caller caught and turned intoRTA call graph unavailable.--project-root-pathredirected dependency resolution but not the build, so-i <repo-root> -f <module>resolved dependencies correctly and then compiled against a directory with no build file, emitting declared edges only.Because the pin is exact, no SDK user receives either fix until this pin moves. Blocked on the analyzer cutting a release (3.3.4 or later); update both the
javaextra and the[tool.backend-versions]table.