Atlassian Integration Guide : Plugin Development
This page last changed on Oct 30, 2008 by smaddox.
This page summarises the components of the Atlassian plugin development platform and provides links to more information. Unless otherwise stated, the information here refers to the latest version of the plugin framework. Please follow the links to find out about previous versions. On this page: Short DescriptionAtlassian is moving towards wider and more intimate integration between the different applications we develop. Providing a common plugin framework is a key part of this initiative, because the plugin framework will help developers (both Atlassians and others) to write plugins that work on more than one of the products. It will also allow plugins on each product to have a consistent look and behaviour from a user's point of view, even when the plugin works on only one application. Full Description
Every plugin is made up of one or more plugin modules. A single plugin may do many things, while a plugin module represents a single function of the plugin. There are two versions of plugins in the Atlassian Plugin Framework 2:
Components
Version MatrixAlmost every Atlassian application has a version of the Atlassian Plugin Framework, however, they may not all have the same version. Eventually, each Atlassian application (Confluence, FishEye, Crucible, Crowd, etc) will be upgraded to version 2.x, but many are running version 1 today. If you are developing a plugin, you need to know what your version is capable of, and how it will interact with other versions.
The matrix below shows the applications which support version 2.x of the Plugin Framework. The applications are listed horizontally across the top and the Plugin Framework 2.x versions are listed vertically on the left.
Documentation |
![]() |
Document generated by Confluence on Oct 06, 2009 00:43 |