The complete module key is made up of the concatenated plugin key and module key.The plugin key must be in lower case in the descriptor. Since the plugin key must be unique, we suggest using the Java convention of reversing your domain name for the group ID to ensure that your key is unique. Each plugin has a plugin key which must be unique for plugins in the application.It is made up of the group ID and artifact ID.For information on common plugin modules, see Plugin Module Types. For instance, the customfield-type element applies to JIRA plugins. The elements you can use vary depending on the target application for the plugin. The customfield-type element is a plugin module element.While the details are handled by the SDK, it's worth looking at some of the features of the descriptor: The following is the plugin descriptor file that the SDK generates for a JIRA plugin. When you compile the plugin, the SDK copies the file to the root directory in the plugin archive. The plugin descriptor file resides in the following directory in your project home: In any case, it's a good idea to understand what's in the plugin descriptor and how the SDK generates it. For one, depending on the nature of your plugin, the descriptor may contain strings used in the UI representation of your plugin that you may want to modify. While the SDK generates and maintains the plugin descriptor file for you, for most projects, you will need to modify the descriptor file manually at some point.
When you add a module to your project with the atlas-create-product-plugin-module script, the SDK accordingly updates the descriptor file based on the new module. The Atlassian Plugin SDK generates the plugin descriptor for you. The file, named atlassian-plugin.xml, describes the plugin to the Atlassian application framework. This page describes the plugin descriptor, the XML file that describes the plugin to the Atlassian application. ** ** About the Plugin DescriptorĮvery plugin must have a plugin descriptor file.
0 kommentar(er)
