[MGNLEE-534] Manage jars for EE addons, not just addon-bundles Created: 18/Aug/15  Updated: 18/Aug/21

Status: Accepted
Project: Magnolia DX Core
Component/s: None
Affects Version/s: 5.4
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Richard Gange Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Support
Story Points: 5

 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.



 Comments   
Comment by Mikaël Geljić [ 16/Feb/18 ]

So it's more the fact that we don't manage jars but only the "bundle/zip" artifacts for ee-addons such as ldap or cas (and these bundle archives contain the respective module jars). I have nothing against managing versions of these magnolia modules in current ee-bundle parent already. It kind of acts like the current BOM.

Generated at Mon Feb 12 05:30:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.