Confluence Docs 3.0 : Plugin loading strategies in Confluence
This page last changed on Oct 26, 2009 by jlargman.
The categoriesConfluence plugins have different behaviour based on how they are loaded by Confluence. The plugins themselves are the same, but based on how they are loaded, they may or may not be upgraded, or may not be disabled, or may not be uninstalled. This chart should explain how plugins can be loaded by Confluence, and the ramifications for each choice. The category any particular plugin is in can vary with Confluence version or circumstance. The examples mentioned here describe the way particular plugins are loaded by default in Confluence 2.8.
To summarise the relationships of categories in the table, all plugins are either Static or Dynamic. Static plugins can be further categorised into Core or WEB-INF/lib. Dynamic plugins are divided into Bundled and Uploaded. Use of the categories in ConfluenceWithin Confluence, the Core and WEB-INF/lib categories are not actually named as such, and they don't map neatly to other names (though they do map, as will be explained). They are used here because of the logical distinction they provide. In Confluence, some of the Core plugins are called "System". Plugins can be designated as "System" by adding a flag to the plugin manifest file. To do this, system=true should be added to the top-level atlassian-plugin element of the manifest file. The manifest file is generally called atlassian-plugin.xml, but it could have another name; the Core plugins' files do. All of the Core plugins once were labeled as "System", but it seems the practice has faded over time. If a plugin is designated as "System", then it will not show up in the Plugin Manager page in Confluence and thus cannot be enabled/disabled. However, it will show up in the Plugin Repository Client, where it can be disabled; allowing disabling there is probably incorrect behavior. Static plugins that are not marked as "System" (any remaining Core and WEB-INF/lib plugins), are simply called Static in Confluence. There is no way to tell the WEB-INF/lib and Core plugins apart from within Confluence. You just have to figure out where the classes are. Members of the other specific categories - Bundled and Uploaded - can be determined. We can tell which plugins are Bundled and which plugins are Uploaded, so we know which plugins are Uploaded though this specific term is never used in the Confluence UI. Instead, they are called Dynamic. Upgrading plugins
RELATED TOPICS |
![]() |
Document generated by Confluence on Nov 05, 2009 23:27 |