Magnolia 5.3 reached end of life on June 30, 2017. This branch is no longer supported, see End-of-life policy.
Back up your system before installing a module. Uninstalling is not as simple as removing the JAR files. Modules add and change configuration and may change content. Try the module in a test environment first. A module is responsible for updating itself across versions. Keep only one version of each module and its dependencies.
Choose this option if you have a bundle. Managing module dependencies with Maven is a Magnolia best practice.
To install a module:
Add a dependency
element including the module version number in the bundle parent POM:
<project> <dependencyManagement> <dependencies> <dependency> <groupId><!-- groupId --></groupId> <artifactId><!-- artifactId --></artifactId> <version><!-- version --></version> </dependency> </dependencies> </dependencyManagement> </project>
Add a dependency
element without the version number in the Magnolia webapp POM, typically inside the parent project:
<project> <dependencies> <dependency> <groupId><!-- groupId --></groupId> <artifactId><!-- artifactId --></artifactId> </dependency> </dependencies> </project>
Choose this option if you are new to Magnolia.
WEB-INF/lib
directory./webapps/<contextPath>/WEB-INF/lib
/server/default/deploy/<contextPath>/WEB-INF/lib