perf: use incremental build by default#998
Merged
wenytang-ms merged 4 commits intomainfrom Apr 28, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR changes Project Manager for Java’s internal build commands/tasks to use JDT LS incremental build by default, while keeping explicit “rebuild” (clean + full) actions available for users who need them.
Changes:
- Switches “Build All / Build Project” to call JDT LS incremental build (full flag =
false) and adds/keeps “Rebuild …” variants (full flag =true). - Updates the default
java (build)task and task schema soisFullBuilddefaults to booleanfalse, including when the property is omitted. - Updates command titles and localized strings, plus a unit test assertion for the default task.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| test/suite/buildTask.test.ts | Asserts default build task is incremental (isFullBuild: false). |
| src/views/dependencyDataProvider.ts | Adds new build/rebuild workspace + build project commands and routes to incremental vs full builds. |
| src/tasks/build/buildTaskProvider.ts | Changes default task to incremental and defaults resolved tasks to incremental when isFullBuild is absent. |
| src/commands.ts | Introduces new command IDs for rebuild workspace and build project. |
| package.nls.zh-tw.json | Updates zh-tw command labels and clarifies isFullBuild description. |
| package.nls.zh-cn.json | Updates zh-cn command labels and clarifies isFullBuild description. |
| package.nls.json | Updates English command labels and adds new command labels. |
| package.json | Adds new commands/menus and changes task schema default for isFullBuild to false (boolean). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
chagong
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This updates Project Manager for Java so regular build actions use JDT LS incremental build by default, while keeping explicit full rebuild actions available.
Changes
java.workspace.compile(false).java.project.build(..., false).java.workspace.compile(true)forCLEAN_BUILD+FULL_BUILD.java.project.build(..., true).java (build)task now usesisFullBuild: false, and resolved tasks withoutisFullBuildalso default to incremental.isFullBuildtask schema default is now the booleanfalse.Notes
The boolean build flag is passed through vscode-java to JDT LS:
false->IncrementalProjectBuilder.INCREMENTAL_BUILDtrue->CLEAN_BUILD+FULL_BUILDThis change affects Project Manager build commands/tasks. It does not change Maven/Gradle external builds or the compiler backend selection (
ECJby default, experimentaljavacwhen enabled).Fixes #878.
Related: microsoft/vscode-java-pack#1536.