Magnolia 5.4 reached end of life on November 15, 2018. This branch is no longer supported, see End-of-life policy.
For more information about working in the DAM see Digital asset management. The DAM App module installs the Assets app.
The Digital Asset Management (DAM) module provides the functionality to manage assets such as images, videos and documents and use them on the website.
artifactId | ||
---|---|---|
magnolia-dam-parent | parent reactor | |
magnolia-dam-api | API for the base classes as
Item
,
ItemKey
,
Asset
,
Folder
AssetRendition
,
AssetProvider
| |
magnolia-dam-core | Core functionality. contains an implementation for
AssetProviderRegistry
, the
DamDownloadServlet
, etc. | |
magnolia‑dam‑compatibility | Exposes the Magnolia DAM 1.x implementation to enforce compatibility between DAM module1.2.x and 2.x | |
magnolia-dam-jcr | JCR based implementation of AssetProvider , etc. | |
magnolia-dam-app | The Magnolia module which contains and configures the content app to administrate the assets. (The content app depends on the magnolia-dam-jcr because of its Content connector). | |
magnolia-dam-imaging | The link between magnolia-dam-jcr and the Imaging module. Provides a AssetRenderer based on magnolia-dam-jcr. | |
magnolia-dam-templating | ||
magnolia-dam-preview | Adds thumbnail and portrait views for PDFs and videos. This is an optional module and is not installed by default. |
All DAM sub modules, except DAM Preview, are bundled with Magnolia and typically already installed. You can download the bundle or individual sub modules from our Nexus repository.
DAM is a Community module. All sub modules, except DAM Preview are typically already installed. Launch the Configuration app and go to /modules/dam
, /dam-app
, /dam-templating
and /dam-jcr
to check. The DAM API and DAM Compatibility modules are not registered in configuration and DAM Preview is an optional module that needs to be downloaded and installed separately.
Choose this option if you have your own bundle. Using Maven to manage module dependencies is a best practice.
Add a dependency
element including the module version number in your bundle's parent POM:
<dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-api</artifactId> <version>2.1.11</version> </dependency>
<dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-app</artifactId> <version>2.1.11</version> </dependency>
<dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-compatibility</artifactId> <version>2.1.11</version> </dependency>
<dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-core</artifactId> <version>2.1.11</version> </dependency>
<dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-jcr</artifactId> <version>2.1.11</version> </dependency>
<dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-templating</artifactId> <version>2.1.11</version> </dependency>
<dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-imaging</artifactId> <version>2.1.11</version> </dependency>
Add a dependency
element without the version number in the Magnolia webapp POM, typically inside the parent project:
<project> <dependencies> <!-- more dependencies here ... --> <dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam</artifactId> </dependency> <dependency> <groupId>info.magnolia.dam</groupId> <artifactId>magnolia-dam-imaging</artifactId> </dependency> <!-- more dependencies here ... --> </dependencies> </project>
All required modules are directly oder transiently included by the 2 modules above.
Get further information at: