[MAGNOLIA-1209] Module dependencies should be able to handle version numbers in a more flexible way Created: 14/Nov/06  Updated: 23/Jan/13  Resolved: 07/Aug/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.0 Final
Fix Version/s: 3.1 M3

Type: Improvement Priority: Major
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MAGNOLIA-1602 Update mechanism Closed
duplicate
duplicates MAGNOLIA-1285 modules: dependency check should get ... Closed
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)

 Description   

For instance, the dms module depends on adminInterface 3.0
At the moment, if we use it with adminInterface 3.0.1, it will just not deploy.
We should be able to

  • declare dependencies without version requirement (i.e "I need adminInterface, no matter what version")
  • declare dependencies with a minimal version requirement (i.e "I need adminInterface, at least version 3.0, ignoring minor versions // I need adminInterface at least 3.0.2")
  • declare dependencies with minimal and maximal version requirements (i.e "I need adminInterface, at least version 3.0, but I won't run with 3.1 or further versions")


 Comments   
Comment by Magnolia International [ 07/Aug/07 ]

duplicate with MAGNOLIA-1285

Generated at Mon Feb 12 03:24:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.