Details
-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
5.4
-
None
Description
In magnolia-enterprise-bundle-parent we manage:
magnolia-ldap-bundle
magnolia-module-cas
magnolia-module-synchronization
magnolia-module-webdav
Like this:
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-ldap-bundle</artifactId>
<version>1.6.3</version>
<type>tar.gz</type>
</dependency>
.
.
.
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-module-cas</artifactId>
<version>1.0</version>
<classifier>bundle</classifier>
<type>tar.gz</type>
</dependency>
Let's manage the dependencies for all the jars in a Magnolia BOM:
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-ldap</artifactId>
<version>1.6.3</version>
</dependency>
.
.
.
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-module-cas</artifactId>
<version>1.6.3</version>
</dependency>
This way customers will not need to look up the compatible version when they want to include one of these modules in their project.
Besides the ones mentioned above it would be nice to include other popular (if not all community and enterprise modules compatible with the given version) modules, such as, Blossom and observation.
Checklists
Acceptance criteria