[MGNLUI-1811] Magnolia Module dependencies between ui modules should be fixed Created: 04/Jul/13  Updated: 09/Jul/13  Resolved: 04/Jul/13

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.1

Type: Bug Priority: Neutral
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Current module dependencies(module descriptors) in UI modules are set like this:

 <dependency>
      <name>ui-framework</name>
      <version>5.0/*</version>
    </dependency>

This cause obscure errors, because really, ui-admincentral 5.0.1 does depend on -framework 5.0.1 and can't work with 5.0

I suggest doing this instead:

    <dependency>
      <name>ui-framework</name>
      <version>5.0.1</version>
    </dependency>

or even

<dependency>
      <name>ui-framework</name>
      <version>${project.version}/version>
    </dependency>

Since all ui modules will be released simultaneously, this should be fine. The day something gets extracted, this can be changed back.



 Comments   
Comment by Magnolia International [ 04/Jul/13 ]

Fixed dependencies to ui-admincentral and ui-framework to current project version instead of 5.0/*. Added explicit dependency to ui-framework on ui-mediaeditor and ui-contentapp.

Generated at Mon Feb 12 08:50:23 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.