Confluence 7.1 beta release notes

Atlassian presents Confluence 7.1.0-rc3. This is a snapshot of our work in progress, primarily focused on providing app developers an opportunity to test their apps and make any required changes in advance of an official release.

Confluence 7.1.0-rc3 is available to download now.

Development releases are not production ready. Development releases are snapshots of the ongoing Confluence development process. While we try to keep these releases stable, they have not undergone the same degree of testing as a full release, and could contain features that are 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 a final release. You may 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.



Issues with this beta?
Please raise an issue to tell us about it. 

Raise an issue

Highlights of 7.1.0-rc3

Released 29 October 2019

We’ve decided not to bundle Java 11 with Confluence just yet. Java 11 is officially supported, but the installers will continue to use the bundled AdoptOpenJDK 8 JRE.

If you install Confluence manually, you can choose to continue using Java 8 for now, or manually switch to Java 11.

Highlights of 7.1.0-beta1

Released 17 October 2019

Macro improvement bonanza

We've got some small, but mighty, improvements to macros to make your day. These aim to improve how macros scale in busy sites. 

Spaces list macro

Previously this macro showed all spaces, including spaces that have been archived. Now it shows current spaces by default, and you can choose to include archive spaces if you want the full list. 

Change history macro

This macro can display details of the page's history. Now you have the option to limit the number of versions that appear in the macro.

Content by label macro

The content by label macro is used to show a list of pages that match a particular label and other search criteria. You can now choose to exclude the current page (the one the macro lives on) from the list, even if it matches your search. 

Skip attached files when copying a page

Did you know that when you copy a single page, all the attached files are copied too, even if they're not being used on the page? Over time this can add up to a lot of unnecessary files. 

We now give you the option to exclude attached files when copying a single page. Any files that were being used on the page will appear as "unknown attachment". 

If there are no attached files to copy, the checkbox will be disabled. 

Extended support for Edit in Office

For many teams, editing and versioning files is a vital part of working productively in Confluence. For that reason, we're extending our support for Edit in Office to enable these features for organizations who can't use the Atlassian Companion app in their environment.

Edit in Office will remain as a dark feature in 7.1 (previously only available in 6.13.6 and 6.15.6). Once enabled, WebDAV integrations will be restored, allowing users to edit attached Office documents using the legacy Edit in Office options. This action will also disable the Companion app integrations, so any functions provided by Companion won't be available.

Check our EAP documentation for details on enabling Edit in Office.

Upgrade notes

Java 11 support

We now support running Confluence with Java 11 (Oracle and AdoptOpenJDK). Java 11 is a Long Term Support version, so will set you up for several years of access to regular bug fixes and security updates.

In this release we've bundled the AdoptOpenJDK 11 JRE for use with new installations. If you've installed Confluence manually you can either continue to use Java 8 or switch to Java 11 now.  See Change the Java vendor or version Confluence uses to find out how to switch your Java version or vendor.

Some of the Java arguments used in our setenv.sh  / setenv.bat  files are no longer recognised in Java 11. When you upgrade, make sure you apply your customisations manually, don't simply copy over your old setenv file (or existing Java options if you run Confluence as a service). 

Here's what changed...

In Java 11, the following arguments:

-XX:-PrintGCDetails -XX:+PrintGCDateStamps -XX:-PrintTenuringDistribution -Xloggc:$LOGBASEABS/logs/gc-`date +%F_%H-%M-%S`.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M
-Djava.locale.providers=COMPAT,SPI 

are replaced by:

-Xlog:gc+age=debug:file="%atlassian_logsdir%\gc-%atlassian_timestamp%.log"::filecount=5,filesize=2M 
-Djava.locale.providers=COMPAT,SPI,CLDR 

We've also added the following new arguments:

-XX:+IgnoreUnrecognizedVMOptions 
-Djdk.tls.server.protocols=TLSv1.1,TLSv1.2 
-Djdk.tls.client.protocols=TLSv1.1,TLSv1.2    

IgnoreUnrecognizedVMOptions  means that unrecognised Java 8 arguments will be ignored. You won't need to remove these manually. 

See Enable Logging with the JVM Unified Logging Framework in the Java 11 documentation for more detailed information. 

If you have added additional arguments, you may need to check that these are still available in Java 11, as they may cause errors when you start Confluence. 

Supported platforms changes

  • Added support for Java 11 (AdoptOpenJDK and Oracle)
  • Advance notice: Confluence 7.3.x will be the last release to support PostgreSQL 9.4, MySQL 5.6 and Oracle 12c R1. See End of Support Announcements for Confluence for more information.

Infrastructure changes

Confluence 7.1 contains changes that may affect apps. Head to Preparing for Confluence 7.1 to find out how these changes will impact app developers. 

Last modified on Oct 29, 2019

Was this helpful?

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