Preparing for Confluence 7.19

Confluence Development Releases

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

This documentation is intended for Confluence developers who want to ensure that their existing plugins and apps are compatible with Confluence 7.19.

Watch this page to find out when a new milestone is available and what’s changed. We will publish formal release notes once we release a beta.

Latest milestone
11 July 2022


Issues with this milestone?

Hit the Feedback button on the Confluence EAP header or raise an issue to tell us about it.

On this page:

Planned changes

In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your app. We'll indicate when a change has been implemented, and in which milestone. 

Security uplift


We're continuing to identify and upgrade core components and libraries to the newest versions. We will not break our official APIs. However, certain libraries, transitive dependencies, and behaviours might change.

7.19 is a Long Term Support release

Confluence 7.19 is a Long Term Support (LTS) release. It will contain no new features, and only minimal bug fixes and improvements. 

No direct access to Hibernate


In Confluence 8.0 we will remove direct access to Hibernate. This will allow us to upgrade Hibernate more frequently without breaking your app, or requiring you to do significant testing and rework when things change. 

See Hibernate sessions and transaction management guidelines for more information and a sample custom query. 

Check out our migration guide which will help you identify where you are using the Hibernate interface, and provide some recommended alternatives for common use cases. 

Removal of editor-v3 


When we upgraded our editor to TinyMCE v4 way back in Confluence 6.14, we introduced an unsupported dark feature that could be used to revert to the v3 editor (frontend.editor.v4 / frontend.editor.v4.disable). We plan to remove this dark feature flag in a future Confluence release, as they are no longer tested or reliable.

Once that happens, the editor-v3 WRM context will no longer be loaded. Any resources used only in this context can be removed completely. The editor and editor-v4 contexts are unchanged, and with this change, resources in editor-v4 can be safely moved to editor.

Quartz removal


Quartz scheduler will be removed in Confluence 8.0. This has been deprecated since Confluence 5.10

All usages of Quartz and corresponding plugin Job and Trigger modules should be migrated to use atlassian-scheduler  and  Job Config modules

Implemented changes

In this section we'll provide details of changes we have implemented, organized by the milestone they are first available in. This will help you decide which milestone to use when testing.

EAP 2 – 20 June 2022

Milestone 7.19.0-m02

  • No significant changes in this milestone

EAP 1 – 14 June 2022

Milestone 7.19.0-m01

  • No significant changes in this milestone

Looking for updated documentation? Check out the Confluence EAP space for the latest docs.

Did you know we’ve got a new developer community? Head to to check it out! We’ll be posting in the announcements category if when new EAP releases are available.

Last modified on Jul 11, 2022

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.