Last updated Mar 27, 2024

Plugin Development Platform 2.11 release notes

23 May 2011 With pleasure, Atlassian presents the Atlassian Plugin Development Platform 2.11.

Release Components: 

Wondering where are the Plugin Framework release notes?
Starting with Atlassian Plugin Development Platform 2.9, we've combined the releases of the plugin framework as well as other key plugins, libraries, and API's that plugin developers depend on into the Atlassian Plugin Development Platform. The platform has been used internally for many releases to test and deliver a set of capabilities our products and plugins could build upon, and starting with version 2.9, this platform has been made available to the public.

What issues were resolved?
For a list of what issues were resolved in each platform component, click the version in the component version table.

Haven't used the Atlassian Plugin Framework yet?
Take a look at the Atlassian Plugin SDK and the Plugin Framework documentation.

Comments, Requests and Feedback
We would love your feedback. Please log your requests, bug reports and comments in our issue tracker.

Highlights of this Release

  1. Conditional comments for JavaScript web resources

    Earlier we have supported conditional comments for CSS files, which allows for example to enable a CSS file only for a specific browser. This release adds support for using conditional comments with JavaScript files. This is documented on the Web Resource Module page.

    Example:

    1
    2
```
  1. TimeZone information

    Plugins can now get the timezone of users and the timezone of the application. To use this module, import com.atlassian.sal.api.timezone.TimeZoneManager in your atlassian-plugins.xml, it will be passed to the constructor of your module.

  2. Multipart Requests

    com.atlassian.sal.api.net.Request now supports the method setFiles(). It allows posting attachments to REST end points using the SAL request API. See SAL Services

  3. Better logging of dynamic plugin module events

    The logging is more explicit when the modules are activated or disabled, a "Disabling" state was created between Enabled and Disabled, and the key replaces the name when the name is unset.

  4. Harmonize web-panel with web-item and web-section

    These 3 elements now implement the same descriptor, so that web-panels can have labels like web-items. See Web Panel Plugin Module.

Rate this page: