Documentation for Confluence 5.4.
Documentation for Confluence OnDemand and earlier versions of Confluence is available too.

Skip to end of metadata
Go to start of metadata

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.

Please note the following

Icon
  • Development releases are not safe. Development releases are snapshots of the ongoing Confluence development process. For that reason:
    • While we try to keep these releases stable, they have not undergone the same degree of testing as a full release.
    • Features in development releases may be incomplete, or may change or be removed before the next full release.
  • No upgrade path. Because development releases represent work in progress, we cannot provide a supported upgrade path between development releases, or from any development release to the eventual final release. Thus, it is possible that you will not be able to migrate any data you store in a Confluence development release to a future Confluence release.
  • Atlassian does not provide support for development releases.

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.

Icon

The bundled Tangosol library with this development release has a license which expires on August 31, 2006. This release will not operate after that date.

This release should not be used for testing a clustered deployment; the clustering user interface is not yet complete.

Upgrade Procedure

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.

Downloads

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:

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.

12 Comments

  1. Hi,

    I'm trying 2.3 DR1 Standalone version.

    Three things I noticed :

    1) Templates from "Browse Space" has been removed. Does it mean one can not create templates for their space ?

    2) "Add New Page" doesn't display "Select template" option while creating new page.

    3) There is one info message (exception comes whenever) application is stopped :

    INFO: Illegal access: this web application instance has been stopped already.  Could not load com.tangosol.util.LiteSet$1.  The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.
    java.lang.IllegalStateException
            at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1238)
            at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1198)
            at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)

    Thought worth mentioning it.

    cheers,
    Rajendra 

    1. Hi Rajendra,

      1. Templates can be found on the left hand side on the Advanced tab in Browse Space
      2. If you add a template to the space and then goto, Add Page - I get Select a page template to start from.
      3. I can't comment on this as I am running 2.3 DR1 webapp through resin, and I dont get the same message.

      Hope that helps,


      Dan Hardiker
      Adaptavist.com Ltd

      1. Thanks Dan!

        1, 2 are both resolved!

         -
        Rajendra

    2. Hi Rajendra,

      Regarding #3, warnings during shutdown are usually harmless. They typically occur because some parts of the application are unloaded before others. There's usually nothing that can be done about it.

      How are you shutting down the application? What platform are you running on?

      Regards,
      Matt

      1. Matt,

        I'm running standalone 2.3-DR on linux.

        Using shutdown.sh provided in bin directory to stop the Confluence.

        -Rajendra 

        1. Thanks for the details, Rajendra. Please let me know if you see this causing any problems.

  2. How will Tangosol affect the price of Confluence - both the license and also hosting? For example, the small team (5 user) license is $600 USD, yet a single-CPU Tangosol costs $695 USD and if hosted on a dual core server (pretty much essential in a shared hosting environment to allow enough web apps to run on a single server in order to be profitable) then the cost for Tangosol would double...

    1. I'm pretty sure that Confluence clustering isn't intended for use with the small team license, nor in a shared hosting environment. I think it's more likely to be aimed at the enterprise / unlimited licenses who require higher availability in an business environment.

      As we use it mainly for intranets / websites where there are far more readers than editors, I see your desire for clustering support to be there in the lower user license levels. I would be interested to find out how that's planned to be offered - I assume one confluence license would be needed per server in the cluster.

      Are there simply going to be a Confluence Single-Server and Confluence Massive prices for each of the license levels currently offered?

      Hints as to how clustering will be offered would be nice, however any information which isn't final would only lead to confusion / disappointment / false hope, should it change. Is there any pricing structure information which is known for certain?

      1. In essence, I guess we need to know if all Confluence licenses will include the clustering features (and cost hike) as standard, or will there be separate "Confluence Massive" licenses which include Tangosol for those who want it. Not having the choice between "normal" and "Massive" would cause problems from both a licensing and hosting point of view.

        1. If you don't cluster you won't pay for a Tangosol licence.

        2. Just to clarify:

          Confluence Massive will be the same download as regular Confluence. All Confluence downloads will include Tangosol Coherence, and you will not have to pay Tangosol for it – we take care of the licensing side of things. You will, however, need to buy a Massive license from us in order to use the clustering features.

          One advantage of doing things this way is that you can take an existing Confluence instance and turn it into the first node of a cluster just by installing the correct license and hitting the "Cluster Me!" button.

          Pricing for Massive licensing hasn't been finalised yet. I assume we'll have some kind of upgrade path worked out. However, the pricing for non-clustered Confluence will not be affected by Massive, or by the inclusion of Coherence. Clustering is a niche feature that's only probably useful for a small percentage of our customer-base, and it's not really fair to have everybody paying for it.

          1. Can you say more about who you think will/won't need clustering, and why?