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.
What is a software BOM?
A Software Bill of Materials (software BOM) is a list of components in a piece of software. Software vendors often create products by assembling open source and commercial software components. The software BOM describes the components in a product. It is analogous to a list of ingredients on food packaging. (Wikipedia)
BOM in Magnolia
As an option you may use a special BOM project to centralize dependencies for third-party modules instead of managing them in the
magnolia-main module and some other modules like
rest . This third-party BOM project is a just plain Maven POM project whose only responsibility is to manage the versions of third-party dependencies in POM file such as
To use a BOM in your project, include the following code snippet as the very first dependency in the dependency management section of the parent poms and adjust the version number accordingly. For the version number, use the latest version released for this branch.
Please note that this number may not be in sync with the version of the latest Magnolia release:If you use
info.magnolia:magnolia-project) to manage the third-party dependencies as well, we recommend that you use our third-party BOM for this in the future. You can apply the change at any time you want.
The BOM in Magnolia 5.7.x
Released for Magnolia 5.7.x, the BOM below (click the link to expand and see the content) centralizes the dependencies originally scattered around the following modules (projects):
- Software bill of materials (English Wikipedia)