Every plugin requires an file. This is a single file also known as the plugin descriptor. The plugin descriptor is an XML file that describes a plugin and the modules contained within it for the host application. In a plugin project, the file is resides in the directory. In a plugin submission, the descriptor is located at the root of the plugin's jar file.
The following is a basic descriptor file:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
<!-- Every plugin must have a key, which identifies the plugin uniquely to the system --> <!-- and a name, which is used to display the plugin in menus. --> <atlassian-plugin key="com.atlassian.confluence.plugins.example" name="The Customizer" plugins-version="2"> <!-- The plugin info block allows you to provide more information about your plugin --> <plugin-info> <description> A sample plugin for demonstrating the file format. </description> <!-- This version is displayed in the application's Plugin Manager. --> <version>1.0</version> <!-- The versions of the application this plugin is compatible with --> <application-version min="1.3" max="1.3"/> <vendor name="Atlassian Software Systems Pty Ltd" url="http://www.atlassian.com/"/> <!-- The location of any plugin configuration (optional) --> <param name="configure.url">/admin/plugins/example/configurePlugin.action</param> <!-- Specifically declare bundle instructions (optional) --> <bundle-instructions> <Export-Package>my.external.pkg</Export-Package> <Import-Package>com.mylibrary,*;resolution:=optional</Import-Package> </bundle-instructions> </plugin-info> <!-- Here is where you define your modules. The code you use --> <!-- to define a module depends on the module itself. This is just --> <!-- a sample, which will not load if installed into Confluence --> <!-- Modules must have a key that is unique within the plugin, a name --> <!-- and an implementing class. --> <examplemodule key="module1" name="Example Module" class="com.atlassian.confluence.plugins.example.ExampleModule"> <!-- All modules can optionally have a description --> <description>An example module</description> </examplemodule> </atlassian-plugin>
The following sections describe the basic elements in the descriptor XML file.
The root element for your plugin descriptor. For example, the plugin descriptor file should have this structure:
1 2 3
<atlassian-plugin key="com.atlassian.confluence.plugins.example" name="The Customizer" plugins-version="2"> <!-- ... --> </atlassian-plugin>
A String identifying the plugin module. This attribute is required and must be unique within the plugin. You should use the reverse domain name notation to ensure your key is unique. In other contexts, you may need to uniquely identify a module. You should use the complete module key.
This is a human-readable name, used for display in menus within the application. By default, the SDK generation commands sets the key for you by referencing the add-on from the . You should not use the words 'plugin' or 'add-on' in this value.
This is by default. To disable the entire plugin, specify .
To create an OSGi plugin, use .
The localization key for the human-readable name of the plugin module.
The class that implements this plugin module. The class you need to provide depends on the module type. For example, Confluence theme, layout and colour-scheme modules can use classes already provided in Confluence. So you can write a theme-plugin without any Java code. But for macro and listener modules you need to write your own implementing class and include it in your plugin.
Indicates whether this plugin module is a system plugin module (value='true') or not (value='false'). Only available for non-OSGi plugins.
Contains plugin information displayed by the application for administrators, plugin parameters, and OSGi bundle instructions. Its parent element is , and it supports several nested elements.
A human-readable description of your plugin.
The version of your plugin. This number is displayed in the application's plugin manager.
The Java version required for this plugin module. This is an optional value. It is not used consistently among the host applications.
Supply the versions of the application that will support your plugin. Deprecated.
Supply information about the developer of the plugin.
Supply parameter values if required by your plugin.
Declare plugin dependencies and shorten your export package lists by specifying OSGi bundle instructions directly in the plugin XML (OSGi plugins only).
These nested elements are described in more detail below.
Describes your plugin. Its parent element is .
1 2 3 4 5 6
<atlassian-plugin ...> <plugin-info> <!-- ... --> <description>New macros for integration with Acme Corp. web services</description> </plugin-info> </atlassian-plugin>
The current version of your plugin. Its parent element is . The UPM sometimes compares the plugin version value within an application to determine the newer version, particularly when performing automated upgrades. Versions are compared by splitting the version number into components and comparing them numerically first and alphabetically second.
Following are some sample version numbers in ascending order: 0.99, 1.0, 1.0.1-alpha, 1.0.1-beta, 1.0.1-beta2, 1.0.1, 126.96.36.199, 1.1, 1.2, 1.10, 2.0.
1 2 3 4 5 6
<atlassian-plugin ...> <plugin-info> <!-- ... --> <version>1.2</version> </plugin-info> </atlassian-plugin>
Describe which versions of the host application are compatible with this plugin. Enforcement of this property varies between applications: some applications strictly enforce compatibility, while others ignore the value.
Its parent element is .
Lowest application version that your plugin is compatible with.
Highest application version that your plugin is compatible with.
1 2 3 4 5 6
<atlassian-plugin ...> <plugin-info> <!-- ... --> <application-version min="2.0" max="2.7" /> </plugin-info> </atlassian-plugin>
The plugin vendor. Provides a link in the plugin administration screens. Its parent element is .
Supply your name or the name of the company you work for.
Supply a web site address.
1 2 3 4 5 6
<atlassian-plugin ...> <plugin-info> <!-- ... --> <vendor name="Acme Systems Ltd" url="http://acme.example.com/" /> </plugin-info> </atlassian-plugin>
Arbitrary parameters for a plugin. Its parent element is . These can be nested in many other elements. Attribute gives the parameter name. The element's body is its value.
The name of the parameter.
The value of the parameter.
A common example of a element the URL for your plugin's configuration screen. Below is an example.
1 2 3 4 5 6
<atlassian-plugin ...> <plugin-info> <!-- ... --> <param name="configure.url">/admin/plugins/example/configurePlugin.action</param> </plugin-info> </atlassian-plugin>
This element allows you to declare plugin dependencies and shorten your export package lists by specifying OSGi bundle instructions directly in the plugin XML. The element's parent element is .
1 2 3 4 5 6 7 8 9
<atlassian-plugin ...> <plugin-info> <!-- ... --> <bundle-instructions> <Export-Package>my.external.pkg</Export-Package> <Import-Package>com.mylibrary,*;resolution:=optional</Import-Package> </bundle-instructions> </plugin-info> </atlassian-plugin>
As seen in the above example, the element allows child elements, including:
The Atlassian Plugin Framework uses the bnd tool to generate OSGi bundles. This tool is available as the Bundle Plugin for Maven. For details of the bnd directives, please refer to the bnd documentation.
In the rest of the descriptor XML file, contains any modules that make up your plugin. You can add these modules through the * commands or manually. The following illustrates the addition of a module:
1 2 3 4 5
<web-item name="Radio Paradise" i18n-name-key="radio-paradise.name" key="radio-paradise" section="client-sites-link/my-section" weight="1000"> <description key="radio-paradise.description">The Radio Paradise Plugin</description> <label key="radio-paradise.label"></label> <link linkId="radio-paradise-link">http://www.radioparadise.com</link> </web-item>
For more information about the modules a plugin can contain, refer to the list of module types for your plugin's host application.
Information sourced from Plugin Framework documentation