[MGNLLIC-68] Licensing module should work with new major version 6.x Created: 10/Jul/18  Updated: 29/Nov/18  Resolved: 26/Oct/18

Status: Closed
Project: Magnolia License
Component/s: None
Affects Version/s: None
Fix Version/s: 1.7

Type: Task Priority: Blocker
Reporter: Michael Mühlebach Assignee: Michael Mühlebach
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: 6.0 requisite
Sprint: Basel 157, Basel 158
Story Points: 8

 Description   

The licensing module atm only work with 4.x and 5.x major versions which are hardcoded in the LicenseProcessor. Some part actually only works with 5. and just considers everything beside as 4.

Goal

The LicenseProcessor is capable to handle multiple license versions/variants which are abstracted. We have to encapsulate the handling of different types of licenses in one place.

Acceptance Criteria

  • All new code has a test coverage of 100% (this system is a crucial part of magnolia and we can't allow ourself to make mistakes)
  • Code to create licenses has to be especially validated because its only used in the license generator project
  • Licensing of individual modules must still work
  • The new new license module version has to still work with magnolia 5 because we potentially want to allow super licenses which support both 5 & 6. (that means its compatible with magnolia 5.5.x)
    • Sales team says "super license" capability may possibly be useful but is not critical. We won't invest in this feature now.

Open Questions?

  • We have some strange dependencies between license and main because of Version & VersionRange. We might want to resolve that in one or another way -> arch meeting
  • Does/should any customer use the license module directly? In other words must the API be backwards compatible??
    • Answer: No. Only authorized Magnolia employees should be able to generate keys.

Generated at Mon Feb 12 06:00:17 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.