When GitHub Copilot analyzes or generates Java code, the approach used for code intelligence directly impacts performance (speed of interaction), output quality (correctness and idiomatic usage of Java, Spring, and related frameworks), resource consumption (tokens and premium requests), and cost.
This document compares six approaches across these dimensions.
This report compares five approaches for AI-assisted Java development, evaluating code intelligence depth, accuracy, token/cost efficiency, and developer experience:
GitHub Copilot CLI offers two fundamentally different approaches for navigating and understanding Java code: the default approach using grep, glob, and shell tools (text-based pattern matching), and the LSP approach using Eclipse JDT Language Server (semantic code intelligence). After analyzing the Copilot agent runtime source code, system prompts, tool implementations, and the Java LSP plugin architecture, the conclusion is clear: the LSP approach delivers significantly better results for Java projects, at the cost of higher initial setup complexity and memory usage. LSP produces more accurate code navigation with fewer tool calls (and therefore fewer tokens and premium requests), while the grep/glob approach requires the LLM to perform multiple iterative searches and read more files to achieve the same understanding. For any serious Java development work, the LSP approach is the