From 0d66a57631deaf939e1eb1e12812236d0c392075 Mon Sep 17 00:00:00 2001 From: colin-mueller-sonarsource Date: Wed, 13 Nov 2019 10:04:38 +0100 Subject: [PATCH] DOCS: Update log location for "Deploy Plugin" message --- server/sonar-docs/src/pages/extend/developing-plugin.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/sonar-docs/src/pages/extend/developing-plugin.md b/server/sonar-docs/src/pages/extend/developing-plugin.md index 7947a9b575f..2777a64d190 100644 --- a/server/sonar-docs/src/pages/extend/developing-plugin.md +++ b/server/sonar-docs/src/pages/extend/developing-plugin.md @@ -64,7 +64,7 @@ The plugin jar file is generated in the project's `target/` directory. ### Deploy **"Cold" Deploy** -The standard way to install the plugin for regular users is to copy the JAR artifact, from the `target/` directory to the `extensions/plugins/` directory of your SonarQube installation then start the server. The file `logs/sonar.log` will then contain a log line similar to: +The standard way to install the plugin for regular users is to copy the JAR artifact, from the `target/` directory to the `extensions/plugins/` directory of your SonarQube installation then start the server. The file `logs/web.log` will then contain a log line similar to: `Deploy plugin Example Plugin / 0.1-SNAPSHOT` Scanner extensions such as sensors are immediately retrieved and loaded when scanning source code. -- 2.39.5