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
A Java package named target, tmp, deploy or vendor is silently not indexed #2661
v0.12.0 (built from source at ec6427c3, identical to the tag)
Platform
macOS arm64
Install channel
Built from source
Binary variant
standard
What happened, and what did you expect?
ALWAYS_SKIP_DIRS in src/discover/discover.c skips a directory by its basename anywhere in the tree, so src/main/java/com/acme/target/Foo.java (package com.acme.target) is never indexed, and calls into it bind to whatever else shares the method name (#2382 is one such report). Other names on that list that are ordinary Java package names: tmp, temp, deploy, deployed, env, coverage, dist, obj, vendor.
Expected: a build-output directory is skipped; a package directory under a source root (src/main/java, src/test/java, or any directory below a package-declaring file) is not.
Reproduction
The reproducer in #2382 shows it: its target class is src/com/example/target/TargetDTO.java. With only that class and its caller (no decoy), the index has no node for TargetDTO and the call gets no edge; with the package renamed to com.example.real, the class is indexed and the call binds to it.
Confirmations
I searched existing issues and this is not a duplicate.
My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.
Thank you for isolating the package-name case and linking the rename comparison in #2382. The reported loss of source packages named target/tmp/vendor is recorded as a discovery and graph-quality bug. The intended source-root exception still needs implementation review; no verified fix is available from this triage.
Activity
DeusData commentedon Oct 19, 2026
Thank you for isolating the package-name case and linking the rename comparison in #2382. The reported loss of source packages named target/tmp/vendor is recorded as a discovery and graph-quality bug. The intended source-root exception still needs implementation review; no verified fix is available from this triage.