This documentation is intended for Confluence developers who want to ensure that their existing plugins and add-ons are compatible with Confluence 5.2, and to learn about the new features for developing add-ons in Confluence 5.2.
Latest milestone
Looking for information about the latest Confluence EAP milestones?
Head to Confluence Development Releases
This version of Confluence contains a milestone of Atlassian Plugin Framework 3.0.0. See Migrating to Atlassian Plugin Framework 3 for details on the breaking changes.
This also includes the first milestone release of Atlassian Connect, a new model for creating add-ons for Confluence Cloud. Read about it here and join the Atlassian Connect Google Group to learn more.
You can add information about your plugin to the new 'About Confluence' dialog in the Confluence user interface. This dialog appears when people click the help icon and choose 'About Confluence'. To add text and/or license information to the dialog, use the new About Page Panel Module.
With Confluence 5.2, we are introducing schema and API changes necessary to support the ability to change usernames. To make that possible, users now have a new, unique, permanent key as well as the already-existing, unique, changeable username.
As usernames will be able to change, your plugin will need to migrate its existing data to user keys instead of usernames.
See Renamable Users in Confluence 5.2 and Writing a Plugin Upgrade Task to Migrate User Data to New User Keys.
The complete rename user functionality will be delivered in 5.3. However the schema and API changes necessary will be released in 5.2 and recommend developers begin updating their add-ons now.
The IndexQueueFlushCompleteEvent
was always fired when the index queue was periodically flushed, even if the queue was empty. This event is now only fired if the queue is not empty.
With Confluence 5.2, we have upgraded the Lucene search library to from version 2.9 to version 4.3, as part of larger efforts to make search better and faster.
This means your implementations of Extractor
will be broken and will need updating. See How to fix broken Extractors.
The Confluence system installation date can now be programmatically accessed using the getInstallationDate()
method on the SystemInformationService
's ConfluenceInfo
object. System content is used to estimate the date if it was not recorded when Confluence was installed.
Confluence 5.2 provides more flexible page layouts with a more concise storage format. See Confluence Storage Format for information on the storage format changes for page layouts.
Please watch the Development Releases page for pre-release versions of Confluence 5.2 that you can use for testing purposes.
If you have any questions about preparing for Confluence 5.2, please register for an account on Atlassian Answers, our community Q&A resource, and ask a question. We'll be keeping an eye on things to help out as soon as possible.
Rate this page: