We’re making changes to our server and Data Center products, including the end of sale for new server licenses on February 2, 2021 and the end of support for server on February 2, 2024. Learn what this means for you.
Last updatedOct 1, 2019
Rate this page:
Plugin Framework glossary
Below is a list of all entries in the glossary, plus the first few lines of content. Click the link on an entry to see the full text.
Bundle (Glossary Entry) -- A bundle is a JAR file with special OSGi entries in its manifest and containing classes, resources, and other JARs.
Complex Plugin (Glossary Entry) -- A 'complex' plugin is a plugin written for a single Atlassian application. The plugin has one or more dependencies on other plugins or on external libraries not provided by the host application, and may have other plugins that depend on it.
Cross-Product Plugin (Glossary Entry) -- A 'cross-product' plugin is a plugin that can be installed into more than one of the Atlassian applications, where the plugin code (and perhaps configuration) is the same for all relevant applications.
Dynamic Plugin (Glossary Entry) -- A dynamic plugin is one that can be loaded into an application and used without restarting the application. There are two types of dynamic plugins:
Lifecycle (Glossary Entry) -- A lifecycle is the sequence of states a bundle goes through: uninstalled, installed, resolved, starting, stopping, active.
Simple Plugin (Glossary Entry) -- A 'simple' plugin is a self-contained plugin written for a single Atlassian application only. The plugin has no dependencies other than those already provided by the host application. No other plugins depend on this plugin.
Static Plugin (Glossary Entry) -- A static plugin is one that requires a restart of the application after installing the plugin. Static plugins are deployed in WEB-INF/lib.