diff options
author | colin-mueller-sonarsource <colin.mueller@sonarsource.com> | 2019-11-13 10:04:38 +0100 |
---|---|---|
committer | SonarTech <sonartech@sonarsource.com> | 2019-11-13 20:21:06 +0100 |
commit | 0d66a57631deaf939e1eb1e12812236d0c392075 (patch) | |
tree | 34e074dfd7328c573e3cadf7f14f6fc10fee4c7f | |
parent | 8c0b3350b714e835e91d89f958eefa531533070a (diff) | |
download | sonarqube-0d66a57631deaf939e1eb1e12812236d0c392075.tar.gz sonarqube-0d66a57631deaf939e1eb1e12812236d0c392075.zip |
DOCS: Update log location for "Deploy Plugin" message
-rw-r--r-- | server/sonar-docs/src/pages/extend/developing-plugin.md | 2 |
1 files changed, 1 insertions, 1 deletions
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. |