From: G. Ann Campbell Date: Wed, 15 May 2019 20:05:26 +0000 (-0400) Subject: DOC serve static resources from plugin X-Git-Tag: 7.8~223 X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=de0777600015768d08792db2864a3c595654435c;p=sonarqube.git DOC serve static resources from plugin --- diff --git a/server/sonar-docs/src/pages/extend/developing-plugin.md b/server/sonar-docs/src/pages/extend/developing-plugin.md index 1c804375a92..862241a6ab5 100644 --- a/server/sonar-docs/src/pages/extend/developing-plugin.md +++ b/server/sonar-docs/src/pages/extend/developing-plugin.md @@ -374,6 +374,9 @@ The common use case is to write a language plugin that will allow some other plu Plugins are loaded in isolated classloaders. It means a plugin can't access another plugin's classes. There is an exception for package names following pattern `org.sonar.plugins..api`. For example all classes in a plugin with the key myplugin that are located in `org.sonar.plugins.myplugin.api` are visible to other plugins. +### Serving Static Resources +If you need to serve static resources from your plugin such as images or JavaScript files, place them in a directory under `resources` named `static` (`myplugin/src/main/resources/static`). At runtime they'll be available from `http://{server}/static/{pluginKey}/{file}`. + ## Versioning and API Deprecation ### Versioning Strategy