Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
This page contains the information you should be aware of when you are upgrading to Magnolia 5.7.x from any previous and currently supported version.
Before starting the upgrade, we recommend you read:
- Release notes for the version you are updating to as well as for all intermediate versions
- How to update
- Certified stack
What to update
Add privacy modules
If you have an Enterprise license, add the new privacy modules that help you make your websites GDPR-compliant:.
Maven is the easiest way to install the modules. Add the following dependency to your bundle:
Maven dependency management will include the other required submodules. Make sure that all dependencies are in the same version.
Changes on add-on modules
Updated add on modules
With Magnolia 5.7 we also have updated the Backup module to version 2.3. If you want to use the backup module, you must upgrade it to 2.3.
Outdated add-on modules
In Magnolia 5.7 we removed several add-on modules (not bundled). We recommend you remove them too.
This is the list of the add-on modules removed:
See also MGNLEE-533 - Getting issue details... STATUS .
You must remove the
You can do many common WebDAV tasks with light development. You can store web resources such as CSS and JS files, template scripts and many more items in a light module and edit them comfortably as local files with your favorite editor. When you are done with the changes, push and commit the files to Git and configure Magnolia to watch for changes in the remote Git directory. Magnolia will register changes in light modules instantly.
Check custom fields extending or decorating Magnolia fields
We have changed some names for field definitions. The name of a field definition is the node name if defined via JCR in the folder
modules/some-module/fieldTypes or the file name of a YAML based definition. Field definitions which have been defined via JCR and which we have renamed now are defined with YAML files. This was part of the initiative to reference fields by its "short" name with the property
fieldType (see Referencing fields).
If you have custom fields which reuse an existing Magnolia configuration via YAML include, YAML inherit, JCR extends or by decoration, your custom definition may be broken now if you reference to a field which has changed its name.
|Old name||New name||Since|
Removed, previously deprecated.
|Content tags module|
|Content dependencies module|
|Content editor module|
Use the Definitions app to check for problems.
Between Magnolia 5.6.6 and Magnolia 5.7, the
magnolia.properties file has not changed.
When upgrading Magnolia, it is always worth comparing your
magnolia.properties file with the one from the newly released Magnolia bundles.
Below are the latest versions of the
magnolia.properties files for the Magnolia 5.7.x series:
Magnolia CE / Magnolia EE Standard **) Magnolia CE and Magnolia EE Standard use the same
Magnolia EE Pro
Apache Tomcat 9.0.8
If you use Apache Tomcat: we have upgraded to Apache Tomcat 9.0.8.
If you use another servlet container, check the certified stack for supported versions.
If you want to run Magnolia on Java 9 or 10, you must use Jackrabbit 2.16.1.
magnolia-module-groovyto version 2.7, which ships the latest stable version of Apache Groovy 2.5.
Earlier versions of Groovy were delivered in a single jar file called
groovy-all but this library does not exist anymore.
magnolia-module-groovy-2.7 now ships with only the minimum set of libraries:
Some of your custom Groovy scripts may require additional libraries.
Other third-party libraries
How to update
Update to the latest minor release version first before upgrading to the most recent major release.→ → 5.7.x
A June 2018 example: a customer is considering an upgrade from 5.5.8 to 5.7. The correct upgrade sequence is: 5.5.8 →
- Update all external libraries required by the Magnolia release to which you intend to upgrade.
- Because the upgrade process takes time and is vulnerable to incidents, we recommend you minimize the risk by cleaning up your system, removing unused data, reindexing everything and doing a full backup first.
Once Magnolia is running, check the Definitions app for deprecated or problematic definitions.
- Stop the application server.
- Extract the new Magnolia bundle.
- Replace JAR files in the
WEB-INF/libfolder of your old Magnolia instances with new JARs from the bundle. Also replace modules coming from the add-ons bundle (magnolia-enterprise-addons-bundle), in case you are using any of these.
Magnolia 5.7 updates numerous 3rd-party libraries, see Java 8, 9 and 10 runtime compatibility and library updates.
- Remove any module JARs you had previously removed from your instances. Add any modules you may have previously added.
We have removed several add-on modules. You must also remove some. See Remove outdated add-on modules.
- Add new Magnolia modules. See Add the privacy modules.
- Optional: Delete all indexes to give them a boost. Delete the
indexfolder under each workspace directory:
repositories/magnolia/workspaces/<workspace>/index. Indexes are recreated on startup, which might take a while depending on the size of your repository.
- If you customized your
magnolia.propertiesfiles, compare the changes to the file in the new bundle. Properties may have been added or removed.
- Read the release notes for all intermediate versions for any additional update tasks.
- Restart the application server.
- In your browser, go to the Magnolia instances and run the web update.
Updating Maven managed webapps
In this section we assume that you use Maven to manage your (custom) webapp. How you do this depends on how you have organized your pom files.
Upgrading the versions of inherited BOM files
The most typical use case is that your custom webapp is based on one of Magnolias preconfigured webapps. The structure of the Maven project that manages your webapp may look like this:Line 3:
custom-ee/custom-ee-webapp/pom.xmlis the pom file of your custom webapp.
custom-ee/pom.xml is the parent pom file of your custom webapp. This file manages the dependencies and their versions.
Note that the parent pom (custom-ee/pom.xml) manages all versions for Magnolia modules as well as for third-party libraries.
info.magnolia.eebundle:magnolia-enterprise-bundle-parent, which manages Magnolia Enterprise module versions and imports the following:
info.magnolia.bundle:magnolia-bundle-parent- manages Magnolia CE module versions.
info.magnolia.boms:magnolia-external-dependencies- manages third-party library versions.
If the pom files for your custom webapp are organized as shown in this example, you only need to change one property. In the
<properties> section of your parent pom, change the version of the
magnoliaBundleVersionto your required version. That is all you need to change in the pom files of your webapp.
Checking the Maven dependency tree
Regardless of how your Maven project is organized, building the Maven dependency tree helps you analyze the versions of all the Magnolia modules and all the third-party libraries of your custom webapp.
Open a shell, go to the directory of your webapp and execute the Maven command for the dependency tree:
Tomcat 8 using BCEL may throw class format exception
On Tomcat 8.5 or lower, you may encounter a class format exception. Reason: Apache Commons BCEL is used by Tomcat to scan for annotations. Some Java EE 8 APIs were produced from JDK9 as Multi-Release JARs. This means they're compatible with Java 8, but may also contain some Java 9 classes, including the Tomcat 8.5.12 and 9.0.0 updated Commons BCEL to support this. See the extract below from the Tomcat changelog. Solution: Use Tomcat 8.5.12 or higher.
module-info.class. Older Commons BCEL versions did not know how to read such classes.
60688: Update the internal fork of Apache Commons BCEL to r1782855 to add early access Java 9 support to the annotation scanning code. (markt)
On Tomcat 8.5 or lower, you may encounter a class format exception.
Apache Commons BCEL is used by Tomcat to scan for annotations. Some Java EE 8 APIs were produced from JDK9 as Multi-Release JARs. This means they're compatible with Java 8, but may also contain some Java 9 classes, including the
Tomcat 8.5.12 and 9.0.0 updated Commons BCEL to support this. See the extract below from the Tomcat changelog.
Use Tomcat 8.5.12 or higher.
If you encounter other problems, check the Known issues page.
Virtual URI mappings not working if too many are configured
To mitigate an issue caused by having more than 500 configured virtual URI mappings in light modules, a WARN-level message is now logged when a
DirectoryWatcher overflow occurs (MAGNOLIA-7762). We recommend to keep the number of files in a single folder below 100 and to use folder hierarchies whenever possible. For the upcoming fix, see MAGNOLIA-7798.