Page History

...

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 magnolia-ui and 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 magnolia-external-dependencies-65.07.pom .

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 the 65.0 branch7 branch.  Please note that this number may not be in sync with the version of the latest Magnolia release:

<dependencyManagement>
 <dependencies>
  <dependency>
   <groupId>info.magnolia.boms</groupId>
   <artifactId>magnolia-external-dependencies</artifactId>
   <version>6<version>5.0<7</version>
   <type>pom</type>
   <scope>import</scope>
  </dependency>
 </dependencies>
</dependencyManagement>

If you use magnolia-main parent ( 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

Released for Magnolia 65.07, the BOM below (click the link to expand and see the content) centralizes the dependencies originally scattered around the following modules (projects):

...

See also

• Software bill of materials (English Wikipedia)