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.
The Tools module provides an app and some commands useful for manipulating repository content. The app, known as Repository Tools, can be found under the Tools menu of admincentral.
artifactId) have changed since Magnolia 5.5.
If you have custom Java code relying on this module, you need to install a compatibility module too.
Note the changes in
artifactId since the 1.9 release.
<dependency> <groupId>info.magnolia.tools</groupId> <artifactId>magnolia-tools</artifactId> <version>1.9.3</version> </dependency>
We have been gradually removing the old Content API from our modules since Magnolia 5.6. If you have custom code relying on classes from the old tools module then you must do one of two things:
- Update your code for the new version of the tools module.
- Or you can use the
magnolia-tools-compatibilitymodule together with the
Add the following snippet to you pom file:
<dependency> <groupId>info.magnolia.tools</groupId> <artifactId>magnolia-tools-compatibility</artifactId> <version>1.9.3</version> </dependency>
Add these jar files to the
WEB-INF/lib folder of your webapp:
See Repository Tools app.