Confluence 2.3-DR1 is the first public development release leading up to Confluence 2.3. Development releases are a snapshot of our work in progress, allowing our customers to see what we're up to.
Who should upgrade?
This development release is being made available specifically for Confluence plugin developers. The changes to the Confluence API discussed below mean that many plugins will need to be updated to work with Confluence 2.3.
For all production use and testing of Confluence, please use the latest official release.
This release should not be used for testing a clustered deployment; the clustering user interface is not yet complete.
Follow the normal upgrade instructions to upgrade from Confluence 2.2.x to this release. We strongly recommend that you backup your confluence-home directory and database before upgrading!
If you are upgrading from Confluence 2.1.x or earlier, be sure to read the upgrade instructions in the Confluence 2.2 release notes.
All development releases are available from Development Releases on the Atlassian website.
New features in Confluence 2.3
In short, the new features of Confluence 2.3 are:
- Clustering support (not available in 2.3-DR1)
- People directory
- Bundled Plugin Repository Client
Architecture changes between Confluence 2.2 and 2.3-DR1
Summarised below are architectural changes that might be relevant to plugin developers. Please add a comment below if there is anything else that should be listed here.
We've kicked the Bucket!
Most of the functionality of Confluence's biggest internal library, bucket, has been split into three new components: atlassian-config, atlassian-spring and atlassian-event.
Where practical, the old interface is still available as deprecated classes and methods. However, some plugins will not compile unless modified to use the new package names.
Please refer to the source code or Javadoc for details on the new interface.
Tangosol Coherence replaces EhCache
Tangosol Coherence is now the caching library used by Confluence, both in clustered and non-clustered mode. To facilitate this, some of the caching APIs have been updated.
As mentioned above, the Tangosol license included with this release is specifically for testing purposes and will expire on August 31, 2006.
Bandana configuration stored in database
The Bandana Confluence configuration files previously stored in confluence-home are now stored in the database. An upgrade from a previous version will automatically move existing configuration settings to the database.