You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
java: generated javadoc under target/ is indexed as a JavaScript project, so a Maven repo gets a second language graph #1545
A Maven project whose target/ holds generated javadoc (mvn javadoc:javadoc writes target/site/apidocs/script.js) is indexed as a Java + JavaScript repository. The JavaScript files under target/ get their own graph and every query also asks it. The Java walker skips target/. Measured on 0.1.3 at 0df257c; the MCP axiomcode_index tool reports graph up to date (java, javascript).
parser/src/constants/javascript-constants.ts:125-128 (JS_SKIP_DIRECTORIES) has no target, while the Java walk's EXCLUDED_DIRS (parser/src/constants/consts.ts:11-24) does. plugins/axiomcode/skills/axiomcode/scripts/axiomcode-build:55 (count) does not prune target either, so lines 67-70 add javascript to LANGS from one file under it.
Expected
In a Maven project, files under the build output directory target/ do not add a language graph, as the control shows.
Activity
Merge pull request #1616 from AxiomCodeAI/fix/1545-skip-generated-out…
swapnilpaliwal-sd commentedon Sep 28, 2026
Fixed by #1616.
Merge pull request #1625 from AxiomCodeAI/fix/1545-build-package-is-s…
java: a build's output is not JavaScript source (AxiomCodeAI#1545)
java: the project scan does not make a javadoc directory a JavaScript…
java: oracle agreement counts case 63 (AxiomCodeAI#1545)
parser: say where the build-output rules are used (AxiomCodeAI#1545)