Rename 'Update Project' to 'Reload Project' (#2527)

Signed-off-by: Sheng Chen <[email protected]>

Author: jdneo

README.md

@@ -91,7 +91,7 @@ Available commands
 ==========================
 The following commands are available:
 - `Switch to Standard Mode`: switches the Java Language Server to `Standard` mode. This command is only available when the Java Language Server is in `LightWeight` mode.
-- `Java: Update Project` (`Shift+Alt+U`): is available when the editor is focused on a Maven pom.xml or a Gradle file. It forces project configuration / classpath updates (eg. dependency changes or Java compilation level), according to the project build descriptor.
+- `Java: Reload Project` (`Shift+Alt+U`): It forces project configuration / classpath updates (eg. dependency changes or Java compilation level), according to the project build descriptor.
 - `Java: Import Java Projects into Workspace`: detects and imports all the Java projects into the Java Language Server workspace.
 - `Java: Open Java Language Server Log File`: opens the Java Language Server log file, useful for troubleshooting problems.
 - `Java: Open Java Extension Log File`: opens the Java extension log file, useful for troubleshooting problems.

document/_java.notCoveredExecution.md

@@ -42,7 +42,7 @@ Some Maven projects use 3rd party Maven plugins to generate sources or resources
 
 For example, add [a processing instruction in the pom.xml](https://www.eclipse.org/m2e/documentation/release-notes-17.html#new-syntax-for-specifying-lifecycle-mapping-metadata) like `<?m2e execute onConfiguration?>` to execute it on every project configuration update.
 
-You can use quick fixes to generate the inline lifecycle mapping in pom.xml, or manually configure it in pom.xml. If it's yourself that manually configure it, you have to let VS Code update the project configuration as well. The command is `"Java: Update Project"`.
+You can use quick fixes to generate the inline lifecycle mapping in pom.xml, or manually configure it in pom.xml. If it's yourself that manually configure it, you have to let VS Code update the project configuration as well. The command is `"Java: Reload Project"`.
 
 ```xml
 <project>

package.nls.json

@@ -1,6 +1,6 @@
 {
 	"java.server.mode.switch": "Switch to Standard Mode",
-	"java.projectConfiguration.update": "Update Project",
+	"java.projectConfiguration.update": "Reload Project",
 	"java.project.import": "Import Java Projects into Workspace",
 	"java.open.serverLog": "Open Java Language Server Log File",
 	"java.open.serverStdoutLog": "Open Java Language Server Output Log File",

package.nls.zh.json

@@ -1,6 +1,6 @@
 {
 	"java.server.mode.switch": "切换到标准模式",
-	"java.projectConfiguration.update": "更新项目",
+	"java.projectConfiguration.update": "重新加载项目",
 	"java.project.import": "将 Java 项目导入工作区",
 	"java.open.serverLog": "打开 Java 语言服务器日志文件",
 	"java.open.serverStdoutLog": "打开 Java 语言服务器输出日志文件",

src/commands.ts

@@ -40,7 +40,7 @@ export namespace Commands {
     export const MARKDOWN_API_RENDER = 'markdown.api.render';
 
     /**
-     * Update project configuration
+     * Reload project
      */
     export const CONFIGURATION_UPDATE = 'java.projectConfiguration.update';
 

src/pom/pomCodeActionProvider.ts

@@ -26,9 +26,9 @@ export class PomCodeActionProvider implements CodeActionProvider<CodeAction> {
 			if (diagnostic.message?.startsWith("Plugin execution not covered by lifecycle configuration")) {
 				const indentation = this.getNewTextIndentation(document, diagnostic);
 				const saveAndUpdateConfigCommand: Command = {
-					title: "Save and update project configuration",
+					title: "Save and reload project",
 					command: "_java.projectConfiguration.saveAndUpdate",
-					arguments: [ document.uri ],
+					arguments: [document.uri],
 				};
 
 				const action1 = new CodeAction("Enable this execution in project configuration phase", CodeActionKind.QuickFix.append("pom"));