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. 

Please note that the artifact's IDs (Maven groupId and 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.

Check  Git for the new module structure .


Maven is the easiest way to install the module. Add the following to your bundle. The parent POM of your webapp project should set the latest version of the module automatically. Should you need to use a specific module version, you can define it using the <version/> in the dependency.

Note the changes in groupId and artifactId since the 1.9 release.


Compatibility module

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-compatibility module together with the magnolia-core-compatibility module.

With maven:

Add the following snippet to you pom file:



See Repository Tools app.